Re: xsd:any problem

2007-05-07 Thread Frank Budinsky
Hi Chris, The problem is this line of code: person.setDataObject(address:Address, address); SDO doesn't support qualified names in string (path) get/set methods. That's why it ignores the address: prefix, and simply demand-creates another Address property (PersonType:address). To

Re: xsd:any problem

2007-05-07 Thread Chris Mildebrandt
Hi Frank, I replaced my code with what you suggested: Property addressProperty = context.getXSDHelper().getGlobalProperty(http://www.example.org/Address;, Address, true); person.setDataObject(addressProperty, address); The call to setDataObject() generates the

Re: xsd:any problem

2007-05-07 Thread Frank Budinsky
Sorry, I didn't notice that your xsd:any had maxOccurs 1: xsd:any namespace=##other processContents=lax minOccurs=0 maxOccurs=unbounded/ If it was maxOccurs=1 then you could do what I suggested. Because it is many valued, however, you need to do this:

Re: xsd:any problem

2007-05-07 Thread Chris Mildebrandt
Hi Frank, Thank you so much for your help so far, your example worked. I'm learning quite a bit. I thought that would help me with my real work, but I'm seeing a different error. My schema can be found here: http://www.oasis-open.org/committees/download.php/23876/CL1_Schema.zip and here:

Re: xsd:any problem

2007-05-07 Thread Frank Budinsky
Assuming that the line numbers in your stack trace correspond to the EMF version (2.2.3) that I'm looking at, it looks to me like null is being passed into the getList() method. If so, I assume it's because this line returned null: Property addressProperty =

Re: xsd:any problem

2007-05-07 Thread Chris Mildebrandt
Hi Frank, I think I've tracked this problem down to an issue with static class generation. The common schema contains the any element in the identity element. The packageIdentity element in the packageDescriptor schema extends the identity element. Some things aren't quite right in the class

Re: xsd:any problem

2007-05-07 Thread Frank Budinsky
Hi Chris, Can you confirm that the cross-package inheritance is the problem by creating a similar subtype in the same package and see if it works? It should be pretty simple to fix this generator problem, but it would be helpful if you could provide a simple test case for us. Adding open

Re: xsd:any problem

2007-04-12 Thread Ashish Panchal
, April 11, 2007 11:12 PM Subject: Re: xsd:any problem Hi Ashish, I'm not sure what you tried, but something like this should work: body.setDataObject(typeHelper.getOpenContentProperty(the target namespace???, ServiceInput), value); Frank. Ashish Panchal [EMAIL PROTECTED] wrote on 04/11

Re: xsd:any problem

2007-04-11 Thread Frank Budinsky
Hi Ashish, I'm not sure what you tried, but something like this should work: body.setDataObject(typeHelper.getOpenContentProperty(the target namespace???, ServiceInput), value); Frank. Ashish Panchal [EMAIL PROTECTED] wrote on 04/11/2007 12:00:50 PM: Hi, Iam trying to create a