Right, so again, where's the need to restrict the context coming from? I don't like this.
On Thu, Dec 10, 2009 at 1:39 PM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > Em Thu, 10 Dec 2009 19:26:40 -0200, Howard Lewis Ship <[email protected]> > escreveu: > >> I still don't get why context assets, outside of WEB-INF, should ever >> be restricted? Did I miss that conversation? > > This was discussed yesterday. I'm also late to it. :( I think that Tapestry > should come with reasonable defaults out of the box, and restricting context > assets isn't reasonable, as they're accessible in a pure servlet > application. Anyway, if something is in the context and isn't below WEB-INF, > it is meant to be public. The original problem was classpath files being > accessible by default. > > -- > 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] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
