Hi Stefan, sounds good, I'll integrate a new build into AndroMDA. Thanks! Chad
----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 14, 2004 2:42 AM Subject: [Andromda-user] NetBeans MDR error messages > Hi, > > due to the problems we had with ARIS XMI exports and AndroMDA I asked the > NetBeans MDR user mailing list for support. (Thanks to Chad for the hint to > ask them for help!) > They could help localizing where the errors were in the ARIS XMI export and > improved the error messages that MDR provides when loading an XMI file. See > below for more details. > > So probably it would be interesting to integrate a new build of the MDR. > > Regards > Stefan > > > ----- Weitergeleitet von Stefan Scheidt/OP-Gummersbach am 14.06.2004 08:43 > ----- > |--------+-----------------------> > | | Martin Matula| > | | <Martin.Matul| > | | [EMAIL PROTECTED]> | > | | | > | | 13.06.2004 | > | | 15:03 | > | | Bitte | > | | antworten an | > | | users | > | | | > |--------+-----------------------> > >--------------------------------------------------------------------------- ---------------------------------------------| > | | > | An: [EMAIL PROTECTED] | > | Kopie: | > | Thema: Re: [mdr-users] Antwort: Re: [mdr-users] Antwort: Re: [mdr-users] Using MDR with ARIS UML Designer | > >--------------------------------------------------------------------------- ---------------------------------------------| > > > > > Hi Stefan, > I did fix the message - that's how I found where the bug is - now it > correctly prints out the name of the reference and also the approximate > line where the error ocurred (the line is not exact - it points to the > closing tag of the element that caused the error - the reason is that > XMI reader collects the element content and adds the data to the MDR > when it reaches the closing tag - that's when the error occurs). > The changes are however not made in the version of MDR that is available > for NetBeans 3.6. So you will have to use the standalone version to get > these better messages. One easy way to do it is to try to load your UML > model using UML2MOF tool - that should give you better error messages. > Regards, > Martin > > [EMAIL PROTECTED] wrote: > > > Hello Martin, > > > > thank you very much for your help! I found all occurences of that kind > and > > after deleting the dublicated references the import works fine. > > > > One last question: Is there any way to get more debug messages on the > > import process, e.g. where in the XMI file a problem occurs? That would > be > > very helpful in our process... > > > > Regards > > Stefan > > > > > > > > > > |--------+-----------------------> > > | | Martin Matula| > > | | <Martin.Matul| > > | | [EMAIL PROTECTED]> | > > | | | > > | | 11.06.2004 | > > | | 01:09 | > > | | Bitte | > > | | antworten an | > > | | users | > > | | | > > |--------+-----------------------> > > > > -------------------------------------------------------------------------- ----------------------------------------------| > > > | > | > > | An: [EMAIL PROTECTED] > | > > | Kopie: > | > > | Thema: Re: [mdr-users] Antwort: Re: [mdr-users] Using MDR with > ARIS UML Designer | > > > > -------------------------------------------------------------------------- ----------------------------------------------| > > > > > > > > > > > Hi Stefan, > > the problem with your XMI is that the operation reference is mentioned > > twice for the same element. Here is an example (lines 50-59 from your > XMI): > > > > <UML:CallEvent name="Neues Call Event" xmi.id="ID.3u----8-----p--" > > xmi.uuid="96e07ae2-abd4-11d8-1068-00e000f95533" > > operation="ID.iy----7-----p--"> > > <UML:CallEvent.operation> > > <UML:Operation xmi.idref="ID.iy----7-----p--"> > > <UML:BehavioralFeature.parameter> > > <UML:Parameter xmi.idref="ID.iq----7-----p--"> > > </UML:Parameter> > > </UML:BehavioralFeature.parameter> > > </UML:Operation> > > </UML:CallEvent.operation> > > > > As you can see, the operation reference is set twice - once using > > "operation" attribute in UML:CallEvent element, the second time using > > <UML:CallEven.operation> element. The second occurence is wrong. The > > operation should not be serialized within the UML:CallEven.operation > > node, since the operation reference is not composite. The > > <UML:Operation> element corresponding to a given operation should be > > serialized inside of its composite (under an attribute or composite > > reference node) and it should be referenced by operation reference only > > using the xmi.id (i.e. using the attribute "operation" in <UML:CallEven> > > element - which is already the case). It seems that the operation > > corresponds to EmployeeController.getEmployees() (given its xmi.id). > > Since it is already serialized correctly within its composite > > (EmployeeController class - lines 22-27 of your XMI), the only thing you > > need to do is to remove the <UML:CallEvent.operation> element from the > > above piece of XMI. So only the first line should remain. I guess there > > will be other ocurrences of this bug - you will have to remove them all. > > Regards, > > Martin > > > > [EMAIL PROTECTED] wrote: > > > > > >>Hello Martin, > >> > >>thank you very much for your quick response. Find enclosed an ARIS 6.2.1 > >>XMI export of a small model. I added some GIF-Exports of the diagrams > too. > >>The problem occured after adding an UML Activity Graph, which has a Class > >>as it's context. So I guess the problem must be somewhere there... > >> > >>The exception that occurs is > >> > >>org.netbeans.lib.jmi.util.DebugException: Cannot set amulti-value to a > >>non-multivalued reference:Reference$Impl ID: .:0000000000000433 MID: > >>.:000000000000022F OPCKG: .:00000000000002B5 > >> at > >>org.netbeans.lib.jmi.xmi.XmiElement$Instance.setReferenceValues(XmiElement .java:705) > > > > > > >>... > >> > >>Regards and thank you very much in advance. > >>Stefan > >> > >>P.S.: We have quite good connections to the ARIS UML Designer developer > >>team at IDS Scheer (http://www.ids-scheer.com/). So if you find any bugs > > > > in > > > >>the way ARIS produces its XMI exports we can send this directly to the > > > > ARIS > > > >>developers... > >> > >>-- > >> > >>OPITZ CONSULTING GmbH > >>Stefan Scheidt - Dipl.-Math. - Bereichsleiter > >>Telefon: +49 2261 6001-0 Mobil: +49 173 7252423 > >>http://www.opitz-consulting.de > >> > >>(See attached file: helloapp.jar) > >> > >> > >> > >>|--------+-----------------------> > >>| | Martin Matula| > >>| | <Martin.Matul| > >>| | [EMAIL PROTECTED]> | > >>| | | > >>| | 04.06.2004 | > >>| | 15:25 | > >>| | Bitte | > >>| | antworten an | > >>| | users | > >>| | | > >>|--------+-----------------------> > >> > > > > > > -------------------------------------------------------------------------- ----------------------------------------------| > > > > > > >> | > > > > | > > > >> | An: [EMAIL PROTECTED] > > > > | > > > >> | Kopie: > > > > | > > > >> | Thema: Re: [mdr-users] Using MDR with ARIS UML Designer > > > > | > > > >> > > > > > > -------------------------------------------------------------------------- ----------------------------------------------| > > > > > > >> > >> > >> > >>The exception indicates that in your XMI there are multiple values for a > >>reference that is only single-valued. I can try to make the message more > >>descriptive. It would be nice if you could send me a small model (that > >>fails in this way) as a testcase so that I can try it out. > >>Thanks, > >>Martin > >> > >>[EMAIL PROTECTED] wrote: > >> > >> > >> > >> > >>>Hi everybody, > >>> > >>>first of all I'm quite new to MDR so please forgive an stupit > > > > questions... > > > >>>(and my quite bad english...) > >>> > >>>I try to use the ARIS UML Designer together with the MDA tool AndroMDA > >>> > >>> > >> > >>(see > >> > >> > >> > >>>team.andromda.org). > >>>In short: AndroMDA uses MDR to load XMI exports of UML tools and then > use > >>>the model to generate code from it. > >>> > >>>Now my problem is that the ARIS UML Designer export and MDR doesn't fit > >>>together... Unfortunatly the only error message I get is: > >>> > >>>org.netbeans.lib.jmi.util.DebugException: Cannot set a multi-value to a > >>>non-multivalued reference:Reference$Impl ID: .:0000000000000433 MID: > >>>.:000000000000022F OPCKG: .:00000000000002B5 > >>> at > >>>org.netbeans.lib.jmi.xmi.XmiElement$Instance.setReferenceValues(XmiElemen t.java:705) > > > > > > >>> > >> > >> > >>> at > >>>org.netbeans.lib.jmi.xmi.XmiElement$Instance.receiveValue(XmiElement.java :729) > > > > > > >>> > >> > >> > >>> at > >>>org.netbeans.lib.jmi.xmi.XmiElement$ObjectValues.endElement(XmiElement.ja va:1476) > > > > > > >>> > >> > >> > >>> at > >>>org.netbeans.lib.jmi.xmi.XmiSAXReader.endElement(XmiSAXReader.java:256) > >>> > >>>Is there any way to get more detailed error messages about what's wrong > >>>with the ARIS XMI export? Due to the vendor the ARIS XMI export is > >>>complient to XMI 1.1 and UML 1.4, the XMI export file starts with > >>> > >>><XMI xmi.version="1.1" xmlns:UML="//org.omg/UML/1.4"> > >>> <XMI.header> > >>> <XMI.documentation> > >>> <XMI.exporter>ARIS UML Designer</XMI.exporter> > >>> <XMI.exporterVersion>2.0</XMI.exporterVersion> > >>> </XMI.documentation> > >>> <XMI.metamodel xmi.name="UML" xmi.version="1.4"/> > >>> </XMI.header> > >>> <XMI.content> > >>>... > >>> > >>>The metamodel used is "M2_DiagramInterchangeModel.xml" which can be > found > >>>in a JAR file "jmiuml-1.4di.jar". > >>> > >>>Does anyone have any ideas how to get more information on the problem? > >>>Any help would be very welcome. > >>> > >>>Regards > >>>Stefan > >>> > >>> > >>> > >>> > >>> > >> > >> > >> > >> > >> > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the new InstallShield X. > From Windows to Linux, servers to mobile, InstallShield X is the > one installation-authoring solution that does it all. Learn more and > evaluate today! http://www.installshield.com/Dev2Dev/0504 > _______________________________________________ > Andromda-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/andromda-user ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
