To clear this one up, I was in error. My App Module class extended the Component Module class. (Doh!) I now remember doing this to have the Jetty Launcher in Eclipse pick up the component module configuration.
During my tour of the tapestry source I came across the "tapestry.modules" system parameter, so I can now have the component module picked up by both a stand-alone Jetty instance and the Eclipse Jetty Launcher. Cheers, Steve. On Dec 5, 2007 4:58 PM, Thiago HP <[EMAIL PROTECTED]> wrote: > On 12/5/07, Steve Eynon <[EMAIL PROTECTED]> wrote: > > > > To clarify, I only have the one component module (the > > WebsiteTagsModule) and it is only in that .jar that I specify the > > Tapestry-Module-Classes property in the MANIFEST.MF. > > So take a look at your environment. Once I ran into a similar problem with > Tapestry 4 because the Tomcat plugin I was using added the Eclipse project > classpath to the Tomcat one. This caused HiveMindo to be loaded twice > because, in WEB-INF/lib, there was a copy of the HiveMind jar. Summary: one > copy being loaded from WEB-INF/lib, one by Eclipse. Since I've found that, > I've never put any JARs in WEB-INF/lib during development. > Thiago > -- Steve Eynon 0780 390 5424 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
