As I said, Tapestry can't find your page class. It doesn't know that
Login.html is supposed to use the Login class you've defined. Have you told
it the default package to look for page classes? Are your templates/page
classes in the right places?
-Original Message-
From: Ken nashua
I'm really not a tap 4.x guru, but...
Doesn't it seem funny that id=emailAddress, but the field is
emailAddressComponent?
Now, it may very well be that tapestry 4 will merilly let you have
inconsistent component
ids and method names (like I said, not a tap4 wiz), but, why do you then
also go
James Carman wrote:
As I said, Tapestry can't find your page class. It doesn't know that
Login.html is supposed to use the Login class you've defined. Have you told
it the default package to look for page classes? Are your templates/page
classes in the right places?
I'm not so sure
that Tapestry isn't finding his page class.
He may have changed something in the meantime, though.
-Original Message-
From: Robert Zeigler [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 11:41 AM
To: Tapestry users
Subject: Re: @Component whoas... Tap-4.1.1 help please (thanks)
James
have changed something in the meantime, though.
-Original Message-
From: Robert Zeigler [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 11:41 AM
To: Tapestry users
Subject: Re: @Component whoas... Tap-4.1.1 help please (thanks)
James Carman wrote:
As I said, Tapestry
users
Subject: Re: @Component whoas... Tap-4.1.1 help please (thanks)
Right... I just looked at his original e-mail and the exception is
different than
the one he reported later (which I didn't realize before; that's what I
get for 1/2 reading e-mails. :).
Apologies if I came across short.
Robert
Thanks Guys for the attention and apologies for the extra posts... web
latency I guess. Wasn't sure I even had a mailing list for a bit.
Anyway...
I have checked out and built all the tapestry-4.1.1 etc...
I am trying to create a tapestry app that has no Login.page file
James, I took your
Ok, so currently I have omitted the inline component annotation from the
java file and moved it back to the Login.page file
!DOCTYPE page-specification PUBLIC -//Apache Software Foundation//Tapestry
Specification 4.0//EN
http://jakarta.apache.org/tapestry/dtd/Tapestry_4_0.dtd;
@Component whoas... Tap-4.1.1 help please (thanks)
Thanks Guys for the attention and apologies for the extra posts... web
latency I guess. Wasn't sure I even had a mailing list for a bit.
Anyway...
I have checked out and built all the tapestry-4.1.1 etc...
I am trying to create a tapestry app that has
You're defining your component in both places. Take it out of the page spec
file and see what happens.
-Original Message-
From: Ken nashua [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 1:17 PM
To: users@tapestry.apache.org
Subject: RE @Component whoas... Tap-4.1.1 help
You don't have to be a 4.x expert to recognize this one; I told you
before. :)
You're trying to implicitly and explicitly define the same component,
and tapestry is complaining.
There are two types of component definitions in tapestry: explicit, and
implicit.
Implicit definitions define the
PM
To: users@tapestry.apache.org
Subject: RE @Component whoas... Tap-4.1.1 help please (thanks)
Thanks guys,
I omitted the Login.page file and tore out the annotations.
All that was left was the Login.html and thats even better for me.
So it runs alright.
James I has a few ques if you don;t mind
12 matches
Mail list logo
