[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stp-dev] OSGI component support in Service Creation
|
Hi Andrei,
It is good to know that you guys already supported the osgi component deployment based on wtp server framework in Swordfish.
Then in the service creation area, we will focus on how to help user to create osgi component more easily.
For the project wizard, I also agree that we will more likely to provide technology based wizard. Such as ServiceMix project wizard.
From end user point of view, when creating a ServiceMix or Swordfish component for osgi based runtime, he need to define:
I think the current WTP server/runtime api can only get the classpath information. This need to be extended to allow retrieving the osgi bundle information as well. (id, version, exported packages...etc). The Eclipse Manifest editor can be used here to setup the dependency.
Just like the eclipse plug-in project, the bundle project's classpath is combined by
-- classes from osgi runtime dependency.
-- jars from local lib dir under project.
-- classes from exported package in other bundle component projects within the same workspace. (Users may develop multiple components at once)
-- compilation output from the project itself
IMHO, it is better to have one dedicated classpath page in the osgi editor to help users to solve the problem.
On the usability side, one possible improvement is to create a GUI layer for those commands from the osgi console. So users won't often start from 'osgi>help' like me.
Thanks
Johnson
On Jan 10, 2008 12:18 AM, Andrei Shakirin <
andrei.shakirin@xxxxxxxxx> wrote:
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.
_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev
