Actually, what you're asking is about module autoloading and it's
described here: http://tapestry.apache.org/autoloading-modules.html.
Summary: put the JARs in the classpath. If they have the right MANIFEST.MF
entries, Tapestry-IoC will find the modules and load them automatically
them.
On Mon, 28 Jan 2013 17:57:22 -0200, Thiago H de Paula Figueiredo
<thiag...@gmail.com> wrote:
On Mon, 28 Jan 2013 17:48:16 -0200, Peter Wendorff
<wendo...@uni-paderborn.de> wrote:
Hi.
Hi!
I tried to setup a modular tapestry application with Maven and Eclipse.
Creating the core application with maven is easy and works.
Creating a java project with a Manifest file that exports some packages
I easy, but how do I get the core application to find/load the module
using run Jetty?
The same way you would in production: by having a JAR with the correct
info in it or by using @SubModule.
How/Where do I have to set the dependencies?
The same way you'd do without Tapestry: manually, in the project
settings, or using m2eclipse or something like that.
Is there a sample project setup for that use case? (modular tapestry
application in eclipse using jetty as (debug) container)
Use @SubModule({Module1.class, Module2.class}) in your AppModule class.
It'll work whether or not your modules are packed in JARs or not.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
