seems argo isn't reporting anything useful either.
unfortunately the powers that be won't let me share this model. and
some attempts at simplifying it has resulted in unbuggy xmi.
i'm currently attempting to generate a list of all the parent
elements TaggedValue is showing up in, in hopes of pinning the error
down.
On May 1, 2007, at 10:44 AM, Chris K Wensel wrote:
> excellent idea on using ArgoUML. i'll give that a shot real quick.
>
> if that doesn't yield anything useful, i'll see if i can whittle
> the model down and share it.
>
>
> On May 1, 2007, at 10:41 AM, Tom Morris wrote:
>
>>> also, this is all brokered through AndroMDA. but the exceptions are
>>> being thrown from netbeans jmi.
>>>
>>> any suggestions?
>>
>> MDR doesn't include the source line and column information in the
>> exception,
>> but it does know it. I think it might be spitting it out to
>> syserr or
>> someplace similar unless the AndroMDA folks have hooked into the
>> NetBeans-specific logging mechanism.
>>
>> The stack trace doesn't really include any useful information
>> other than the
>> summary, viz a TaggedValue is enclosed in something that it
>> shouldn't be.
>> You'll probably have to provide the XMI file for anyone to give
>> you any more
>> concrete feedback.
>>
>> ArgoUML uses MDR as well, so that might be a quicker way to debug
>> this
>> rather than firing up an AndroMDA build every time.
>>
>> Tom
>>
>> p.s. If you want to send me the XMI file, I can take a quick look
>> at it and
>> may be able to spot the problem.
