|
| Re: analyziing XSDSimpleTypeDefinitions [message #33446 is a reply to message #33391] |
Sat, 22 November 2003 11:43  |
Eclipse User |
|
|
|
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
|
|
|
| Re: analyziing XSDSimpleTypeDefinitions [message #580994 is a reply to message #33391] |
Sat, 22 November 2003 11:43 |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
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
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03446 seconds
] 
Search
Help
Register
Login
Home
