JAXB - useful or a hindrance?

M

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.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
474,001
Messages
2,570,255
Members
46,853
Latest member
GeorgiaSta

Latest Threads

Top