Yes, I kept my parameter class inside same package as component, since it is
only sensible place to keep it.
It feels a bit stupid to have ImageMessage and ImageMessageModel in separate
packages. So, its classloader issue then because of mandatory type of
packaging.
Hope this will change sometime in a future, because it really disturbs
proper packaging.
Since I have just criticism in my last mails, I want to say there are bunch
of things which are SOOOO better then previous versions of Tapestry.
-V.jeran
----- Original Message -----
From: "Davor Hrg" <[EMAIL PROTECTED]>
To: "Tapestry users" <[email protected]>
Sent: Friday, November 16, 2007 8:35 PM
Subject: Re: [T5.0.6] Is coercion MANDATORY for custom parameter classes?
you must move any class that is not page or componenta from
base, components, pages packages
they get enhanced and those exceptions occur
http://wiki.apache.org/tapestry/Tapestry5HowToNotMakeCustomComponent
Davor Hrg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
