2008/4/11, Raymond Feng <[EMAIL PROTECTED]>: 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.
I have to read it. 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); } I have a more a real use-case based on DICOM, which I'm working now in another platform. http://it.wikipedia.org/wiki/DICOM http://www.gbooksoft.com/ Imagine a service which has as input a DICOM image and it needs a transformation, in order to discover problems. We can start from a WSDL and use wsimport to generate the java interface. > > What do you think? That's ok for me. Ciao, Giorgio. --- Giorgio Zoppi [EMAIL PROTECTED]
