This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
bug scenario: 0) open clean MDR-Explorer 1) mof import uml 1.4 metamodel 2) instantiate uml metamodel 3) import XMI uml model 4) import java 1.0 metamodel 5) instantiate java metamodel 6) try import XMI java model -> javax.jmi.reflect.InvalidCallException at org.netbeans.mdr.handlers.PackageProxyHandler. refClass(PackageProxyHandler.java:252) at org.netbeans.lib.jmi.xmi.XmiContext. resolveElementName(XmiContext.java:557) ... note: insert in JAVA 1.0 metamodel xmi namespace tag
Created attachment 10726 [details] a java model
What is Java 1.0 metamodel? Where did you get the XMI for it? How was the java_model produced?
Created attachment 10732 [details] java metamodel
What is Java 1.0 metamodel? sorry, see new attachment. Where did you get the XMI for it? patched netbeans test java metamodel (xmi import + export rational rose, unisys plugin) How was the java_model produced? my tool
The metamodel and model work for me. Although I didn't load UML metamodel before I was trying it out. Does the exception occur only when you load and instantiate UML metamodel before that? I guess so. It seems that the problem is that you don't specify a package prefix for Core package. Now, it depends on how you load the UML metamodel. Do you load it together with the diff files provided at http://mdr.netbeans.org/metamodels.html, or you load it as is? I think that the problem occurs because of the name clash of some interfaces automatically generated for UML with interfaces generated for your metamodel of Java - there is a lot of elements with the same name (Core package, etc.) and if you do not specify a package prefix, they reside in the same java package - i.e. they are in conflict.
Does not seem to be a bug in MDR (see the comments above).