Thanks to both of you, i don't know why but i used to see enums more as
constants declarations than as "classic" Java classes.
Howard Lewis Ship a écrit :
If ManagerStates is an enum, it does not belong in the components
package. It should be moved out to a more general package, such as
com.myc
If ManagerStates is an enum, it does not belong in the components
package. It should be moved out to a more general package, such as
com.mycompany.data. Anything under the components package is handled
specially by Tapestry.
On Tue, Apr 8, 2008 at 6:12 AM, Stephane Decleire
<[EMAIL PROTECTED]> wr
Sorry Ted but i don't see any non component in my component package ...
Ted Steen a écrit :
You shouldn't put non components under the components package.
If you do that Tapestry will do runtime class instrumentation on the
class and you will end up with exceptions like that.
Atleast this is wha
You shouldn't put non components under the components package.
If you do that Tapestry will do runtime class instrumentation on the
class and you will end up with exceptions like that.
Atleast this is what I think.
Maybe we could check this and show a more human readable error message?
Hope it he
Has anybody already get such a strange exception ?
org.apache.tapestry.ioc.internal.util.TapestryException :
com.mycompany.components.accounts.ManagerStates cannot be cast to
com.mycompany.components.accounts.ManagerStates
???
My ManagerStates class is an enum and here is the stack trace :
