Release 607

[Tjerk]

Hi Sparx,

Great work on the XML schema generation! I will look into the details next week. On forehand, I would like to press to look into the use and proper definitions of namespaces in XSDs.

Other bugfixes and new features are great too. Another one of the usefull patches  .

Thanks,
Tjerk

After first use, I found the following issues:
XSD generation

• newline character generated between <?xml?> and <xs:schema> is invalid (either a carriage return or a linefeed is missing).
  
• Generation dialog has a cancel button, close is better.
  
• Validation pass x: maybe some more information on what is verified.
  
• I'm already using namespaces (like "xs:") in the attributes, generator doesn't like this and makes them xs:string.
  
• Would be nice to include XSD as one of the languages, just as e.g. java and treat them the same. Maybe include an options window in the View/Options dialog for XSD generation.
  
• I use the <<XSDSchema>> component as a representation of a schema, am I wrong in doing so? Otherwise, I would like the XSD generation to be possible on components as well (see previous issue).
  
• Attributes & elements include classname prefix, they are already in the scope of the ComplexType and in my opinion the classname is not wanted.
  
• I get a "failed class constraint" due to the default constraints in the UML profile!
  

Property window

• MAJOR: Dropdown boxes in propertywindow cannot be edited: dropping down results in immediate fold in.

[benc]

Hi Tjerk,

Thanks for the feedback.

• The newline issue should be resolved as of build 609
  
• We'll look at the logging in some more detail- the validation passes are performed until a valid set of classes is reached according the UML profile constraints.  So if you have an XSDchoice stereotyped class that has no containing
  class, it will discard it try again.
  
• As regards namespaces- probably best to keep the prefixes as tagged values on the package.  This way you'll have a single point of control when the "prefix de jour" becomes "foo" instead of "bar".  Regarding the xs: prefix in particular- best to use the provided XSDDataTypes package.  That said, if many users prefer to include the prefix before each UML attribute, we might look at getting the schema generator to "make a guess" at what part is the namespace.  This approach could be messy though...
  

• Would be nice to include XSD as one of the languages, just as e.g. java and treat them the same. Maybe include an options window in the View/Options dialog for XSD generation.

  
  We'll have a look at this...
  

• I use the <<XSDSchema>> component as a representation of a schema, am I wrong in doing so? Otherwise, I would like the XSD generation to be possible on components as well (see previous issue).

  
  In a future release the <<XSDschema>> stereotype will be available on components- it is not currently.  Support for aggregation (and composition) connectors is coming also.
  
• The classname prefix behaviour can be turned off by using tagged values on the package or on indivual complexType classes.  The prefix helps ensure uniqueness of element names within a schema.  Useful if the xsd ever gets generated in a "Garden of Eden" style, where all elements (from all class attributes) would be declared as root elements.
  

• I get a "failed class constraint" due to the default constraints in the UML profile!

  
  There could be lots of reason for a class failing constraints from the profile.  Eg an XSDchoice class that has no owner.
  Note the constraints specified in the help file are non-negotiable- they form part of the profile.
  

[benc]

Hello again Tjerk,

On the Properties window... we've seen this behaviour occasionally and it appears to be a 3rd party software issue.
We're hunting down a work around currently- other than restarting EA...

Ben