Re: Re: How I plan to move forward.

Geoff Longman wrote:
>> Unfortunately, I wasn't aiming the exclusions at the user - more for
>> Spindle. I agree that it should "just work" - and up until Tapestry
>> became "ultimately configurable" it seemed as though it did (99% of the
>> time anyway ;-) ). What I was looking at was a possibility of Spindle
>> doing recursive searches down a hierarchy and excluding any 'namespaces'
>> that have a library in them. Thus:
>>
>> /WEB-INF/foo.application would include everything except
>> /WEB-INF/bar/** if there was a bar.library under /WEB-INF/bar
>>     
>
> Yes, of course. I misunderstood.
>
> The recursive search is implemented already and your suggestion is a good one.
>
> I guess the namespace with the 'deepest' path would 'win' anything
> below it (path-wise) to the exclusion of any other namespace.
>
> Need to identify the corner cases though.
>
> what about
>
> /com/mystuff/foo.library
> /com/mystuff/bar.library
>
> or
>
> /WEB-INF/foo.application
> /WEB-INF/bar.library
>
> These are cases exclusions won't help solve.
>
> Perhaps relax the "namespaces are never to overlap" rule into
> "namespaces may never be colocated" (bad wording for sure).
>
> Hmm, pondering...
>   
It may seem like bad wording, but I like it. The case of .application +
.library to me has always been contentious at best (may as well just
have one .txt file that processes everything). As for
/com/mystuff/*.library - I think this would indeed be a corner case. As
users find out all too often that they live in corners, I know. But
disallowing colocation should be a definite step in the right direction.

As a side question... is there any differentiation between the following:
library1.jar:/com/mystuff/foo.library
library2.jar:/com/mystuff/bar.library
WEB-INF/classes/com/mystuff/foo2.library

The reason I ask is that currently Tapestry itself distinguishes between
jar'ed resources and classes on the classpath (for page-spec packages at
least). I know this would be another can of worms - but still more in
the 'corner-case' scenarios than anything [my work with Tapestry has
been deeply rooted in an extreme corner-case environment, so don't think
I discount corner-cases as insignificant]



-------------------------------------------------------
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&kid=103432&bid=230486&dat=121642