[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[stp-dev] OSGI component support in Service Creation
|
Hi Johnson,
I have some points to your wiki page "OSGI component support in Service Creation".
At first your ideas are very similar to our understanding of OSGi components support. And what is more, we have made first implementation of WTP-based deployment for OSGI bundles to Equinox runtime (Equinox is WTP Server and Swordfish is WTP Runtime in this implementation). User has a possibility to deploy/undeploy, start/stop OSGi bundles via standard WTP Server Tools GUI. This code is part of Swordfish contribution.
It will be very useful to support also different OSGi runtimes (Apache Felix, Spring, etc) and provide a standard way to create, build, deploy and debug OSGi bundles.
The points:
1) Deployment. I also prefer WTP based solution for deployment. It seems to be standard for a lot of projects, family for the user and we have working POC solution for it.
2) Project wizards. As I understood it is not really necessary to have dedicated project wizards for OSGi runtimes (Equinox, Apache Felix, Spring), but it will be useful to have dedicated project wizards for SOA runtimes deployed (or based) on OSGi runtimes (ServiceMix bundle, Swordfish bundle, etc), because theoretically SOA runtimes can be deployed to different OSGi runtimes. Is it also your understanding?
3) Manifest Editor. Which other extensions beside support of different OSGi runtimes you see in Eclipse Manifest editor? Probably it makes sense to improve validation and usability there.
Regards,
Andrei.
