Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » Re: Plugin classes conflict
Re: Plugin classes conflict [message #101689] Tue, 20 November 2007 13:28 Go to next message
Paul Webster is currently offline Paul WebsterFriend
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

Vikram wrote:
> Hi,
>
> I have a custom plugin that wraps Jacorb CORBA classes.
>
> I have another plugin that uses these classes at runtime.
>
> This setup used to work on eclipse 3.2 (JDK1.5) . Since I have ported to
> eclipse 3.3(JDK 1.5),
> I get java.lang.VerifyError at runtime.
>
> I think this is occuring due to common interfaces org.omg.* in both the JDK
> and the JacORB jars.
>
> I tried to resolve this issue by not exporting the common interfaces in the
> JacORB plugin - but then I run into
> ClassCast exceptions.
>
> What is the mechanism for overriding JDK classes in eclipse plug-in
> development environment ?

Re-directed to eclipse.technology.equinox ... they might be able to help
you over there.

PW


--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/workbench.htm


Re: Plugin classes conflict [message #101701 is a reply to message #101689] Tue, 20 November 2007 14:44 Go to previous messageGo to next message
Simon Kaegi is currently offline Simon KaegiFriend
Messages: 381
Registered: July 2009
Senior Member
Try adding specific "versions" to you imports and exports.

Without putting attributes (like version) on your imports you're effectively
saying bind me to whatever export satisfies my requirements
Barring any extra information the OSGi resolver will prefer binding your
imports to the version from the JDK to promote sharing of the same package
definitions.

HTH
-Simon


"Paul Webster" <pwebster@ca.ibm.com> wrote in message
news:fhumuk$e0c$1@build.eclipse.org...
> Vikram wrote:
>> Hi,
>>
>> I have a custom plugin that wraps Jacorb CORBA classes.
>>
>> I have another plugin that uses these classes at runtime.
>>
>> This setup used to work on eclipse 3.2 (JDK1.5) . Since I have ported to
>> eclipse 3.3(JDK 1.5),
>> I get java.lang.VerifyError at runtime.
>>
>> I think this is occuring due to common interfaces org.omg.* in both the
>> JDK and the JacORB jars.
>>
>> I tried to resolve this issue by not exporting the common interfaces in
>> the JacORB plugin - but then I run into
>> ClassCast exceptions.
>>
>> What is the mechanism for overriding JDK classes in eclipse plug-in
>> development environment ?
>
> Re-directed to eclipse.technology.equinox ... they might be able to help
> you over there.
>
> PW
>
>
> --
> Paul Webster
> http://wiki.eclipse.org/Platform_Command_Framework
> http://wiki.eclipse.org/Command_Core_Expressions
> http://wiki.eclipse.org/Menu_Contributions
> http://wiki.eclipse.org/Menus_Extension_Mapping
> http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/workbench.htm
Re: Plugin classes conflict [message #101714 is a reply to message #101701] Tue, 20 November 2007 16:17 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: vb.prismtech.com

Thanks for your reply, Simon. I am not sure(don't have a clue :) ) what you
mean by putting attribute on the imports.
Can you provide more details.

Thanks,
Vikram

"Simon Kaegi" <simon_kaegi@ca.ibm.com> wrote in message
news:fhurs8$543$1@build.eclipse.org...
> Try adding specific "versions" to you imports and exports.
>
> Without putting attributes (like version) on your imports you're
> effectively saying bind me to whatever export satisfies my requirements
> Barring any extra information the OSGi resolver will prefer binding your
> imports to the version from the JDK to promote sharing of the same package
> definitions.
>
> HTH
> -Simon
>
>
> "Paul Webster" <pwebster@ca.ibm.com> wrote in message
> news:fhumuk$e0c$1@build.eclipse.org...
>> Vikram wrote:
>>> Hi,
>>>
>>> I have a custom plugin that wraps Jacorb CORBA classes.
>>>
>>> I have another plugin that uses these classes at runtime.
>>>
>>> This setup used to work on eclipse 3.2 (JDK1.5) . Since I have ported to
>>> eclipse 3.3(JDK 1.5),
>>> I get java.lang.VerifyError at runtime.
>>>
>>> I think this is occuring due to common interfaces org.omg.* in both the
>>> JDK and the JacORB jars.
>>>
>>> I tried to resolve this issue by not exporting the common interfaces in
>>> the JacORB plugin - but then I run into
>>> ClassCast exceptions.
>>>
>>> What is the mechanism for overriding JDK classes in eclipse plug-in
>>> development environment ?
>>
>> Re-directed to eclipse.technology.equinox ... they might be able to help
>> you over there.
>>
>> PW
>>
>>
>> --
>> Paul Webster
>> http://wiki.eclipse.org/Platform_Command_Framework
>> http://wiki.eclipse.org/Command_Core_Expressions
>> http://wiki.eclipse.org/Menu_Contributions
>> http://wiki.eclipse.org/Menus_Extension_Mapping
>> http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/workbench.htm
>
>
Re: Plugin classes conflict [message #101744 is a reply to message #101701] Tue, 20 November 2007 19:49 Go to previous message
Eclipse UserFriend
Originally posted by: vb.prismtech.com

I got it. I had to associate version numbers with the exported/imported
packages.
Thanks for your help.

"Simon Kaegi" <simon_kaegi@ca.ibm.com> wrote in message
news:fhurs8$543$1@build.eclipse.org...
> Try adding specific "versions" to you imports and exports.
>
> Without putting attributes (like version) on your imports you're
> effectively saying bind me to whatever export satisfies my requirements
> Barring any extra information the OSGi resolver will prefer binding your
> imports to the version from the JDK to promote sharing of the same package
> definitions.
>
> HTH
> -Simon
>
>
> "Paul Webster" <pwebster@ca.ibm.com> wrote in message
> news:fhumuk$e0c$1@build.eclipse.org...
>> Vikram wrote:
>>> Hi,
>>>
>>> I have a custom plugin that wraps Jacorb CORBA classes.
>>>
>>> I have another plugin that uses these classes at runtime.
>>>
>>> This setup used to work on eclipse 3.2 (JDK1.5) . Since I have ported to
>>> eclipse 3.3(JDK 1.5),
>>> I get java.lang.VerifyError at runtime.
>>>
>>> I think this is occuring due to common interfaces org.omg.* in both the
>>> JDK and the JacORB jars.
>>>
>>> I tried to resolve this issue by not exporting the common interfaces in
>>> the JacORB plugin - but then I run into
>>> ClassCast exceptions.
>>>
>>> What is the mechanism for overriding JDK classes in eclipse plug-in
>>> development environment ?
>>
>> Re-directed to eclipse.technology.equinox ... they might be able to help
>> you over there.
>>
>> PW
>>
>>
>> --
>> Paul Webster
>> http://wiki.eclipse.org/Platform_Command_Framework
>> http://wiki.eclipse.org/Command_Core_Expressions
>> http://wiki.eclipse.org/Menu_Contributions
>> http://wiki.eclipse.org/Menus_Extension_Mapping
>> http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/workbench.htm
>
>
Previous Topic:ESDK Europa: Error installing WTP bundle javax.servlet_2.4.0.v200706111738.jar
Next Topic:OSGi console on RCP/Exclipse application.
Goto Forum:
  


Current Time: Wed Sep 19 01:29:11 GMT 2018

Powered by FUDForum. Page generated in 0.01357 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top