--- Begin Message ---
Ovidiu Predescu wrote:
>>Another question, is the current abstraction of a sitemap able to allow
>>different principles of sitemaps (current one, scheme-based one, etc.)
>>the admin/developer can choose from depending on his needs ? E.g., I'd
>>use the current sitemap type at the root, mounting a scheme-based
>>sitemap under /scheme, then in the scheme-based sitemap I'd mount some
>>other sitemap type under /scheme/other and so on.
>>
>The scheme-based sitemap will provide the old semantic of the sitemap
>as well. We can even support the current syntax by adding a
>translation layer.
>
>In the general case, we can provide two servlets, CocoonServlet and
>the Scheme servlet in the same WAR files, mounted at different URLs as
>you mention above. This way the two implementations share the same
>classes, but each does it's own dispatching.
>
I meant it another way; currently, we are able to mount a sub-sitemap
from our sitemap, but the implementation of the mounted sitemap cannot
be chosen. If we were able to choose and mount alternative
implementations (the classic sitemap as "transforming" or "interpreting"
implementations, and a scheme-based, XMLified, implicit approach) as
sub-sitemaps, we could both solidify the current sitemap as we all know
it and allow for extensions like your implicit scheme-based concept.
Best regards,
Michael Hartle
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
