|
|
|
|
| Re: Fake OSGi in enterprise applications? [message #79655 is a reply to message #79567] |
Tue, 19 December 2006 23:11   |
Eclipse User |
|
|
|
Originally posted by: alex_blewitt.yahoo.com
> I agree that the bundle aspect is one of the most important in the long
> run, but I don't think it's usable in a production environment right
> now.
Each to their own, I guess. I personally see it as production ready.
> Also, we have a lot of applications installed in our cluster and
> have a policy that each applications should preferably come as a single
> EAR, I don't think admins would be happy with dynamically updateable
> bundles and also configuration that wouldn't survive a restart (or would
> it? We are using Weblogic 8.1, 9.2 soon).
There's no intrinsic difference between a dynamically restartable EAR and a dynamically restartable bundle. They both work in the same way, which is to support classloaders per archive (although the EAR approach often launches a separate Java process anyway, depending on J2EE server). It's just a different name/extension.
The bigger problem, perhaps, is that the current J2EE servers (including Weblogic/WebSphere) just have command-and-control systems for running EARs, so the admin tools are very EAR focussed. Of course, that doesn't prevent you running OSGi inside the EAR if you wanted; except that each EAR would be bundled with its own separate OSGi engine. That would give you the benefit of allowing it to work both in an EAR and also in other configurations at a later stage.
Don't quite know what you're referring to with the configuration data, so can't answer that one.
Alex.
|
|
|
| Re: Fake OSGi in enterprise applications? [message #79670 is a reply to message #79655] |
Wed, 20 December 2006 08:20 |
 Erkki Lindpere
Messages: 90
Registered: July 2009 |
Member |
|
|
> Each to their own, I guess. I personally see it as production ready.
Actually, if BIRT has been using Equinox in the webapp, I might reconsider
my opinion about production readyness. The last time I looked at the BIRT
code it seemed to me that it was using it's own concepts of Platform etc.
and it's own plugin registry.
> Don't quite know what you're referring to with the configuration data, so
> can't answer that one.
What I meant was that if bundles in the application get updated during
runtime, and then for some reason the server has to be restarted, normally,
I think the application would be deployed from the EAR again, forgetting any
updates or OSGi configuration changes that were done in the meantime. Maybe
this can be avoided, though -- I must admit I'm not familiar with all the
specs/possibilities in Weblogic or J2EE servers in general.
Erkki
|
|
|
| Re: Fake OSGi in enterprise applications? [message #79715 is a reply to message #79670] |
Thu, 21 December 2006 04:14 |
| Eclipse User |
|
|
|
Originally posted by: jeff_mcaffer.REMOVE.ca.ibm.com
Erkki Lindpere wrote:
>> Each to their own, I guess. I personally see it as production ready.
>
> Actually, if BIRT has been using Equinox in the webapp, I might reconsider
> my opinion about production readyness. The last time I looked at the BIRT
> code it seemed to me that it was using it's own concepts of Platform etc.
> and it's own plugin registry.
Depends on what you are talking about but, for example, the new version
of IBM Websphere App Server is based on Equinox. They are not
themselves using the servlet bridge etc since they are implementing the
app server. I do know of a few very significant projects using the
servlet bridge and related technology.
>> Don't quite know what you're referring to with the configuration data, so
>> can't answer that one.
>
> What I meant was that if bundles in the application get updated during
> runtime, and then for some reason the server has to be restarted, normally,
> I think the application would be deployed from the EAR again, forgetting any
> updates or OSGi configuration changes that were done in the meantime. Maybe
> this can be avoided, though -- I must admit I'm not familiar with all the
> specs/possibilities in Weblogic or J2EE servers in general.
Not sure what answer you want here. The short answer is that nothing is
random. If you want the configuration to stay the same from run to run,
don't update it. If you want it to get the latest stuff that is there,
then update the configuration. This should all be in your control.
Jeff
|
|
|
Powered by
FUDForum. Page generated in 0.02063 seconds
] 
Search
Help
Register
Login
Home
