So sanjiva, let me tackle it post release or atleast we can do the release without this mediator.
I have a backlog of items to work on, and so maybe by the time I get to this mediator, the release will be finalized :)
Regards,
Rajith
On 10/28/06, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
On Thu, 2006-10-26 at 23:59 +0100, Paul Fremantle wrote:
> Seems interesting. I'm not sure how you do this in Axis2 without
> knowing the XPath of the binary attachment, because without looking at
> WSDL or specifying the path, the Base64 just looks like a string.
>
> So I guess we'd need a syntax like:
>
> <binary>
> <mtom>xpath1</mtom>
> <base64>xpath2</base64>
> </binary>
>
> This would take xpath1 and make it optimized, and xpath2 and make it
> base64. I guess we could add hex too.
Going from MTOM to base64 can be done w/o any help I think .. every
MTOM'ized bit is flagged at the XML level (with xop:Include).
The other way is definitely impossible without metadata assistance;
there's no way to tell that a string is base64 or not.
I'd *really* like to get another release out and get Synapse out of
incubation before adding yet another feature :). Synapse is not lacking
in features even now .. let's get the stuff we have really working and
then make it more functional.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
