Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Rodrigo Nascimento

Pages: 1 [2] 3
General Board / Re: Schema Composer - Editing Restrictions
« on: June 24, 2015, 12:20:10 pm »
As promised... here is my Schema Composer overview article:

Hope you find it useful!

General Board / Re: Schema Composer - Editing Restrictions
« on: June 23, 2015, 10:45:12 pm »
Hi Ian,

The restrictions will be based on how you modelled the physical class model.  In the case of a class attribute that is going to be translated as a XSD simple type, just go to respective class attribute settings and change the multiplicity.

I'm finishing my first overview of the Schema Composer tool, and will post the link here by the end of this week.

Hope it helps!


General Board / Re: How best to model different architectures
« on: June 12, 2015, 11:16:44 pm »
I agree with Paolo's view that data domain (which I prefer to call Information Domain at Enterprise Level) covers data/information aspect of Business, Application and Technology domains. I wouldn't have it under Application Architecture as it may constrain the scope of your information architecture and minimise its important role in defining and communicating the semantics used across the organisation, and its support in linking Business, Application and Technology domains.

Regarding your first question, I would have all your models in the same repository (being .eap file or database) for a better discoverability and reusability. Sparx EA gives you a lot of flexibility to organise and maintain the models. We have been managing models at package level by using XMI exports/imports and Subversion to distribute releases and merge changes.

Another suggestion on the Information Modelling side, I would prefer to use UML and BPMN models rather than ERDs and DFDs, as the formers provide you a better alignment with the business (and the laters can be derived from them). Using UML for your logical models also betters support derivation for other physical models and technologies. I wrote a post with an example how to derive XML Schemas from an Enterprise Information Model: (updated! sorry... I've put the wrong link before!)

It follows the OMG's MDA approach, which is supported by Sparx EA functionalities.

Hope it helps!

General Board / Re: Batch Job for XML Technologies -> Generate XSD
« on: May 29, 2015, 04:08:26 am »
Hi Nol,

I've tested your code and it is generating the schemaLocation for all my XSD schemas.

I have couple questions for you:

1. what EA version are you using?
2. How are you creating your XSD schemas in EA? (i.e. are you using the MDA approach? or are you manually creating the XSD models?)

Regarding your questions, the only option that the documentation says that is available at the moment is the GenGlobalElement for "Global elements for all global ComplexTypes" (a.k.a. Garden of Eden style).

IMHO, I don't think you need these options as you can programatically set the schemaLocation and you are generating all the XSD schemas anyway.  


General Board / Re: Mac OS X Installation
« on: April 08, 2015, 09:07:00 pm »
I've been using Sparx EA since version 9 running on parallels and I find that it provides seamless integration with Mac OS X.

I also tried it on other virtual machine solutions like Virtual Box and VM Ware, but I found that parallels was actually optimised to run windows under Mac OS X with minimum performance impact. It also offers a great visual integration with its 'Coherence' mode, with makes the windows apps behave like a Mac OS native app (at least from the UI perspective, there are still some other functionalities that use windows native functions - like file management that will still use Windows Explorer).

There is a good (and comprehensive) benchmark analysis on the following link:

If you run (or plan to use) other windows apps on your Mac, I would definitely recommend to take a look at the VM options.

Hope it helps!  ;)

General Board / Re: Adding new XSD data types for auto generation.
« on: March 25, 2015, 12:16:02 am »
Hi Will,

We are using a similar approach for a client. I may be able to 'partially' answer you question...  ;)

First, I need to understand if you are following the Model Driven Architecture (MDA) approach. For example, we create a Platform Independent Model when we import Erwin models into Sparx EA, then we use the MDA Transformation Template to convert it to a XSD model (Platform Specific Model - PSM). Are you using something similar?

We are using the transformation template to do the transformation of the class model data types to the XSD specific data types (i.e. char to xs:string, date to xs:date...). This can solve your data type 'mapping' issue, but I don't know how to use the restrictions for XSD models (as I never had to use them). This will lead to my next point...

Second, I would like to understand why do you nee to use length restrictions.


Bugs and Issues / Re: XSD Export - Truncating similarly named packag
« on: December 09, 2015, 10:50:54 am »
That is odd...

I have couple suggestions:

  • Check if the MDA Transformation Template script is setting the schemaLocation (just in case).
  • If not, try to populate the schemaLocation and see if you get the same error.

Another option is to use the new Schema Composer (from v12 onwards). I find it more useful for integration purposes as you can create a model subset with right level of granularity for your integration services. You can find few articles about it in my blog:

Hope it helps.

Bugs and Issues / Re: XSD Export - Truncating similarly named packag
« on: October 07, 2015, 01:13:43 am »
Few questions:

  • What Sparx EA version are you using?
  • Are you specifying the schemaLocation as a tag in your packages? Or are you using the relative-path option in the schema generation?
  • Are experiencing the same problem when you transform to XSD UML Profile?


Bugs and Issues / Re: EA 12 Schema Composer not generating XSDchoice
« on: March 25, 2015, 08:17:14 pm »
Thanks Simon!

I'm happy to help you guys regarding testing and giving feedback if you want.


Bugs and Issues / Re: EA 12 Schema Composer not generating XSDchoice
« on: March 25, 2015, 09:38:41 am »
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:

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).



Bugs and Issues / Re: EA 12 Schema Composer not generating XSDchoice
« on: March 24, 2015, 11:00:08 pm »
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.

Bugs and Issues / EA 12 Schema Composer not generating XSDchoice
« 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.


Automation Interface, Add-Ins and Tools / Re: Software AG
« on: September 24, 2015, 12:22:16 am »
Hi Chris,

Essentially, webMethods Integration Server's flow language is a visual language to specify the integration logic for a integration service. I can't see any reason for customising Sparx EA to generate this very specific type of (and proprietary) code. Technically it is possible, but you need to recreate all the development functionalities from WM Designer into Sparx EA, including the visual tools like Mapping.

Even if you heavily customise Sparx EA to generate WM Flow language code (XML), you can't guarantee that the next WM version will not change its behaviour, breaking all the work you've done in Sparx.

The approach that I usually use with my clients is to do all the integration architecture and design models in EA and  produce service contract artefacts (i.e. XSDs and WSDLs) that can be imported into WM, and then implementing the integration logic using WM Designer (Flow language).

Hope it helps.


Hi Simon,

Any luck with this one?


Thanks for the help Simon!

Any documentation or updates on this will be much appreciated!

As far as I could see, the 'exports' parameter pass the export format (i.e. XSD, JSON...) that is being requested by the SC. These export formats are defined in the 'EA_GetProfileInfo' method. I'm using them to give the option to generate both XSD and JSON schemas.

Pages: 1 [2] 3