| Equinox on Websphere and context updates [message #102566] |
Wed, 05 December 2007 18:06  |
Eclipse User |
|
|
|
Originally posted by: jacek.pospychala.pl.ibm.com
Dear Equinox,
I've heard from few sources a following concern regarding deploying
Equinox on WebSphere (as well as other app servers).
Equinox works fine there, but when installing additional bundle jars,
app server detects this (new Jar in app area) and reloads whole
application context killing Equinox instance.
Is it a known issue? Does it require any special configuration of
WebSphere, or is it rather misconfiguration of Equinox?
I'm trying to be as precise as I can, but I'm not an expert in app
servers, and it's not me who faced this problem. From my understanding,
Equinox would be fine to install bundles from remote locations, eg. by
issuing "install http://x.y.z/bundle.jar" in console. Then it would
probably make a local copy of that bundle in <configuration> area, which
is hopefully out of WebSphere surveillance. Does it make sense? Or are
there better workarounds?
Thank you for your help,
Jacek
|
|
|
|
| Re: Equinox on Websphere and context updates [message #102652 is a reply to message #102566] |
Thu, 06 December 2007 08:36  |
| Eclipse User |
|
|
|
Jacek,
I am assuming that the equinox deployment mechanism used is the Equinox
Servlet Bridge. If this is the case then there are no issues with adding
new bundles as the the OSGi working area is placed in the
WebApplications temp directory which is not monitored for file changes.
Running the Servlet Bridge in WAS 6.1 is no problem.
BTW turning on/off the monitoring of file changes is something that is
configuration per Application deployment.
Richard
Jacek Pospychala wrote:
> Dear Equinox,
>
> I've heard from few sources a following concern regarding deploying
> Equinox on WebSphere (as well as other app servers).
> Equinox works fine there, but when installing additional bundle jars,
> app server detects this (new Jar in app area) and reloads whole
> application context killing Equinox instance.
>
> Is it a known issue? Does it require any special configuration of
> WebSphere, or is it rather misconfiguration of Equinox?
>
> I'm trying to be as precise as I can, but I'm not an expert in app
> servers, and it's not me who faced this problem. From my understanding,
> Equinox would be fine to install bundles from remote locations, eg. by
> issuing "install http://x.y.z/bundle.jar" in console. Then it would
> probably make a local copy of that bundle in <configuration> area, which
> is hopefully out of WebSphere surveillance. Does it make sense? Or are
> there better workarounds?
>
> Thank you for your help,
> Jacek
|
|
|
| Re: Equinox on Websphere and context updates [message #102743 is a reply to message #102652] |
Thu, 06 December 2007 16:55 |
| Eclipse User |
|
|
|
Originally posted by: jacek.pospychala.pl.ibm.com
Thanks Richard,
I like your answer.
Richard Backhouse wrote:
> Jacek,
>
> I am assuming that the equinox deployment mechanism used is the
> Equinox Servlet Bridge. If this is the case then there are no issues
> with adding new bundles as the the OSGi working area is placed in the
> WebApplications temp directory which is not monitored for file
> changes. Running the Servlet Bridge in WAS 6.1 is no problem.
>
> BTW turning on/off the monitoring of file changes is something that is
> configuration per Application deployment.
>
> Richard
>
> Jacek Pospychala wrote:
>> Dear Equinox,
>>
>> I've heard from few sources a following concern regarding deploying
>> Equinox on WebSphere (as well as other app servers).
>> Equinox works fine there, but when installing additional bundle jars,
>> app server detects this (new Jar in app area) and reloads whole
>> application context killing Equinox instance.
>>
>> Is it a known issue? Does it require any special configuration of
>> WebSphere, or is it rather misconfiguration of Equinox?
>>
>> I'm trying to be as precise as I can, but I'm not an expert in app
>> servers, and it's not me who faced this problem. From my
>> understanding, Equinox would be fine to install bundles from remote
>> locations, eg. by issuing "install http://x.y.z/bundle.jar" in
>> console. Then it would probably make a local copy of that bundle in
>> <configuration> area, which is hopefully out of WebSphere
>> surveillance. Does it make sense? Or are there better workarounds?
>>
>> Thank you for your help,
>> Jacek
|
|
|
Powered by
FUDForum. Page generated in 0.03334 seconds
Home