why would someone want to block css, javascript and images only because they are on the classpath?
i use a lot of these type of assets to modularize by web application g, kris "Thiago H. de Paula Figueiredo" <[email protected]> 13.01.2010 11:56 Bitte antworten an "Tapestry development" <[email protected]> An "Tapestry development" <[email protected]> Kopie Thema Re: [VOTE] Tapestry Release 5.1.0.7 On Wed, 13 Jan 2010 07:18:14 -0200, Ulrich Stärk <[email protected]> wrote: > Ulrich Stärk: -1 (non-binding) > > For the same reasons and because one has to do additional configuration > in order for common assets on the context to be accessible. -1 (binding), for the reasons above. Let's reach an agreement on what the default must be. I guess most people here would agree with: Context assets: all common assets (images, CSS, JavaScript) accessible. Classpath assets: all blocked. -- 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: [email protected] For additional commands, e-mail: [email protected]
