On Sat, 2010-04-24 at 15:14 +0100, Eoghan Glynn wrote:
How about using the <xs:choice> mechanism to represent the
mutually
exclusivity of NFS-specific info versus iSCSI-specific details, and have
the storage type intended be implicit from this selection?
Sounds good
So say we were to start generating the JAXB model from XML schema
(which
is what I thought you meant yesterday, though obviously I got that
backwards).
Yeah, this makes a lot of sense to me - I was struggling because I had
an XML model and was trying to make a nice Java model to represent it.
Let's leave that up to xjc and concentrate on the XML format.
We should make this switch to generating the classes from a schema ASAP
...
AFAIK the JAXB compiler is then supposed to generate code of form
ThisOrThat, e.g. getNfsSpecificOrIsciSpecific(), to represent the
one-or-t'other-ness.
That's a bit uggh, but hopefully we'll figure something out
Cheers,
Mark.