"Sylvain Wallez" <[EMAIL PROTECTED]> wrote:
> Moreover the process() function could simply take an URI string and let
> the underlying implementation use the SourceResolver to get the actual
> source and verify that it's writeable.
>
> You will then write :
> cocoon.process("whatever", "file://blah") but also
> cocoon.process("whatever", "context://xdocs/content/foo.xml") (for a
> deployed webapp) and even
> cocoon.process("whatever", "cvs://my-module/foo")
>
> How does it sound ?
I prefer this approach to exposing the source resolver itself, indeed...
If one, then, needs to get a hold on the resolver, yes, he can obtain an
instance of the resolver through the component manager...
Pier
