[News.eclipse.technology.eclipselink] Re: EclipseLink MOXy in Spring-WS

[shaun.smith@xxxxxxxxxx (Shaun Smith)]

Hi Geert,

greyfairer wrote:

> In Shaun Smith's blog post on 
http://eclipselink.blogspot.com/2008/03/spring-252-ships-eclipselink-10m4.html, 
> he promised to show us how to integrate EclipseLink MOXy into Spring-WS as 
> a JAXB marshaller/unmarshaller. No followup has come since.

Guilty as charged--I forgot all about my promise ;-)  I'll get an example 
together up on my blog asap.

> Does anybody else use this setup? What are the dependencies we need to do 
> this? Can we use MOXy without the JPA? And how do we get started?

Right now EclipseLink code is all in one jar so while you don't need to 
use JPA you will have the classes.

> We already decided to use Spring-WS, but we didn't decide yet if we are going 
> to use JAXB(2), Castor, or anything else, ...

Spring-WS will allow you to use various technologies for 
marshalling/unmarshalling but only JAXB is a Java standard.  And the 
advantage of JAXB is that you can shop for the best implementation (which 
of course we think is EclipseLink).

> ... so I want to propose MOXy, but don't >know how to get started.

There are some introductory TopLink JAXB How-To's on the Oracle Technology 
Network [1] that haven't been ported to EclipseLink yet, but you can 
certainly take a look at them.  I think converting the code to EclipseLink 
is a matter of replacing TopLink.jar with EclipseLink.jar in the ant 
build.xml.

I'll post to the forum when the Spring-WS/EclipseLink MOXy blog is posted.

--Shaun


[1] 
http://www.oracle.com/technology/products/ias/toplink/preview/index.html