Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
Refactor to use OXM from Spring 3 [SWS-567] #689
Since the OXM stuff from Spring-WS has now been incorporated into Spring 3, Spring-WS will at some point need to be updated to use the OXM code from the core framework. The OXM code in the core has already moved on, and is newer than that in Spring-WS.
I am currently developing a system using Spring 3 M4 and Spring-WS 1.5.x, and I have to be very careful not to include the OXM code from Spring-WS in the build. When Spring 3 goes final, this will become increasingly problematic as prople try to use them together.
When would you propose making this leap? Perhaps a 1.6 version bump?
1 votes, 1 watchers
Werner Guttmann commented
Arjen, can you please elaborate on this subject. Are you saing that - even if we managed our Maven dependencies ourselves and carefully - it is not possible to use Spring 3.0 OXM classes with current (1.5.x) spring-ws code ?
Arjen Poutsma commented
If it works for you, that's good. I have even ran my test suite against SPR's OXM, and it seems to work fine. But it's not 'formally' supported, as I did make some minute changes to the oxm package when it moved to the core.
Kenny MacLeod commented
I've experienced occasional clashes between Spring 3 OXM and Spring-WS OXM, in particular when using the Spring 3 OXM with MVC, and the appserver happens to pick the Spring-WS OXM classes in preference. It's hard to reproduce, and hard to fix when it does happen, to the point where I try to avoud using OXM from both Spring MVC and Spring-WS in the same application.
The problem, of course, is that the Spring 3 OXM classes have evolved onwards since they were copied from Spring-WS, and if the Spring-WS versions get picked by the classloader, you get "no such method" errors and the like.