To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
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.
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.
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!
What’s the problem with xmlbeans ?