Comments on: Use JAX-B or Castor for document-style encoding? http://technology.amis.nl/2004/08/20/use-jax-b-or-castor-for/?utm_source=rss&utm_medium=rss&utm_campaign=use-jax-b-or-castor-for Fri, 12 Apr 2013 10:04:09 +0000 hourly 1 http://wordpress.org/?v=3.5.1 By: Bad Credit Car Loans Now http://technology.amis.nl/2004/08/20/use-jax-b-or-castor-for/#comment-616 Bad Credit Car Loans Now Thu, 26 Apr 2007 06:50:29 +0000 /?p=122#comment-616 Bad Credit Car Loans Now

Are you sure?

]]> By: Business Credit Card http://technology.amis.nl/2004/08/20/use-jax-b-or-castor-for/#comment-615 Business Credit Card Mon, 23 Apr 2007 18:42:26 +0000 /?p=122#comment-615 Business Credit Card

Is that a template? If not your a great designer!

]]> By: Tubas http://technology.amis.nl/2004/08/20/use-jax-b-or-castor-for/#comment-614 Tubas Fri, 20 Apr 2007 19:02:21 +0000 /?p=122#comment-614 Tubas

Is that a template? If not your a great designer!

]]> By: Adrian http://technology.amis.nl/2004/08/20/use-jax-b-or-castor-for/#comment-613 Adrian Fri, 20 Aug 2004 09:32:08 +0000 /?p=122#comment-613 xmlbeans is a superb API as long as you have a schema not a DTD for your document, which obviously is your case, too. Unfortunately, I cannot comment upon its integration with Axis, but I think you’ll probably have the same namespace ‘issues’ as the one related to Castor, mentioned by Dan.

]]> By: Zeger Hendrikse http://technology.amis.nl/2004/08/20/use-jax-b-or-castor-for/#comment-612 Zeger Hendrikse Fri, 20 Aug 2004 09:24:59 +0000 /?p=122#comment-612 No problems with xmlbeans, I think (I haven’t got experience). But if there are any arguments in favour of it (such as ease of use :-) , I’ll surely consider it an option.

]]> By: Dan Barber http://technology.amis.nl/2004/08/20/use-jax-b-or-castor-for/#comment-611 Dan Barber Fri, 20 Aug 2004 09:21:42 +0000 /?p=122#comment-611 From my experience with Castor and Axis, I would say that it works pretty well. IBM’s excellent article
provides a solid roadmap for implementing DOC/Literal. My process for managing changes in the interface
(new fields exposed in the service) is pretty simple. I make a change in the schema, run an ant target
to generate binding classes, merge generated classes with my code base, recompile and deploy. Issues
to watch out for include:

- namespaces in the schema: I found that the xml returned from the service contained namespace prefixes
for every attribute and element! I ended up removing namespace settings from within the generated classes.

- Axis bug fixes: There were a few classes in Axis that had bugs relating to Castor. I grabbed the fixes from
cvs because they weren’t included in the standard Axis distribution (can’t remember what classes were fixed).

I’m sure there are better ways to implement now. I haven’t played with JAX-B so I don’t know how easy it is.

Good Luck!

]]> By: Adrian http://technology.amis.nl/2004/08/20/use-jax-b-or-castor-for/#comment-610 Adrian Fri, 20 Aug 2004 09:12:44 +0000 /?p=122#comment-610 What’s the problem with xmlbeans ?

]]>