Howard Lewis Ship wrote:
> 
> By putting the ASO class into the pages package, Tapestry created an
> enhanced version of the ASO class, as if it were a component. This
> enhanced class is in the class loader used for pages, components and
> mixins.  The reference to the ASO in the page is a reference to the
> enhanced version, not the normal version.  The ASO that's injected is
> from the normal class loader, not the enhanced class loader, thus a
> ClassCastException.
> 

I encountered the same problem by accident, but did suspect something
quickly as I had moved the class and the exception showed up on the next
refresh.

Still it would be nice for Tapestry to report more precisely what has
happened, if that's possible.

Stephan
--
http://www.stephan-schwab.com
-- 
View this message in context: 
http://www.nabble.com/T5---ASO-cannot-be-in-the-same-package-as-the-page--tf3447765.html#a9622369
Sent from the Tapestry - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to