More on classpath order semantics (and lookup)

So, after all the verbal diarrhea in the last message I want to talk
some more about lookup and classpath order semantics.

I asked myself why is this a big deal with classpath order semantics
in the context root? There are no hidden files in an exploded war
layout.

This is true if you follow Spindle's example and 'require' the project
context to be in exploded war format.

But there is nothing saying that an exploded war format is *required*
by the core. On having more than one folder represent the context
root, some people actually prefer it.

It's an IDE implementers choice whether they want to support more than
one 'root' folder in the context root. I mean the core is ignorant of
the implementation of IResourceRoot/ICoreResource/ISearch.

But I think in this case classpath order semantics should come into play.

It could be the case that a file in one context root folder is
'hidden' by a file by the same name in another. I guess it depends on
how a real war file is built for deployment from all these folders but
would guess that one would want *something* like classpath order
semantics to apply!

Or am I off base here?

Geoff

--
The Spindle guy.          http://spindle.sf.net
Get help with Spindle:   
http://lists.sourceforge.net/mailman/listinfo/spindle-user
Blog:                     http://jroller.com/page/glongman
Feature Updates:          http://spindle.sf.net/updates


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642