On 10/26/06, Stefan Podkowinski <[EMAIL PROTECTED]> wrote:
My case for creating the patch was that some frameworks require to have config files in the classpath, so we decided to just put all of them there, incl. spring etc. This convention also works for creating standalone apps where no web-inf directory is available. I think it should just be up to the developer to decide. In fact, I've only came accross two frameworks so far that insisted on the web-inf location, which is sitemesh (patch available through jira on this) and trinidad (same as well now ;))
Actually, it's probably many more than that. Many, many J2EE web frameworks, component libs, etc. just do all of their configuration in WEB-INF/web.xml. That counts as insisting on WEB-INF to me! Since we are strictly a webapp framework - there is no such thing as "standalone Trinidad" - it's hard to see any developer gain from moving it around within the file system. Auto-loading from the classpath - supporting both WEB-INF/trinidad-config.xml in the webapp and META-INF/trinidad-config.xml on the classpath - is a more potentially useful feature, esp. since we could pretty easily support precedence rules where WEB-INF wins. -- Adam On 10/26/06, Simon Lessard <[EMAIL PROTECTED]> wrote:
> I don't really see the gain on trinidad-config.xml either... Web app. config > files are all found under WEB-INF except sometimes log4j.properties and .hbm > for Hibernate and those are linked to the classes, while > trinidad-config.xmlis a pure WEB app config file. I could see it in > META-INF as well by pushing > the limits, but really not anywhere else. > > My 2ยข > > ~ Simon > > On 10/26/06, Adam Winer <[EMAIL PROTECTED]> wrote: > > > > What do people think about this proposed feature: > > > > http://issues.apache.org/jira/browse/ADFFACES-253 > > > > It lets you put trinidad-config.xml somewhere other than WEB-INF. I'm > > kinda > > split > > on whether this is a good idea or not. It's hardly a big feature, so on > > the > > one hand, why not, but on the other hand, it makes life harder for > > development tools - they can't just know where to find the file - makes > > it possible for people to get confused about which file they're using, > > and doesn't really seem to add a lot of benefit. > > > > -- Adam > > > > > >
