yes i did use idPath for the hidden field.
but i'm using tapestry 4.0.2 - could that be the reason i'm seeing different
results than you are?
On 11/5/06, Patrick Moore <[EMAIL PROTECTED]> wrote:
did you assign the hidden field's id using idPath?
Also I am using the 4.1.1 SVN build.
I am havi
did you assign the hidden field's id using idPath?
Also I am using the 4.1.1 SVN build.
I am having some success with this method (borrowed from another's
email) in finding the unique ids but I haven't throughly tested it
yet:
public String getUniqueId(AbstractComponent component) {
retu
Hi,
I am using Hibernate+Spring+Tapestry and Spring's OpenSessionInView filter.
It works fine with classical Http Requests. But it does not work with
asynchronous requests i.e. with tacos, perhaps now with tapestry 4.1. If you
have any ideas how to make it work i am interested.
- Original
Nevermind, after a lot of searching I found the issue: JBoss.
Apparently JBoss defines its date formats differently and I need to
start it up with
-Dorg.jboss.util.propertyeditor.DateEditor.format=dd/MM/
See http://article.gmane.org/gmane.comp.java.tapestry.user/32671
On Nov 4, 2006, at 4
Pat, I tried an example similar to the one you've mentioned above. My
observation however is that the output will be something like this:
i.e. in the second instance of input type="hidden"
the id="my.path.foo" and *NOT* id="my.path.foo_0" as you had suggested.
Any comments?
Patrick Mo
Whenever you're not sure about something there are always branchesVery
cheap and easy to use and allows for easier collaboration on code.
On 11/4/06, andyhot <[EMAIL PROTECTED]> wrote:
Patrick Moore wrote:
> I am hardly close to being an expert ... :-) So I always qualify what
> I am saying
I don't know about reconnecting the object in session-per-request.
The session is not maintained between requests. I think that's
session-per-conversation. There a version number column for the
database entity that increments on the first entity select. If the
version number doesn't match, a wa
Patrick Moore wrote:
> I am hardly close to being an expert ... :-) So I always qualify what
> I am saying because some of the times I was just making a mistake in
> my understanding. For me clientId was not working if I had a component
> nested in a @For loop.
clientId also didn't work for me...
I am hardly close to being an expert ... :-) So I always qualify what
I am saying because some of the times I was just making a mistake in
my understanding. For me clientId was not working if I had a component
nested in a @For loop.
On 11/3/06, Roberto Ramírez Vique <[EMAIL PROTECTED]> wrote:
He
So do you have some way of locking all objects to the new session on
the subsequent request? Is this automated in some way? My problem with
the session-per-request-with-detached-objects is that there needs to
be some way to easily identify and re-attach the set of objects that
will be used. I've f
I'm not sure I want to persist the session across requests. I think
session per request with detached objects is OK for us because
optimistic locking will almost certainly work. The opt. lock
versioning should be ok.
I looked at your examples and saw the hivemodule and hibernate.cfg
config file
For the lazy loading, what about writing a custom servlet filter as
recommended in the hibernate docs, one that handles the session for
you? Let it sit out there in front of Tapestry and manage the
sessions. I'm leaning toward
session-per-request-with-detached-objects and letting optimistic
lock
Lot of thanks Sam & Karthik. I'll try it !
sincerely,
robert
On 11/3/06, Karthik N <[EMAIL PROTECTED]> wrote:
Sam is right.
is correct
We have used this before and it works well.
On 11/3/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
>
> I've never actually done this, but I imagine tha
Glad to see tapernate is not an orphaned project. I don't quite understand
the "java-forge" thing. If Im on the tapernate page, I can go get to the
javaforge home page, but from the javaforge home page I can not find
tapernate (leading me to belive it was orphaned).
Is there a new version that
I use my own implementation of a session-per-conversation strategy.
What I do is I have a conversation manager that stores all
conversations for a user betwee requests. I persist the conversation
ID to the client using an @Persis("client") annotation. I attach the
conversation in the pageValidateL
Bill,
The lazy loading problem can't really be solved in a generalized way.
But, Tapernate does a lot of work for you. I wouldn't suggest using
the property persistence strategies from Tapernate right now. I'm
working on a new version that will hopefully be more robust. The main
problem that I
Hi all,
Anyone been looking for a hosting for a tapestry based web application?
Do you think it's necessary/preferable to have a dedicated virtual machine?
What is an acceptable monthly price?
Other things to consider that are specifically important when using
tapestry?
Thanks,
Lennart
--
Lenna
http://wiki.apache.org/tapestry/HowTos
http://wiki.apache.org/tapestry/TapestryFasttrackForStrutsProgrammers
esp. check out the last link... it describes a @JspPage component,
allowing you to
simply add
anywhere !
Edgar Yip wrote:
> Hi All,
>
>
>
> Our company is evaluating Tapestry 4.0 and
Brooks, Aiyana [CIB-IT] wrote:
> Hi,
>
> I am new to Tapestry and am having some trouble getting the basic
> (nothing dynamic) "Hello World" application to run. Whenever I run the
> application I get the following error:
>
> Unable to process client request: Failure enhancing class
> org.apache.tap
Hello,
I'm trying to use a date picker with validation:
value="validators:required,minDate=7/1/2006,maxDate=12/31/2006"/>
But I'm having 2 issues. First I keep getting this error:
Error initializing validator 'minDate' (class
org.apache.tapestry.form.validator.MinDate): Unable to convert
'7
Ok I tried it very often ... and it looked like that
page:
...
...
myformcomponent.jwc
...
...
myformcomponent.html
Content...
21 matches
Mail list logo
