I think that both load() and save() should demand-create the global
property if necessary. I would suggest that we wait until we get all the
SDO 2.1 open content properties support working, and then we can fix this
using it.
Frank.
Fuhwei Lwo <[EMAIL PROTECTED]> wrote on 09/27/2006 11:43:00 AM
Hi Kelvin,
Based on your experiment, that means XMLHelper.save() did not automatically
add the "fred" as a new global element to the type registry. That's why it
cannot be recognized during loading.
In this case, I suggest XMLHelper.save() throws an exception to indicate
"fred" is n
Hi Fuhwei,
sorry to take so long to get this, but I needed to experiment. I've been
adapting XSDHelperTestCase to see what we have, and I think that with the
current state of the implementation for your scenario a regeneration of the
XSD after a save would not help in being able to load the s
Concerned API: XMLHelper.save(DataObject dataObject, String rootElementURI,
String rootElementName, OutputStream outputStream)
My observation is the current implementation of this method would
automatically add the rootElementName to the namespace if it does not exist
and serialize the ne
