Please check out: http://tapestry.apache.org/tapestry5/tapestry-core/guide/reload.html
Basically, you shouldn't mix component classes with services classes. When you do so, you need to define an interface for your components to implement. On 10/10/07, Peter Stavrinides <[EMAIL PROTECTED]> wrote: > > Hi All > > I use Tapestry 5, Java 6 with the maven plugin in eclipse 3.3. I am > building a user specific navigation component, and I am getting this > strange error: > > java.lang.LinkageError > loader constraint violation: when resolving method > "com.web.services.BreadCrumbs.getRootLink()Lcom/web/components/IrmLink;" > the class loader (instance of > > org/apache/tapestry/internal/services/ComponentInstantiatorSourceImpl$PackageAwareLoader) > of the current class, com/web/components/Navigation, and the class > loader (instance of org/mortbay/jetty/webapp/WebAppClassLoader) for > resolved class, com/web/services/BreadCrumbs, have different Class > objects for the type com/web/components/IrmLink used in the signature > > I have tried to clean the project several times thinking this is an > issue with cached resources on the classpath, but have had no luck, so I > am starting to wonder if this could relate to Java 6 and the maven plugin. > > Has anyone seen this before? > > thanks for your help. > > Peter > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Partner and Senior Architect at Feature50 Creator Apache Tapestry and Apache HiveMind
