Carsten Ziegeler wrote:
Olivier Billard wrote:
Hi Cocooners,
I read here and there (COCOON-1995 for example), that using Cocoon 2.2,
the SourceResolver cannot be used in Spring Beans.
If true, this is very annoying, because this feature is really usefull,
to have components really independant in the way sources URI are passed
to them : "cocoon:" (yeah costfull, I know, this is just an example :)),
"context:", "blob:", etc... Those services are not tied to an absolute
path or whatever.
What are the solutions to use this ? Only to develop services using the
old Avalon framework ? Is it work in progress ?
I post this question in the users list, because this is really a Cocoon
2.2 "usability" issue.
Afaik, you can use the SourceResolver in your spring beans (when running
inside Cocoon); the bean name is the full name of the source resolver
interface.
Great news, thank you very much !
However, there might be protocol implementations (like cocoon:) which do
not work outside of a Cocoon request as the environment for this has not
been setup then. But I think this could be fixed by using the stuff
which is currently used in the cron block for the background stuff.
Sounds logic, thank you for this warning.
HTH
> Carsten
A lot, thanks ! And thank you for the quick answer.
--
Olivier Billard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
