On Wed, 10 Mar 2010 21:05:22 -0300, Robert Hailey <robert@(protected)>
wrote:

> On Mar 10, 2010, at 5:47 PM, Howard Lewis Ship wrote:
>> I think the way that T5 locates the module class from the filter name
>> is over-engineered.
>> I think it should just be fixed as "AppModule", in the services
>> package, end of story.

That's a good idea.

> Is there utility in a multi-module tapestry app?

Yes. AppModule would include the other modules through @SubModule or
module autoloading.

> The other possibility would be to fail to initialize if it does not find
> the *Module.class it expects?

It makes sense, all real applications have some configuration to be done.

--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)