By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,996 Members | 896 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,996 IT Pros & Developers. It's quick & easy.

JAXB - useful or a hindrance?

P: n/a
mat
I'm pondering utilising JAXB to interrogate SOAP messages defined in a
schema. However, as currently concocted the schema will likely have
to change/evolve frequently with new element types being added which
would mean having to recompile the derived-classes and, more
importantly, recode the app. I see two ways around this

a) ditch JAXB and use more general methods to interrogate the document
e.g.

getPropertyValue(String property)

as opposed to

getPropertyX()

or

b) make the schema itself more extensible
e.g. by have a more generic element type with variable
sub-elements/attributes which satisfy my needs for the forseeable
future - the only difficulty here being the forseeing.

Any advice appreciated.
Jul 17 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.