By mitchp
via java.dzone.com
Published: Feb 06 2013 / 08:38
When creating webservices a lot of people have objections against using JAXB for binding XML to objects. This may be because of performance reasons, allergy to generated code or simply a philosophical belief that you should not mix document centric services with an object oriented model. Whatever the reasons for not using JAXB you have, I'll try to describe a possible alternative solution using Camel.
Tweet
SaveShareSend
Tags: how-to, java, open source, web services
-
Date and Time API changes in Java 8
-
Automatically build and include one Eclipse project into another as a JAR file
-
Deloitte, xPrize and Singularity University team up on innovation
-
How to be a good web service? Syncronous or asyncronous, let's straight!
-
Postgres Demystified
-
Your login form posts to HTTPS, but you blew it when you loaded it over HTTP
Add your comment
