Sparx Systems Forum
Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: jens on January 20, 2005, 07:11:36 am
-
I'm trying to export the model in XMI with the automation interface(s) (EA 4.50 build 7.40).
I'm able to load a model with the Repository interface. I also get access to the Project interface where I can use the method ExportPackageXMI. But this method requires as one parameter XMIType of type long. No valid values are defined in the help file ??!! I need at number for XMI 1.2 ...
Has anybody an Idea??
Thanks in advance
Jens
-
If anyone from Sparxsystems is reading this forum/message why do I not get a answer??
I thought this is a very easy question with a real short answer, since at least anywhere in the code of EA should the mapping of long values to XMI types be defined!!??
I'm realy disappointed!
-
Jens,
this is a user forum, not a Sparx helpline. Nevertheless Sparx staff is contributing quite a lot and they are very responsive. Either the answer to your question has been missed (which may happen) or there is no answer. If you have a license you can also ask Sparx support directly by mail.
-
Hang on, this forum doesn't work like that - see here:
http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=suggestions;action=display;num=1103289802;start=2#6.
Maybe a polite email to [email protected] requesting the appropriate enums, and pointing out that their documentation is incomplete ?
Usually works better than getting angry.
Mike.
-
Maybe a polite email to [email protected] requesting the appropriate enums, and pointing out that their documentation is incomplete ?
I already send (two) emails with no response...
Half a year ago I had some questions/bug submits to sparxsystems (regarding XMI export) which were answered very fast and helpfull!!
I thought I was a little bit helpfull to sparx on comitting bugs, but and could expect any answer? Maybe it's a pronlem that I can' t authenticate myself with the userid, since my company/IT-department does not share such information with their dump users, but that's my problem and I'm already working on it (since several days...)
this is a user forum, not a Sparx helpline
But such information could be of interrest for other users, since this forum topic is called Automation Interface... and the documentation (at that chapter) is missing some informations.
Thanks for your help
Jens
-
Hi Jens,
I agree that this topic might be useful, but as you noticed, no one else did comment on it. So likely this topic was not so important for others :-/
Your registration key can be found in the About box. I'm shure you could refer to that when sending a support request. Also keep in mind: s_h_i_t happens...
-
I guess some trial and error might get you a usable value.
First try 1,2,3,4 and see if it's enumerated.
Then maybe 12, 120, 1200, to see if it's related to 1.2.
If you get an fail code each time, you could just hit it with a loop and increment until you get a success code, check the XMI type of your exported result, and then keep going until you have found values for all required types.
Brute force, but why not ?
Then you can post the values here ;-)
-
I guess some trial and error might get you a usable value.
Thanks for that suggestion but that was what I already tried in a couple of hours before I posted my question here in the forum: it's not any value between 0 and 200, and some hex values/bits 0x01, 0x02 etc. also did not work ;D
I'm currently looking to get the username/password of my license from my IT-department to be able to write a request/question as authenitcated user ;)
When I get new informations I'll post is here!
Thanks for your comforts
Jens
-
Hi Guys,
The documentation is certainly lacking for the XMIType parameter. Apparently the only recognised value is 2, which generates XMI using the Unisys/Rose format. All other values result in EA's default XMI. We've discussed the possibility of retrofitting a set of documented values to allow for exporting to the other supported XMI formats, 1.2, 1.0 etc. So you would call something like :
proj.ExportPackageXMI(Pkg.PackageGuid, EA12, ...)
Jens, thanks for your patience in this regard and my apologies for a delayed response. Hopefully the updated API will prove useful.
Regards,
Ben
-
Thank you Ben for your answer!
Now knowing that trial and error approaches will never succeed I'm curious about your next release(s) :D
The automation support of XMI 1.2 will be very helpfull for us: we are using AndroMDA (http://AndroMDA.org) for our development of a J2EE app. Since we are using it on calling an ANT task, with an additional EA-Export-ANT-Task we won't need any manual export on EA side, which would be very comfortable ;)
Regards,
Jens