Home » Eclipse Projects » Rich Client Platform (RCP) » classpath
| classpath [message #460007] |
Mon, 11 December 2006 10:01  |
Eclipse User |
|
|
|
Hi,
I have an RCP that uses an external library wrapped as a plugin.
This library has classes that are available in JDK as well. How can I ensure
that the classes
in the external library are used at runtime.
(In a stand alone java app, this would be done using the Xbootclasspath
option)
Thanks,
|
|
| | |
| Re: classpath [message #460019 is a reply to message #460015] |
Mon, 11 December 2006 12:50  |
| Eclipse User |
|
|
|
Hi,
My set up is as follows:
I want to use a CORBA ORB called Jacorb with my application.
JDK has it's own implementation of CORBA which I do not want to use.
(The org.omg.CORBA.* packages are common)
I want to make sure that my application gets the Jacrob classes for which I
have created a
separate plugin.
Thanks
"Toni Menzel" <tonimenzel@gmx.de> wrote in message
news:elk3d8$olv$1@utils.eclipse.org...
> Hi,
>
> Your pointer to "Xbootclasspath" says me that you want to "force" the
> ClassLoader to load the classes from specific origins, right?
> In an OSGi Environment (and Eclipse RCP relies on that) there can be only
> one and exacly one bundle exporting the same package at any given time.
> Altough OSGi allows mutiple concurrent versions, but only one of the same
> version.
> So you never have the situation you have in naked VM environments with the
> classloader depend on the time you "declare" your dependency (=library) in
> the classpath.
>
> With this, you should not be able to load different libraries (from
> different locations) with the same exporting package by specification.
>
> Could you describe your set-up a little bit?
> So we maybe can help here.
>
> If you want to overwrite classes from the runtime itself (rt.jar) you
> could hack the bootclasspath as you are familar with - as Neil described
> in a previous posting
>
> kind regards,
> Toni
>
> Vikram schrieb:
>> Hi,
>> I have an RCP that uses an external library wrapped as a plugin.
>> This library has classes that are available in JDK as well. How can I
>> ensure that the classes
>> in the external library are used at runtime.
>> (In a stand alone java app, this would be done using the Xbootclasspath
>> option)
>>
>> Thanks,
>>
|
|
|
| Re: classpath [message #460022 is a reply to message #460019] |
Mon, 11 December 2006 14:53 |
| Eclipse User |
|
|
|
So you won't contribute the corba packages as bundles dynamciliy and
just want to make sure to have the correct implementation?
the Xbootclasspath VM option is the way to go, I think.
I don't know how and when the VM initially picks up the corba
Implementation.
If it's the bootstrapper (classloader which has null as parent), it
should count to the vm libraries from the osgi perspective. This way you
shouldn't come into into trouble.
Do you have a real problem or do you ask to ensure the assumtion?
regards,
Toni
Vikram Bhanot schrieb:
> Hi,
> Here's the setup:
> The JDK has an implementation of CORBA org.omg.CORBA packages.
> I am using Jacorb libraries, another CORBA product, which provides the
> same classes as well.
>
> Basically, at runtime I want to ensure that I get the right classes (
> Jacorb ).
>
> Thanks,
>
>
>
> "Toni Menzel" <tonimenzel@gmx.de> wrote in message
> news:<elk3d8$olv$1@utils.eclipse.org>...
>> Hi,
>>
>> Your pointer to "Xbootclasspath" says me that you want to "force" the
>> ClassLoader to load the classes from specific origins, right?
>> In an OSGi Environment (and Eclipse RCP relies on that) there can be
>> only one and exacly one bundle exporting the same package at any given
> time.
>> Altough OSGi allows mutiple concurrent versions, but only one of the
>> same version.
>> So you never have the situation you have in naked VM environments with
>
>> the classloader depend on the time you "declare" your dependency
>> (=library) in the classpath.
>>
>> With this, you should not be able to load different libraries (from
>> different locations) with the same exporting package by specification.
>>
>> Could you describe your set-up a little bit?
>> So we maybe can help here.
>>
>> If you want to overwrite classes from the runtime itself (rt.jar) you
>> could hack the bootclasspath as you are familar with - as Neil
> described
>> in a previous posting
>>
>> kind regards,
>> Toni
>>
>> Vikram schrieb:
>>> Hi,
>>> I have an RCP that uses an external library wrapped as a plugin.
>>> This library has classes that are available in JDK as well. How can
> I ensure
>>> that the classes
>>> in the external library are used at runtime.
>>> (In a stand alone java app, this would be done using the
> Xbootclasspath
>>> option)
>>>
>>> Thanks,
>>>
>>>
--
Toni Menzel
http://www.tonit.com
mailto:tonimenzel@gmx.de
Vikram schrieb:
> Hi,
> My set up is as follows:
> I want to use a CORBA ORB called Jacorb with my application.
> JDK has it's own implementation of CORBA which I do not want to use.
> (The org.omg.CORBA.* packages are common)
>
> I want to make sure that my application gets the Jacrob classes for which I
> have created a
> separate plugin.
>
> Thanks
>
>
>
>
>
>
> "Toni Menzel" <tonimenzel@gmx.de> wrote in message
> news:elk3d8$olv$1@utils.eclipse.org...
>> Hi,
>>
>> Your pointer to "Xbootclasspath" says me that you want to "force" the
>> ClassLoader to load the classes from specific origins, right?
>> In an OSGi Environment (and Eclipse RCP relies on that) there can be only
>> one and exacly one bundle exporting the same package at any given time.
>> Altough OSGi allows mutiple concurrent versions, but only one of the same
>> version.
>> So you never have the situation you have in naked VM environments with the
>> classloader depend on the time you "declare" your dependency (=library) in
>> the classpath.
>>
>> With this, you should not be able to load different libraries (from
>> different locations) with the same exporting package by specification.
>>
>> Could you describe your set-up a little bit?
>> So we maybe can help here.
>>
>> If you want to overwrite classes from the runtime itself (rt.jar) you
>> could hack the bootclasspath as you are familar with - as Neil described
>> in a previous posting
>>
>> kind regards,
>> Toni
>>
>> Vikram schrieb:
>>> Hi,
>>> I have an RCP that uses an external library wrapped as a plugin.
>>> This library has classes that are available in JDK as well. How can I
>>> ensure that the classes
>>> in the external library are used at runtime.
>>> (In a stand alone java app, this would be done using the Xbootclasspath
>>> option)
>>>
>>> Thanks,
>>>
>
|
|
|
| Re: classpath [message #460025 is a reply to message #460022] |
Mon, 11 December 2006 16:01 |
| Eclipse User |
|
|
|
I do have have a real problem.
Thank you and Neil for the responses.
"Toni Menzel" <tonimenzel@gmx.de> wrote in message
news:elkcsp$m15$1@utils.eclipse.org...
> So you won't contribute the corba packages as bundles dynamciliy and just
> want to make sure to have the correct implementation?
> the Xbootclasspath VM option is the way to go, I think.
>
> I don't know how and when the VM initially picks up the corba
> Implementation.
> If it's the bootstrapper (classloader which has null as parent), it should
> count to the vm libraries from the osgi perspective. This way you
> shouldn't come into into trouble.
>
> Do you have a real problem or do you ask to ensure the assumtion?
>
> regards,
> Toni
>
> Vikram Bhanot schrieb:
> > Hi,
> > Here's the setup:
> > The JDK has an implementation of CORBA org.omg.CORBA packages.
> > I am using Jacorb libraries, another CORBA product, which provides the
> > same classes as well.
> >
> > Basically, at runtime I want to ensure that I get the right classes (
> > Jacorb ).
> >
> > Thanks,
> >
> >
> >
> > "Toni Menzel" <tonimenzel@gmx.de> wrote in message
> > news:<elk3d8$olv$1@utils.eclipse.org>...
> >> Hi,
> >>
> >> Your pointer to "Xbootclasspath" says me that you want to "force" the
> >> ClassLoader to load the classes from specific origins, right?
> >> In an OSGi Environment (and Eclipse RCP relies on that) there can be
> >> only one and exacly one bundle exporting the same package at any given
> > time.
> >> Altough OSGi allows mutiple concurrent versions, but only one of the
> >> same version.
> >> So you never have the situation you have in naked VM environments with
> >
> >> the classloader depend on the time you "declare" your dependency
> >> (=library) in the classpath.
> >>
> >> With this, you should not be able to load different libraries (from
> >> different locations) with the same exporting package by specification.
> >>
> >> Could you describe your set-up a little bit?
> >> So we maybe can help here.
> >>
> >> If you want to overwrite classes from the runtime itself (rt.jar) you
> >> could hack the bootclasspath as you are familar with - as Neil
> > described
> >> in a previous posting
> >>
> >> kind regards,
> >> Toni
> >>
> >> Vikram schrieb:
> >>> Hi,
> >>> I have an RCP that uses an external library wrapped as a plugin.
> >>> This library has classes that are available in JDK as well. How can
> > I ensure
> >>> that the classes
> >>> in the external library are used at runtime.
> >>> (In a stand alone java app, this would be done using the
> > Xbootclasspath
> >>> option)
> >>>
> >>> Thanks,
> >>>
> >>>
>
>
> --
> Toni Menzel
> http://www.tonit.com
> mailto:tonimenzel@gmx.de
>
>
> Vikram schrieb:
>> Hi,
>> My set up is as follows:
>> I want to use a CORBA ORB called Jacorb with my application.
>> JDK has it's own implementation of CORBA which I do not want to use.
>> (The org.omg.CORBA.* packages are common)
>>
>> I want to make sure that my application gets the Jacrob classes for which
>> I have created a
>> separate plugin.
>>
>> Thanks
>>
>>
>>
>>
>>
>>
>> "Toni Menzel" <tonimenzel@gmx.de> wrote in message
>> news:elk3d8$olv$1@utils.eclipse.org...
>>> Hi,
>>>
>>> Your pointer to "Xbootclasspath" says me that you want to "force" the
>>> ClassLoader to load the classes from specific origins, right?
>>> In an OSGi Environment (and Eclipse RCP relies on that) there can be
>>> only one and exacly one bundle exporting the same package at any given
>>> time.
>>> Altough OSGi allows mutiple concurrent versions, but only one of the
>>> same version.
>>> So you never have the situation you have in naked VM environments with
>>> the classloader depend on the time you "declare" your dependency
>>> (=library) in the classpath.
>>>
>>> With this, you should not be able to load different libraries (from
>>> different locations) with the same exporting package by specification.
>>>
>>> Could you describe your set-up a little bit?
>>> So we maybe can help here.
>>>
>>> If you want to overwrite classes from the runtime itself (rt.jar) you
>>> could hack the bootclasspath as you are familar with - as Neil described
>>> in a previous posting
>>>
>>> kind regards,
>>> Toni
>>>
>>> Vikram schrieb:
>>>> Hi,
>>>> I have an RCP that uses an external library wrapped as a plugin.
>>>> This library has classes that are available in JDK as well. How can I
>>>> ensure that the classes
>>>> in the external library are used at runtime.
>>>> (In a stand alone java app, this would be done using the Xbootclasspath
>>>> option)
>>>>
>>>> Thanks,
>>>>
>>
|
|
|
Goto Forum:
Current Time: Fri Jul 04 15:30:52 EDT 2025
Powered by FUDForum. Page generated in 0.06146 seconds |
Home