Eclipse Community Forums: Remote Application Platform (RAP)

Home » Eclipse Projects » Remote Application Platform (RAP) » Endorsed libraries(how to add endorsed libs in an RAP app)

Show: Today's Messages :: Show Polls :: Message Navigator

Endorsed libraries [message #507458]

Wed, 13 January 2010 15:00

Opfermann C

Messages: 53
Registered: July 2009
Location: Annecy

Member

Hi all,

I'm transforming an RCP application into an RAP application and I'm getting the following problem.
My RCP application uses endorsed libraries to call EJB on a Websphere Application Server.
So, in RAP, how do I add these endorsed libs ? I tried to add them like standard libraries but it doesn't work.

Thank in advance,

Cédric

Report message to a moderator

Re: Endorsed libraries [message #507509 is a reply to message #507458]

Wed, 13 January 2010 17:45

Rüdiger Herrmann

Messages: 581
Registered: July 2009

Senior Member

Cedric,

I not sure what the actual problem is. What prevents you from handling
endorsed librarys the same way as you do in RCP?
What so you mean with "add them like standard libraries"?

Regards
Rüdiger
--
Rüdiger Herrmann
http://eclipsesource.com

On 13.01.2010 16:00, Opfermann C wrote:
> Hi all,
>
> I'm transforming an RCP application into an RAP application and I'm
> getting the following problem.
> My RCP application uses endorsed libraries to call EJB on a Websphere
> Application Server.
> So, in RAP, how do I add these endorsed libs ? I tried to add them like
> standard libraries but it doesn't work.
>
> Thank in advance,
>
> Cédric

Report message to a moderator

Re: Endorsed libraries [message #507519 is a reply to message #507509]

Wed, 13 January 2010 18:27

Opfermann C

Messages: 53
Registered: July 2009
Location: Annecy

Member

On my RCP application, I add endorsed libraries with "-Djava.endorsed.dirs" what I cannot do on the RAP application.

Actually my problem is to call an EJB from the RAP application, both are deployed on the same WAS instance.
When I try to call the EJB I get a class not found exception on WsnInitialContextFactory which is annoning because this class exists in the IBM JVM of the WAS server.
To handle this EJB call in RCP, we use the endorsed libraries because we are on a Sun JVM and we need all the WAS stuff to make the call (endorsed+ext WAS libs).

I have two options to solve this.
I can find why the WsnInitialContextfactory is no found by the classloader (possibly an OSGI issue ?)
or I can use the endorsed libraries, the same way as RCP.

I don't know if it's clear but it's a bit complicated.

Report message to a moderator

Re: Endorsed libraries [message #507577 is a reply to message #507519]

Wed, 13 January 2010 21:30

Rüdiger Herrmann

Messages: 581
Registered: July 2009

Senior Member

On 13.01.2010 19:27, Opfermann C wrote:
> On my RCP application, I add endorsed libraries with
> "-Djava.endorsed.dirs" what I cannot do on the RAP application.
This depends on how you deploy the RAP application. When deploying as a
standalone Equinox app, you can do the same as with your RCP
application. But I understand that you may not be free to chose the
deployment scenario.

>
> Actually my problem is to call an EJB from the RAP application, both are
> deployed on the same WAS instance.
> When I try to call the EJB I get a class not found exception on
> WsnInitialContextFactory which is annoning because this class exists in
> the IBM JVM of the WAS server.
> To handle this EJB call in RCP, we use the endorsed libraries because we
> are on a Sun JVM and we need all the WAS stuff to make the call
> (endorsed+ext WAS libs).
>
> I have two options to solve this.
> I can find why the WsnInitialContextfactory is no found by the
> classloader (possibly an OSGI issue ?)
> or I can use the endorsed libraries, the same way as RCP.
From my POV, finding out why the class isn't found seems the way to go.
At least I can't help mich with WAS and how to manage endorsed libs there.

As this is nothing that is specific to RAP, have you asked on the
Equinox newsgroup? They might have faced this issue before.

>
> I don't know if it's clear but it's a bit complicated.
>

Report message to a moderator