| building XSDComplexTypeDefinition programmatically [message #44838] |
Wed, 19 May 2004 14:41  |
Eclipse User |
|
|
|
Originally posted by: hoe.zurich.ibm.com
I've written some code to build an XSDComplexTypeDefinition from scratch
by calling to XSDFactory, setting a name, content, etc.
Do I also have to build a DOM representation and pass it into
setElement, or is this done somewhere automatically?
The issue is that my type seems to work fine for current purposes, but
that its element remains null even after a call to updateElement. Since
the XSDComplexTypeDefinition knows its name, etc., I would assume/hope
that it can build its DOM representation by itself.
Thanks for your help,
Christian
|
|
|
| Re: building XSDComplexTypeDefinition programmatically [message #44866 is a reply to message #44838] |
Wed, 19 May 2004 15:49  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Christian,
No, the DOM can be created for you, but your complex type needs to be in an
XSDSchema in order to be able to that.
Christian Hoertnagl wrote:
> I've written some code to build an XSDComplexTypeDefinition from scratch
> by calling to XSDFactory, setting a name, content, etc.
>
> Do I also have to build a DOM representation and pass it into
> setElement, or is this done somewhere automatically?
>
> The issue is that my type seems to work fine for current purposes, but
> that its element remains null even after a call to updateElement. Since
> the XSDComplexTypeDefinition knows its name, etc., I would assume/hope
> that it can build its DOM representation by itself.
>
> Thanks for your help,
> Christian
|
|
|
|
| Re: building XSDComplexTypeDefinition programmatically [message #587232 is a reply to message #44838] |
Wed, 19 May 2004 15:49 |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Christian,
No, the DOM can be created for you, but your complex type needs to be in an
XSDSchema in order to be able to that.
Christian Hoertnagl wrote:
> I've written some code to build an XSDComplexTypeDefinition from scratch
> by calling to XSDFactory, setting a name, content, etc.
>
> Do I also have to build a DOM representation and pass it into
> setElement, or is this done somewhere automatically?
>
> The issue is that my type seems to work fine for current purposes, but
> that its element remains null even after a call to updateElement. Since
> the XSDComplexTypeDefinition knows its name, etc., I would assume/hope
> that it can build its DOM representation by itself.
>
> Thanks for your help,
> Christian
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Powered by
FUDForum. Page generated in 0.02837 seconds
] 
Search
Help
Register
Login
Home
