Patrick Moore wrote:
To my untrained eye, it looks like the problem is that the
_componentResolver on line 390 of
org.apache.tapestry.pageload.PageLoader doesn't have the full class
name.
On 10/12/06, Patrick Moore [EMAIL PROTECTED] wrote:
Hi there --
I just shifted over to Tap 4.1.1 and
If this causes confusions , i'm 100% for making type required again.
I would vote a +1 for changing type back to required, mainly because of new
users.
Discarding type results in less readable code for example when
compared to omitting @InjectObject, which has a more implicit meaning.
So,
Ok, very thank you for your reply.
The problem is than I am using the wrong component.
In a form to populate tehe values of form fields to the bean properties
it must be submited. If you use the DirectLink component the form is not
submited, and values are not populated to bean properties.
Guys,
I am whipping up a simple Login page... no *.page files just annotations.
The page displays and the validators are nice.
If someone could bail me out here I would be greatful. The Login.html quits
on trying to render the OGNL for emailAddress.
OGNL is having trouble getting to this
Guys,
All I am trying to do is operate a model object Person.getEmailAddress()
from html to java.
Whats the deal with this notation...
@Component(type = TextField, id = emailAddress, bindings = {
value = ognl:person.emailAddress,
displayName = message:label.emailAddress,
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
Guys,
I am whipping up a simple Login page... no *.page files just annotations.
The page displays and the validators are nice.
If someone could bail me out here I would be greatful. The Login.html quits
on trying to render the OGNL for emailAddress.
OGNL is having trouble getting to this
The fact that (from his previous email) Tapestry was saying that it can't
find an emailAddress property on the generated page class BasePage_4
means that it's not using his Login page class or else the generated page
class name would be something like Login_x. So, that leads me to believe
that
Sorry, this is the delete component.
component id=delete type=Checkbox
binding name=selected value=toDeleteCategory/
/component
-Mensaje original-
De: Mael Caldas [mailto:[EMAIL PROTECTED]
Enviado el: Miércoles, 11 de Octubre de 2006 12:05 p.m.
Para: Tapestry users
Asunto: Re:
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
James Carman wrote:
The fact that (from his previous email)
No problem. I've seen that error many times before (in my own experience
especially). I've learned to look for BasePage_x when I get those unknown
property things.
-Original Message-
From: Robert Zeigler [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 12:57 PM
To: Tapestry
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;
The 4.0.x versions were ripe enough for that. I don't use page spec files
at all in my applications, especially with Tapestry-Autowire.
-Original Message-
From: Ken nashua [mailto:[EMAIL PROTECTED]
Sent: Friday, October 13, 2006 1:10 PM
To: users@tapestry.apache.org
Subject: RE
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
I would vote just the opposite way. In this case I am returning the
exact type that is declared on the abstract method. I am not returning
a BaseComponent. I hate the 'type' parameter. It interfers with
refactoring because eclipse doesn't know it should do anything with
the type parameter. So far
How do you tell if a component was rendered?
--
Dan Adams
Senior Software Engineer
Interactive Factory
617.235.5857
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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
1. Autowire is a feature that I implemented as a separate library and was
integrated into the 4.1 branch. Basically, it allows you to declare an
abstract getter for a type of a HiveMind service. For example, you can do
this:
public abstract HttpServletRequest getHttpServletRequest();
And,
Hello,
I have a persistent page property which gets set in pageBeginRender,
during the render phase. The persistent property is a value in a
property selection. When the page has rendered the the drop down list
box represented by the property selection always shows the first
element in the
Hello,
My page contains a persistent byte property which is used as the value
in Property Selection.
The persistent value is assigned inside pageBeginRender. During
debugging I can see the property being assigned a value other then
one. After the render the property selection always shows the
Should be fixed in latest snapshot.
I discovered the cause of some outstanding issues that had previously
plagued me in tacos. Thankfully I've been extremely conservative and haven't
let the code grow out of control so this one has been permanently tracked
down / fixed. (stupid IE ...)
On
24 matches
Mail list logo
