Re: Group pages or components into packages

[Thiago H. de Paula Figueiredo]

On Tue, 30 Mar 2010 14:34:08 -0300, Juan Isern  wrote:


Hi guys,


Hi!

does anyone if it's possible to put components/pages into some other  
package instead of the default app/components app/pages?


The pages, componentes, mixins and base package names are fixed and can't  
be changed. On the other hand, you can have multiple Tapestry root  
packages. Just contribute to the ComponentClassResolver configuration:


public static void  
contributeComponentClassResolver(Configuration  
configuration) {
	configuration.add(new LibraryMapping("somePrefix",  
"your.root.tapestry.package"));

}

That's exactly what you need to do when you package components, pages and  
mixins in a JAR.


--
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-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Group pages or components into packages

[Juan Isern]

Hi guys,

does anyone if it's possible to put components/pages into some other package
instead of the default app/components app/pages?

I'd like to group closely related components into (sub) packages for a
better organization.

Thanks!
-- 
View this message in context: 
http://old.nabble.com/Group-pages-or-components-into-packages-tp28085894p28085894.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org