Any top-level class under components is considered to be a component and will be loaded in a special class loader. This causes a problem when an instance is created by the normal class loader and passed into a comopnent, which has a distinct Class instance.
Create a different package for objects of this type; i.e. com.java.dse.cwp.eos.data.Tab. This is all documented http://tapestry.apache.org/tapestry5.1/guide/reload.html On Fri, Jul 10, 2009 at 3:16 PM, xfile80303<l...@grokers.net> wrote: > > The more I look at this the more it looks like a classloader issue. As in, > my classes are being loaded by two different classloaders which do not > inherit from one-another. Any bells ring for folks? > > Levi > -- > View this message in context: > http://n2.nabble.com/-T5.1--Coercion-Class-mismatch-error-%28a-real-headbanger%29-tp3237426p3237771.html > Sent from the Tapestry Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
