Wouter Zoons wrote:
Chad implemented a feature that might help you with this, it's an XSL pipeline that can transform the input XMI and feed an updated version to andromda instead
so, if you can write an XSL that can process it so it works with ARIS then we'll gladly include it in the distribution
that way you don't need to wait for the NBMDR guys
Yep, we're hoping to solve a lot of the incompatiblity problems with XMI this way, people can submit the XSL transformations and we can include them in the distribution and then they can be transparently applied to the model before processing occurs.
-- Wouter
[EMAIL PROTECTED] wrote:
Hello guys,
it took quite a time, but we finally found the reason for a problem of
Bpm4Struts when using ARIS UML Designer. (For the first posting of this
issue see
http://www.mail-archive.com/[email protected]/msg05402.html,
followed by some conversation of Wouter and me...) As it seems, it's neither a problem of Bpm4Struts nor ARIS, but of NetBeans MDR...
Here's what we found: When using ARIS, you have to provide a value for the
tag @andromda.struts.usecase.activity, belonging to a FrontEndUseCase, to
establish the link between the use case and the activity graph. (ARIS UML
Designer dosn't permit to define a Activity Graph in the namespace of a Use
Case...)
To do this in ARIS you define a tagged definition and then use this in the
FrontEndUseCase. This results in the following XMI:
<UML:UseCase name="Ticketreservation" xmi.id="ID.9-----6-----p--" ...>
<UML:ModelElement.stereotype>
<UML:Stereotype xmi.idref="ID.c2----4-----p--"/>
</UML:ModelElement.stereotype>
<UML:ModelElement.taggedValue>
<UML:TaggedValue xmi.id="ID.10----6-----p--" type="ID.2o----5-----p--">
<UML:TaggedValue.dataValue>TicketreservationGraph</UML:TaggedValue.dataValue>
</UML:TaggedValue> </UML:ModelElement.taggedValue> </UML:UseCase>
where the UML:TaggedValue references the Tagged Definition via type type ="ID.2o----5-----p--".
***Unfortunatly the NetBeans MDR doesn't seem to resolve this reference!***
As soon as you patch the XMI-File like this:
... <UML:TaggedValue xmi.id="ID.10----6-----p--" name=" @andromda.struts.usecase.activity" type="ID.2o----5-----p--">
<UML:TaggedValue.dataValue>TicketreservationGraph</UML:TaggedValue.dataValue>
</UML:TaggedValue> ...
it works fine! We found this by comparing ARIS UML Designers XMI-Output with that of MagicDraw bit by bit...
So it seems to be a NetBeans MDR issue. I'll ask the question in the MDR users mailing list and will keep you updated...
Regards Stefan
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/andromda-user
