> One of the big changes of Cocoon 2.1 compared to 2.0 is that
> SourceResolver is now available as a regular component, meaning you
> get it using "cocoon.manager.lookup(SourceResolver.ROLE)", so I don't
> see the need to expose it as a property.
>
> 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 ?
Sounds even better to me.
Upayavira
