Re: [mdr-users] Invalid sub-element: UML:TaggedValue

Chris K Wensel <[email protected]> Tue, 1 May 2007 12:18:42 -0700
Newsgroups gmane.comp.java.netbeans.modules.mdr.user
Message-ID <[email protected]>
found the issue. looks likely to be either related to an outstanding  
bug I have with EA or a new one.

seems in some cases, they are dropping a UML:TaggedValue element  
directly inside an UML:Association element without the  
UML:ModelElement.taggedValue element.

if interested, this xslt did most of the work

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"  
version="1.0" xmlns:UML="org.omg.xmi.namespace.UML">

     <!-- disable default passthrough template -->
     <xsl:template match="text()"/>

     <xsl:template match="/">
         <xsl:apply-templates/>
     </xsl:template>

     <xsl:template match="comment()"/>

     <xsl:template match="UML:TaggedValue">
         <xsl:copy-of select="name(parent::*)"/><xsl:text>  </ 
xsl:text><xsl:value-of select="parent::*/@xmi.id"/>
         <xsl:text>
         </xsl:text>
     </xsl:template>

</xsl:stylesheet>

via:
xsltproc tagged.xslt output.xml | tr -d "\t" | sort | uniq

cheers,
ckw

On May 1, 2007, at 12:00 PM, Chris K Wensel wrote:

> not looking good..
>
>  ./argouml.sh
> org.netbeans.lib.jmi.util.DebugException: Invalid sub-element:  
> UML:TaggedValue
>         at org.netbeans.lib.jmi.xmi.XmiElement 
> $Instance.startSubElement(XmiElement.java:508)
>         at org.netbeans.lib.jmi.xmi.XmiSAXReader.startElement 
> (XmiSAXReader.java:219)
>         at  
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElem 
> ent(AbstractSAXParser.java:501)
>         at  
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl 
> .scanStartElement(XMLDocumentFragmentScannerImpl.java:1357)
>         at  
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl 
> $FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2741)
>         at  
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next 
> (XMLDocumentScannerImpl.java:645)
>         at  
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl 
> .scanDocument(XMLDocumentFragmentScannerImpl.java:508)
>         at  
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse 
> (XML11Configuration.java:807)
>         at  
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse 
> (XML11Configuration.java:737)
>         at  
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse 
> (XMLParser.java:107)
>         at  
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse 
> (AbstractSAXParser.java:1205)
>         at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl 
> $JAXPSAXParser.parse(SAXParserImpl.java:522)
>         at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
>         at org.netbeans.lib.jmi.xmi.XmiSAXReader.read 
> (XmiSAXReader.java:136)
>         at org.netbeans.lib.jmi.xmi.XmiSAXReader.read 
> (XmiSAXReader.java:107)
>         at org.netbeans.lib.jmi.xmi.SAXReader.read(SAXReader.java:77)
>         at org.netbeans.lib.jmi.xmi.SAXReader.read(SAXReader.java:70)
>         at org.argouml.model.mdr.XmiReaderImpl.parse 
> (XmiReaderImpl.java:205)
>         at  
> org.argouml.persistence.ModelMemberFilePersister.readModels 
> (ModelMemberFilePersister.java:283)
>         at org.argouml.persistence.XmiFilePersister.doLoad 
> (XmiFilePersister.java:264)
>         at org.argouml.ui.ProjectBrowser.loadProject 
> (ProjectBrowser.java:1479)
>         at org.argouml.swingext.LoadSwingWorker.construct 
> (LoadSwingWorker.java:68)
>         at org.argouml.swingext.SwingWorker.doConstruct 
> (SwingWorker.java:129)
>         at org.argouml.swingext.SwingWorker$2.run(SwingWorker.java: 
> 257)
>         at java.lang.Thread.run(Thread.java:637)
>
>
>
>
>
> On May 1, 2007, at 11:53 AM, Tom Morris wrote:
>
>>> seems argo isn't reporting anything useful either.
>>
>> I know for ArgoUML we don't (yet) hook the NetBeans error logger,  
>> so MDR is
>> going to be spitting this info out on the console.  You'll need to  
>> start
>> ArgoUML from the command line to see it.
>>
>> Tom
>