Sylvain Wallez wrote:
> > 1) serializers don't have full access to the component environment and
> >some want this to be changed
> >
>
> The major need is to be able to access the SourceResolver. I haven't
> seen any good use case where a Serializer needs to access something else
> in the environment. So what about a "SourceResolvable" interface handled
> by CocoonComponentManager ?
>
> public interface SourceResolvable {
> void setSourceResolver(SourceResolver resolver),
> }
>
> One more use case for this need : I have pending on my HD a Batik
> ProtocolHandler that allows any Cocoon source to be used in Batik's URL
> handling system. This allows to insert bitmaps stored in Blobs (using
> the BlobSource in scratchpad) in SVG drawings. The only thing that's
> needed is the SourceResolver. Nothing else.
Sounds like a good compromise. +0
What do others think of this?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
