[P.G.Taboada]

Did someone here try to use Myeclipse as the AndroMDA UML tool?

just wondering…

brgds

Papick

[Riyad Kalla]

Are you running into problems using them?

[jrporter]

I am. I think this is due to AndroMDA requiring UML 1.4 but MyUML only exporting as UML 1.3.

Are there any plans to upgrade the export version in MyUML? This would be a very handy way of allowing users to customise the code generation abilities of MyEclipse…

Thanks,

Jon.

FYI, here’s the stack trace from AndroMDA:

org.netbeans.lib.jmi.util.DebugException: Element name cannot be resolved, unknown package: Foundation.Core.ModelElement.name
    at org.netbeans.lib.jmi.xmi.XmiContext.resolveElementName(XmiContext.java:527)
    at org.netbeans.lib.jmi.xmi.XmiElement$Instance.startSubElement(XmiElement.java:502)
    at org.netbeans.lib.jmi.xmi.XmiSAXReader.startElement(XmiSAXReader.java:223)
    at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at javax.xml.parsers.SAXParser.parse(Unknown Source)
    at org.netbeans.lib.jmi.xmi.XmiSAXReader.read(XmiSAXReader.java:139)
    at org.netbeans.lib.jmi.xmi.XmiSAXReader.read(XmiSAXReader.java:98)
    at org.netbeans.lib.jmi.xmi.SAXReader.read(SAXReader.java:56)
    at org.andromda.repositories.mdr.MDRepositoryFacade.loadModel(MDRepositoryFacade.java:350)
    at org.andromda.repositories.mdr.MDRepositoryFacade.readModel(MDRepositoryFacade.java:137)
    at org.andromda.core.ModelProcessor.process(ModelProcessor.java:193)
    at org.andromda.core.ModelProcessor.process(ModelProcessor.java:94)
    at org.andromda.ant.task.AndroMDAGenTask.execute(AndroMDAGenTask.java:220)
    at org.apache.tools.ant.Task.perform(Task.java:341)
    at org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:232)
    at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
    at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
    at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
    at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
    at com.werken.werkz.Goal.fire(Goal.java:639)
    at com.werken.werkz.Goal.attain(Goal.java:575)
    at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
    at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634)
    at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
    at org.apache.maven.cli.App.doMain(App.java:486)
    at org.apache.maven.cli.App.main(App.java:1215)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.werken.forehead.Forehead.run(Forehead.java:551)
    at com.werken.forehead.Forehead.main(Forehead.java:581)

[Riyad Kalla]

There are not plans right now to change the version of the UML spec that MyUML supports, possibly moving forward we may focus on the 2.0 spec, but for now 1.3 is where we are while we focus on stabalizing the tool.

[jrporter]

That’s a shame as I would have thought it would have been a useful addition to the UML to java code generation feature.

Thanks for the quick reply.

Jon.

[Riyad Kalla]

Jon,
I should clarify my statement to “There is absolutely nothing set in stone, just my personal take on the situation is <what I typed above>, but as always user demand deictates what we do”.

If you’ve been on this list long enough, you’ve learned that NOTHING we do is set in stone if user demand says otherwise, we’ve even changed entire features during our ramp up to beta builds before because user demand has been so high for some things.

[Dan Adamson]

I would be loving life if you could support UML 1.4 XMI export. This would allow us to throw away our modeling tool which I guess will continue to used because of AndroMDA’s 1.4 requirement.

The newest argouml (0.19.5+) has included this capability, so perhaps it is doable… In the meantime, I guess I will be trying argouml’s 1.3 -> 1.4 feature.

Dan

[support-michael]

From the UML development lead,

“We are continuously evaluating different approaches and windows of opportunity to upgrade the UML version and XMI support. We are very aware of Argo’s progress in this area. But it has not come without the introduction of many problems. Our immediate focus is enhancing MyUML to support Sequence Diagrams. Following that we will revisit the architecture and spec upgrade as quickly as possible.”

I hope this helps.

[tfmorris]

I’m not sure who the anonymous “UML Development lead” is, so I can’t see what bug reports he/she has filed, but the ArgoUML team is actively working to resolve any outstanding problems before the first general user release of UML 1.4 support which we expect to happen before the end of the year. If their “many problems” aren’t reflected in the issue tracking system, they should get them entered.

Support for AndroMDA is an explicit goal for the ArgoUML team and we aim to provide seamless upgrade of all old ArgoUML projects from UML 1.3 to UML 1.4, so if you can find a project which breaks the upgrade, we’d love to hear from you.

We just made our first developer release with UML 1.4 support and there are still a little half baked, but we’ve got an aggressive schedule, so we could use all the testing help that we can get. If you’ve got an interest in UML 1.4, particularly targetting AndroMDA, and you have the spare cycles to play on the bleeding edge, we’d love to have you play with the developer release at http://argouml.tigris.org/download/release0196.html. There’s even a WebStart version to get you up and running instantly. As an added bonus, this developer release (and several before it) have working Sequence Diagrams.

I’m not sure how far behind the mainline ArgoUML development MyUML lags, so I have no idea for what this implies for feature availability in their product.

Tom

[wayne]

Hi Thomas,

I provided the “many bugs comment” and didn’t intend it to be an insult or gig to the Argo team. I monitor every bug status and discussion topic on the Tigris mail lists and bug tracking system and I was responding to a user comment about Argo 0.19 abilities. I know 1st hand how hard and potentially error prone an effort it is to introduce significant features such as these being discussed.

We are very interested in Argo’s MDR and UML 1.4/XMI 1.1 support as MDA support is an ultimate objective for MyUML. Spare cycles have been hard to come by but now that ME 4.0 is out we have much more bandwidth to help test drive Argo features.

Regards,

Wayne Parrott
VP, Product Development
Genuitec, LLC

[tfmorris]

Thanks for the clarification Wayne. No offense was taken — I just wanted to make sure that you didn’t have a secret cache of problems that we didn’t know about.

As you are probably aware, we use an odd/even release numbering scheme with the 0.19.x being the developer/unstable stream. I suspect the comment that you saw was from one of the first users to try the 0.19.5 release which was our first with UML 1.4 support. Because of the significant XSLT changes that Sun made between Java 1.4 & 1.5 (and our lack of testing), no old UML 1.3 projects could be upgraded if you were running with a 1.5 JVM. We do no system test for developer releases and, as luck would have it, all developers were using JVM 1.4.x while our very first external user was, of course, using JVM 1.5. We fixed the problem the same day and cut a new 0.19.6 kit (link above) which works on both JVM 1.4 & 1.5.

There’s no question that upgrading to UML 1.4 is a significant change, but the ArgoUML team is committed to making it a successful one. Since basically no one uses UML 1.3 any more, this enhancement will open a lot of doors for users of ArgoUML and its commercial derivatives.

Tom

[P.G.Taboada]

Hi,

as I understand, there soon will be a eclipse emf repository for AndroMDA available (read it in the AndroMDA forum). So here is my question: why do you not use the Eclipse EMF UML support?
Maybe it could speed up your development…
I am sure OpenArchitectureWare (another MDSD toll) will be providing an adapter to EMF very soon.

brgds,

Papick

[P.G.Taboada]

Just for people who got curious

http://galaxy.andromda.org/forum/viewtopic.php?t=1344&highlight=emf

so its almost there. Until now Magic Draw was THE tool to use with AndroMDA, you guys could become the next – just start using EMF…

brgds,

Papick

[ghessler]

I would like to add my voice to the request for support of the 1.4 Metamodel for compatibility with AndroMDA. I really like the variety of plug-ins that MyEclipse provides, but really need the AndroMDA UML support for my projects.

[Riyad Kalla]

I notified management that our UML user base really needs AndroMDA support, keep the requests comming.

[Author]

Posts