Re: Re: How I plan to move forward.

> 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...

>
> As for being on crack - well... you are working endless hours on the
> taming of the shrew(d Tapestry configuration options), aren't you? :-)
> [and yes, all work VERY MUCH appreciated]
>

Thanks!

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