|
Re: Class Resolving when editting XMI attribute with EJavaClass type [message #380524 is a reply to message #380522] |
Mon, 30 April 2007 15:08 |
Ed Merks Messages: 33139 Registered: July 2009 |
Senior Member |
|
|
Ron,
Please use the EMF newsgroup for EMF-specific questions. I've added it
to the "to"list. If I understand your question correctly you are
hoping that a reference to a class such as com.example.MyType will
resolve to something in your workspace, but it's only possible to
resolve to a java.lang.Class instance that's actually in the running JVM
itself, so you should expect classes to resolve only if you have those
classes loaded in the running process.
RonPiterman wrote:
> Hi,
>
> When editting an XMI relying on an ecore module, Input of java classes
> in EJavaClass attributes cannot resolve classes from the
> wokrspace/project -
>
> How do I change that?
>
> Cheers,
> Ron
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Re: Class Resolving when editting XMI attribute with EJavaClass type [message #592428 is a reply to message #380522] |
Mon, 30 April 2007 15:08 |
Ed Merks Messages: 33139 Registered: July 2009 |
Senior Member |
|
|
Ron,
Please use the EMF newsgroup for EMF-specific questions. I've added it
to the "to"list. If I understand your question correctly you are
hoping that a reference to a class such as com.example.MyType will
resolve to something in your workspace, but it's only possible to
resolve to a java.lang.Class instance that's actually in the running JVM
itself, so you should expect classes to resolve only if you have those
classes loaded in the running process.
RonPiterman wrote:
> Hi,
>
> When editting an XMI relying on an ecore module, Input of java classes
> in EJavaClass attributes cannot resolve classes from the
> wokrspace/project -
>
> How do I change that?
>
> Cheers,
> Ron
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03169 seconds