I've created JIRA 747 to record this. On 21/09/06, Simon Laws <[EMAIL PROTECTED]> wrote:
On 9/21/06, Geoffrey Winn <[EMAIL PROTECTED]> wrote: > > I won't be able to do anything about this until the week after next at the > earliest (ie early October) - but even then I have other commitments. I'll > try to find some time to look at it then. > > Regards, > > Geoff. > > On 21/09/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > > > Geoffrey Winn wrote: > > > I spoke to Ed about this and it seems that when there is no type > > > information > > > available, the XML parser makes a series of assumptions about the > > > structure > > > of the incoming data (for example all elements are assumed to be > > > repeating). > > > Of course, these assumptions are not always correct. It also means > > > that, for > > > example, things that you think of as single valued or simple can be > > > represented as multi-valued or by a data object. The implementation > _is_ > > > flawed but it shouldn't be as bad as your example suggests. So yes it > > > is a > > > bug, although even when fixed it may not give quite what you > > want/expect. > > > > > > On 07/09/06, Jean-Sebastien Delfino < [EMAIL PROTECTED]> wrote: > > >> > > >> Well, I can load it, but it's desperately empty :) > > >> > > >> Given the following XML: > > >> > > <customer><firstName>Jane</firstName><lastName>Doe</lastName></customer> > > >> > > >> I have no XSD for this document, and don't want to have one or have > to > > >> define specific SDO types for it. I just want to load this XML into > an > > >> SDO DataObject. > > >> > > >> XMLDocumentPtr doc = XMLHelper::load(xml); > > >> gives me an XMLDocumentPtr with no root DataObject. > > >> > > >> char* xml = XMLHelper::save(doc); > > >> gives me this: > > >> <?xml version="1.0" encoding="UTF-8"?> > > >> > > >> Is this supported by our SDO/C++ implementation? or is it a bug? > > >> > > >> -- > > >> Jean-Sebastien > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >> For additional commands, e-mail: [EMAIL PROTECTED] > > >> > > >> > > > > > Do you guys have any update on this one? What would it take to fix it? > > As Simon said earlier in this thread, getting open content to work would > > be really handy for script based applications where interfaces and > > operations are not always known in advance. > > > > Thanks, > > > > -- > > Jean-Sebastien > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > I forgot to come back on this one. Sorry about that. What I found was confirmed by Geoff so I cheated to get round it. For a sample I needed to do (Implementing a simple JSON DAS) I defined a single type in the model that had open content and then read in each element in the JSON tree in turn giving it this type in order to create an SDO. I didn't try reading in an XML file using this approach but it would be interesting to see if you can make it work somehow. Of course you end up with an SDO with no useful type information but for my purposes that was OK. I have to get on a train in a bit so I'll give it a go S
