In previous articles I demonstrated how EclipseLink JAXB (MOXy) is directly integrated into the JAX-WS implementations in WebLogic (as of 12.1.1) and in GlassFish (as of 3.1.2). In this post I'll demonstrate how to leverage MOXy in any application server by using the JAX-WS Provider class.
Showing posts with label JAX-WS. Show all posts
Showing posts with label JAX-WS. Show all posts
February 15, 2013
Leveraging MOXy in your Web Service via JAX-WS Provider
February 29, 2012
GlassFish 3.1.2 is Full of MOXy (EclipseLink JAXB)
I am very happy to announce that EclipseLink JAXB (MOXy) is now a JAXB (JSR-222) provider in GlassFish 3.1.2. I would like to thank the EclipseLink and GlassFish committers for all their hard work to make this happen.
In this post I will introduce how MOXy can be leveraged to create a JAX-WS service. In future posts I will cover more of the extensions in greater detail.
In this post I will introduce how MOXy can be leveraged to create a JAX-WS service. In future posts I will cover more of the extensions in greater detail.
December 16, 2011
EclipseLink MOXy is the JAXB Provider in WebLogic Server 12c
I am very happy to announce that EclipseLink JAXB (MOXy) is now the default JAXB (JSR-222) provider in WebLogic Server 12c. I would like to thank the EclipseLink committers and the WebLogic team for all their hard work to make this happen.
In this post I will introduce how MOXy can be leveraged to create a JAX-WS service. In future posts I will cover more of the extensions in greater detail.
In this post I will introduce how MOXy can be leveraged to create a JAX-WS service. In future posts I will cover more of the extensions in greater detail.
March 23, 2011
JAXB, Web Services, and Binary Data
When an instance of a class is used with a Web Service, the JAX-WS implementation can choose to handle fields/properties that hold binary data as SOAP attachment. An attachment is a means to send the data outside of the XML message, this is done as an optimization since binary data encoded as a xs:base64Binary string could be quite large. JAXB offers a couple of annotations to control this behaviour:
- @XmlInlineBinaryData
This specifies that the binary data for this field/property must be written to the XML document as xs:base64Binary and not sent as an attachment.
- @XmlMimeType
For properties of type java.awt.Image or javax.xml.transform.Source, this annotation allows the mime type to be specified that will be used for encoding the data as bytes.
Labels:
Attachment,
JAX-WS,
JAXB,
XmlInlineBinaryData,
XmlMimeType
Subscribe to:
Posts (Atom)