Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community Forumsanalyziing XSDSimpleTypeDefinitions
https://www.eclipse.org/forums/index.php/mv/msg/10788/33391/#msg_33391
You may recall from your response to my previous posting concerning
serializing XSDSimpleTypeDefinition instances to XMI, you mentioned that
certain computed features were not marked as transient and being output to
the XMI file (for example, validFacets in XSDSimpleTypeDefinition). To get
around this problem I mark computed features, like validFacets, to be
transient when a new XSDSimpleTypeDefinition instance is created. This
allowed me to my save simple xsd datatypes to an XMI file. One problem I
noticed is when reading the XMI file the XSDSimpleTypeDefinition instances
that are created have an empty list for validFacets. This list gets
populated when an XSDTypeDefinition is analyzed but the deserialization of
the datatype was not enough to trigger it. My work-around for now is to
force re-analyzing whenever the setBaseTypeDefinition is called. Is there a
better way?
Dennis]]>Dennis Fuglsang2003-11-21T21:56:52-00:00Re: analyziing XSDSimpleTypeDefinitions
https://www.eclipse.org/forums/index.php/mv/msg/10788/580994/#msg_580994
It would be best if you could just call XSDSchema.update at the end since doing
type analysis is a global operation that involves looking at the whole schema
and that's not likely something you want to do as you're building a big model...
dfuglsang wrote:
> Ed,
>
> You may recall from your response to my previous posting concerning
> serializing XSDSimpleTypeDefinition instances to XMI, you mentioned that
> certain computed features were not marked as transient and being output to
> the XMI file (for example, validFacets in XSDSimpleTypeDefinition). To get
> around this problem I mark computed features, like validFacets, to be
> transient when a new XSDSimpleTypeDefinition instance is created. This
> allowed me to my save simple xsd datatypes to an XMI file. One problem I
> noticed is when reading the XMI file the XSDSimpleTypeDefinition instances
> that are created have an empty list for validFacets. This list gets
> populated when an XSDTypeDefinition is analyzed but the deserialization of
> the datatype was not enough to trigger it. My work-around for now is to
> force re-analyzing whenever the setBaseTypeDefinition is called. Is there a
> better way?
>
> Dennis]]>Ed Merks2003-11-22T11:43:47-00:00Re: analyziing XSDSimpleTypeDefinitions
https://www.eclipse.org/forums/index.php/mv/msg/10788/33446/#msg_33446
Originally posted by: merks.ca.ibm.com
Dennis,
It would be best if you could just call XSDSchema.update at the end since doing
type analysis is a global operation that involves looking at the whole schema
and that's not likely something you want to do as you're building a big model...
dfuglsang wrote:
> Ed,
>
> You may recall from your response to my previous posting concerning
> serializing XSDSimpleTypeDefinition instances to XMI, you mentioned that
> certain computed features were not marked as transient and being output to
> the XMI file (for example, validFacets in XSDSimpleTypeDefinition). To get
> around this problem I mark computed features, like validFacets, to be
> transient when a new XSDSimpleTypeDefinition instance is created. This
> allowed me to my save simple xsd datatypes to an XMI file. One problem I
> noticed is when reading the XMI file the XSDSimpleTypeDefinition instances
> that are created have an empty list for validFacets. This list gets
> populated when an XSDTypeDefinition is analyzed but the deserialization of
> the datatype was not enough to trigger it. My work-around for now is to
> force re-analyzing whenever the setBaseTypeDefinition is called. Is there a
> better way?
>
> Dennis]]>2003-11-22T11:43:47-00:00