El Lun 02 Mar 2009 18:26:32 Carl Crowder escribió:
> This is just a vague guess, but as far as I *think* that class name
> isn't the only thing Java uses to compare two classes when casting. So
> if you have defined your TreeNode class in more than once place, it's
> possible that the class you're passing it and the class Tapestry is
> trying to use were loaded by different classloaders from different
> places. When you define it in the Tapestry page class I guess it only
> uses the one class file so it works fine. Check how many TreeNode.class
> files you have on your classpath, in jars or locally.
Yes I think that's the problem. I found about it in the tapestry faq just
after I sent this email :)
Best regards
Jorge
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
