You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Ryan Owens <ry...@infoether.com> on 2005/04/26 23:35:04 UTC
page property type gotcha
Hello,
I just ran into a 'gotcha' and was curious if it's been documented
somewhere and I just missed it.
The problem is that I simply had the incorrect type specified for a
page property, eg:
<property-specification name="myProperty"
type="my.package.WrongClassName" />
where it was supposed to be:
<property-specification name="myProperty"
type="my.package.CorrectClassName" />
being far too reliant on Java compile-time type checking, I was
expecting Tapestry to throw an error here so when I started getting
null pointers it didn't even cross my mind that the type might be
wrong. Eventually I figured out the type was wrong and that Tapestry
was simply setting the value to null since it didn't match the
specified type. I've hit this once or twice before, but it isn't
sinking in yet, maybe this time.
Makes sense, I usually like a quiet fail in my html, but I think of the
.page file more like java code than html, so I'd kinda like it to fail.
Is there a way to change this behavior easily?
No big deal really, just curious if this is a real 'gotcha' or if I
just missed a paragraph in the book.
thanks,
Ryan Owens
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: page property type gotcha
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
The "good" news is that in Tapestry 4.0, there are no 'type' attributes
on <property> (it's renamed in the 4.0 DTD).
Erik
On Apr 26, 2005, at 5:35 PM, Ryan Owens wrote:
> Hello,
>
> I just ran into a 'gotcha' and was curious if it's been documented
> somewhere and I just missed it.
>
> The problem is that I simply had the incorrect type specified for a
> page property, eg:
>
> <property-specification name="myProperty"
> type="my.package.WrongClassName" />
>
> where it was supposed to be:
>
> <property-specification name="myProperty"
> type="my.package.CorrectClassName" />
>
> being far too reliant on Java compile-time type checking, I was
> expecting Tapestry to throw an error here so when I started getting
> null pointers it didn't even cross my mind that the type might be
> wrong. Eventually I figured out the type was wrong and that Tapestry
> was simply setting the value to null since it didn't match the
> specified type. I've hit this once or twice before, but it isn't
> sinking in yet, maybe this time.
>
> Makes sense, I usually like a quiet fail in my html, but I think of
> the .page file more like java code than html, so I'd kinda like it to
> fail.
>
> Is there a way to change this behavior easily?
> No big deal really, just curious if this is a real 'gotcha' or if I
> just missed a paragraph in the book.
>
> thanks,
>
> Ryan Owens
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org