Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: Rodrigo Nascimento on March 24, 2015, 10:11:16 pm
-
I've been trying to use the new Schema Composer functionality from EA 12 as it helps me in the file generation of my XSD models.
Unfortunately, I have a critical issue that is preventing me to use this functionality for my clients. During the file generation, the schema composer does not recognise the class with stereotype XSDchoice and generates the respective class as a Complex Type. If I use the 'old' Generate XML Schema function, it works well.
I already contacted the support, but with no response yet. Therefore I would like to know if someone else has faced this issue.
Rodrigo
-
Not really - http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1371721807
q.
-
I'm sorry about the confusion qwerty! I've mentioned the wrong functionality... It is not the Schema Generator.... I'm talking about the new Schema Composer!
This issue is not related to the link you've mentioned... although, I think I may have a solution for that problem... I will put some comments there...
I've updated the subject and my original text.
-
My bad. I just read XSD and got the wrong train ;)
q.
-
The schema composer feature isn't intended to generate from a model using all the xsd stereotypes (although it could be made to.)
The primary purpose is so that industry standard class models can be generated as schemas according the the standards set out for generating schemas usually by the same organization that defines the class model.
It can also be useful for individual users by allowing them to model a class model, and then simply generate a consistent schema (in one of a variety of ways) based on that model or portions of it.
If you're not happy with the available formats, hooks are available for add-ins to generate a custom format (or multiple formats that the user can select from.) There's even a sample add-in in the Code Samples directory of your install. Finally, there is also the option for any selected output to be overridden using a script.
If you want to use the schema composer with an xsd model, you could use either of the last two methods described to make it happen. However, think about whether you are using the right tool for the job.
-
Hi Simon,
Thank you for your response.
I understand your point, but this kind of limitation should be clear in the functionality description. In your website it says that the tool support Generic XSD, which gives the impression that non-standard based models are also a priority. I'm probably not the only one to expect that product enhancements would carry on with the same behaviour.
For a long time I had clients giving up from modelling canonical models in EA and using other tools (i.e. Altova XML Spy or Visual Paradigm), which has been a real pain for me and my colleagues as we try to use Sparx EA as the only modelling tool for Enterprise Information Modelling and respective derivation of XSDs for Integration services. This give us more control over change due the benefit of traceability.
I know that you've mentioned we can use scripts and add-ins, but this is not usually welcomed from my clients' perspective as they prefer 'out-of-the-box' functionalities to avoid problems with support and upgrades.
Regarding your point about what would be the right tool for the job, I was expecting it to be the Schema Composer. This is because its main functionality, create model subset, is something that we are doing by using the 'Create Subset' functionality from Altova XML Spy, and it does the job well (but it is not great to use 2 different tools to do this job).
If you are interested, I've written an article that mentions some of these issues with the respective context and workarounds:
http://connection.rnascimento.com/2015/03/23/an-approach-to-implement-class-specialisation-in-xml-schemas-xsd/
My main message here is that this is an amazing functionality that needs just a few adjustments to be used as great selling point (for you and for me), and potentially replace other competitor (e.g. as I've said, we are only using XML Spy because of the Create Subset functionality).
Regards,
Rodrigo
-
I'll pass that on. Personally I wasn't aware of XML Spy having a Create Subset functionality.
For now, the feature you want isn't there. I can see that it is a potential new direction to take that feature though.
-
Thanks Simon!
I'm happy to help you guys regarding testing and giving feedback if you want.
Regards,
Rodrigo
-
Just wondering if EA 13 corrected this issue in Schema Composer. I would also like to add my opinion that Sparx definately DID push Schema Composer as a handy XSD production tool. I am just starting to use it and I can immediately see the confusion it causes by not natively supporting the full XSDSchema types. Odd to come so close to a perfect product functionality and stop short! I hope Sparx pays attention to this and realizes the benefits of a job well done.
-
No, there has been no development by us to using the schema composer with the XSD UML profile.