Hi, Fredrik,
both things shouldn't be technically too difficult. I'll start with
the ID/IDREF thing, we may return to the xjc:dom implementation later.
Forgetting for a moment, that the actual bean classes need changes,
I'll suggest that we start with validating the IDREF's. We'll later
see, that this is actually most of the work, if we do it right.
If an object has embedded ID/IDREF's, then its generated SAX handler
needs two additional objects:
- A Map for storing the ID's and and the elements, to which are
being mapped. An
element is added to this Map, whenever the SAX handler detects an
ID. The Map
keys are the ID's and the Map elements are the associated elements.
- A List for storing the IDREF's. Whenever the SAX handler detects
an IDREF, then
it adds an implementation of the interface
interface IDREF {
void validate(Map pIds) throws SAXException;
}
The idea is, that the SAX handler will invoke all the IDREF's
within endDocument().
Obviously, if the IDREF implementation is a suitable inner class,
then it can not
only validate the reference, but invoke a proper setter as well.
For that first step, you should be able to work within the class
DriverSGImpl and its subclasses only, so a deeper understanding of all
the JaxMe details shouldn't be required.
In any case, regards for the hint, that we do not meet the SPEC's in
that particular point.
Jochen
--
What are the first steps on the moon, compared to your child's?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
