Thorsten Scherler wrote:
[...]
The locationmap provides a matching mechanism that is fully configurable
were the fallback:// is expecting the files in a fixed defined path
(e.g. lenya/xslt/some.xsl) forcing the dev/user to imitate/adopt this
structure. Meaning *lenya* defines the location (I hate to be forced to
do something). ;-)
Hmmmm ... I have to admit that I consider the location contract
appropriate in this context. Configuring this would IMO be too
much flexibility.
[...]
Now to why I think
"Fallback provides an implicit mapping, which IMO is
sufficient for publication templating. "
is not true. Imagine images or design resources in general in a
multi-pub environment, here I do want to have full control over the
mapping.
Why would it not be sufficient?
Further I activated actions in the locationmap when I wrote an implicit
mapping action
http://svn.apache.org/viewcvs.cgi/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.structurer/src/java/org/apache/forrest/structurer/acting/RecursiveDirectoryTraversalAction.java?rev=320710&view=markup
This is a fallback mechanism that we have in the dispatcher to match
view definition files.
Why do we need more flexibility?
To keep the site structurer open and not forcing to use the lenya
default one. IMO this adds to the entry barrier understanding lenya.
When I started I never really understand why some files *have to* go
into dir a and others in dir b. Let the user/dev decide this mappings.
I still disagree. If I'm familiar with a publication, I'd expect the
corresponding files in instances in the same locations.
The major point to convince me would be to switch to an established
solution instead of using our own implementation.
That is another point, what do we gain with the fallback:// what the
locationmap cannot gives us? If the answer is: nothing. Then I say we
are having the "luxury" of duplicate code, which is bad for maintenance.
Our committer base is still quite small and should focus on stuff that
we do not duplicate. Let forrest worry about locationmap maintenance and
if we find a bug we can fix it in their rep right away since we all have
write access there. I say pretty good deal. ;-)
I agree to this statement. But I'm not convinced that we should allow
to configure the locations.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
