Thanks Massimo, I was not aware of that! For anyone else who might use this, note that you must provide the fully-qualified class names instead of the simple names (com.foo.MyModule, instead of MyModule).

chris

Massimo Lusetti wrote:
On Sat, Feb 23, 2008 at 9:38 AM, Chris Lewis <[EMAIL PROTECTED]> wrote:

List,

 I'm working on a multi-module project in Eclipse. One of the modules is
 a T5 web app, while the others are components and services for T5. The
 generated artifacts are drop-in modules for T5, meaning they contain a
 Tapestry-Module-Classes header in their jar manifest.

 Now my problem is that in Eclipse, I can't figure out how to launch the
 web app through jetty launcher and have it pick up the other modules.
 Specifically, I can't get it to load the module classes - unless I use
 @Submodule. The problem with this is that I can't have @Submodule load
 modules that have already been (auto)loaded, and this is my problem. How
 can I get around this? It seems like the ioc container would know when a
 module has been loaded and therefore know no to load it again.

 As a side note, I'm told by Sven that this can be handled in Idea using
 some configuration/manifest hackery (see:
 http://code.google.com/p/tapestry5-components/issues/detail?id=26).
 However I'm using Eclipse. Any suggestions?

Specify the list of your tapestry modules into the tapestry.modules
JVM property in your jettylauncher configuration as stated here:
http://tapestry.apache.org/tapestry5/tapestry-ioc/run.html

That's all.


Reply via email to