Hi, Giorgio.
Thank you for looking into this. I would like to extend your proposal to
cover the binary data support for binding.ws.
1) JAXB mapping rules for binary data
java.awt.Image --> xs:base64Binary
javax.activation.DataHandler --> xs:base64Binary
javax.xml.transform.Source --> xs:base64Binary
xs:base64Binary --> byte[]
xs:hexBinary --> byte[]
Some of the JAXB annotations can be used to customize the mapping.
We also need to follow APPENDIX H: ENHANCED BINARY DATA HANDLING of the JAXB
spec.
2) Support xmime extensions in WSDL, see
http://www.w3.org/TR/xml-media-types/.
3) Support the exchange of binary data for WS using AXIS2 MTOM.
Let's work together to define a scenario and get it working end-to-end. Here
is what I have in mind:
A image transformation service which converts svg into jpeg. The pseudo
JAX-WS interface can be:
public interface ImageTransformer {
java.awt.Image transform(javax.xml.transform.Source svg);
}
We can start from a WSDL and use wsimport to generate the java interface.
What do you think?
Thanks,
Raymond
--------------------------------------------------
From: "Giorgio Zoppi" <[EMAIL PROTECTED]>
Sent: Monday, April 07, 2008 2:30 PM
To: <tuscany-dev@ws.apache.org>
Subject: Re: [jira] Created: (TUSCANY-2207) First steps towards Axis MTOM
Support
About this topic. I'd like to ask somethings that tomorrow i wish to
implement.
The Axis MTOM at client side is easy:
1) If you enable in Axis ServiceClient's Options whenever you send a
SOAP Envelope
with base64encode. It becomes MTOM attachment.
Here I've a question.
If enableMTOM is enabled should i convert to base64 current SOAP
Envelope, replacing
current nodes with OMText containing base64, so that the support will
be able to MTOMize it? (I think NO, but I'd like to have confirm on
this).
2) Axis recognizes automatically all incoming MTOM at server side.
More difficult (but a just bit more) is about outgoing messages. From
axis docs it seems
that you should enable it in configuration. My idea is to enable it
optionally.
With this:
<parameter name="enableMTOM">optional</parameter>
Axis2 will respond with a MTOMised message if the request message was
a mtomised message. Axis2 will respond with a non-MTOMised message if
the request message was a non-mtomised message. Also this does not
take in to the account whether there is an attachment outgoing message
or not.
Is that ok for you?
Ciao,
Giorgio.
---
Giorgio Zoppi [EMAIL PROTECTED]
You're not your job. You're not how much money you have in the bank.
You're not the car you drive. You're not the contents of your wallet.
You're not your fucking khakis. You're the all-singing, all-dancing
crap of the world. - Tyler Durden (Fight Club)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
