Home » Eclipse Projects » Virgo » Tips on How to Integrate Felix GoGo, SSH, dan Gemini Blueprint to Eclipse Virgo
 Tips on How to Integrate Felix GoGo, SSH, dan Gemini Blueprint to Eclipse Virgo [message #685009] |
Thu, 16 June 2011 16:12  |
|
Glyn Normington suggested me to create this thread so other Virgo users would benefit this information.
I blogged a tutorial on how to integrate Felix GoGo, SSH, and OSGi Blueprint (Gemini Blueprint, but working instructions for Apache Aries also available) with Eclipse Virgo Web Server here:
http://eclipsedriven.blogspot.com/2011/06/how-to-create-felix-gogo-commands-with.html
I also created a sample PDE plug-in project openly accessible in GitHub: https://github.com/ceefour/gogosimple1
In my sample case Gemini Blueprint 1.0.0.M1 ran without problems in Virgo 3.0.0.M5! Yay!
So do you want Blueprint support in Virgo ? If so, please comment/vote on https://bugs.eclipse.org/bugs/show_bug.cgi?id=317943 and maybe you can help too by testing/developing/etc. 
Though particularly for my sample case, Apache Karaf won big (not to brag the competition, but hoping it would be a constructive feedback to Virgo team) due to well-integrated Felix GoGo, SSH server, Apache Aries as OSGi Blueprint implementation, and also good logging that can be inspected right inside console/SSH (Karaf shell commands like log:tail). I hope Virgo will also integrate these features, to which Borislav has confirmed that Virgo 3.0 will release with Felix GoGo + SSH integration! (oh yeah!)
Actually, installing Gemini is much less troublesome than Aries because I only had to put 3 bundles (io, core, extender, pretty intuitive) without no missing external dependency.
For Aries Blueprint, I needed 3 Aries bundles (aries.blueprint, aries.proxy, and aries.util), the latter two are not so intuitive to infer that they're blueprint's dependencies but perhaps it's because Aries modules (as a whole) are more cohesive than Gemini subprojects. Then Aries needed 3 more JARs: asm, asm.tree, asm.commons. I just happen to have those (SpringSource EBR version) lying around so I'm a bit lucky.
There is a but... On other project I use Blueprint "Compendium", it seems like Aries' "proprietary" extension on OSGi Blueprint, specifically these namespaces:
http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0
http://svn.apache.org/repos/asf/aries/tags/blueprint-0.3.1/blueprint-cm/src/main/resources/org/apache/aries/blueprint/compendium/cm/blueprint-cm-1.1.0.xsd
http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0
http://svn.apache.org/repos/asf/aries/tags/blueprint-0.3.1/blueprint-core/src/main/resources/org/apache/aries/blueprint/ext/blueprint-ext.xsd
If Gemini Blueprint can support those in the future, or better yet: standardize them, it'd be great.
Overall, Gemini Blueprint on Virgo works great, just as advertised, and I have yet to hit any edge cases.
[Updated on: Thu, 16 June 2011 16:13] Report message to a moderator |
|
|
| Re: Tips on How to Integrate Felix GoGo, SSH, dan Gemini Blueprint to Eclipse Virgo [message #685300 is a reply to message #685009] |
Fri, 17 June 2011 08:32  |
 Glyn Normington
Messages: 1222
Registered: July 2009 |
Senior Member |
|
|
Hi Hendy
Thanks for "surfacing" the discussion in bug 317943.
As promised, your blog is now linked from the Virgo home page.
We need Gemini Blueprint to release before we can consume it in a Virgo release. I understand the first release of Gemini Blueprint is not too far away, so that will free us up to upgrade Spring DM 1.2.1 to Gemini Blueprint (which includes Spring DM 2.0 function). There may turn out to be a fair amount of work to do because of the close integration of the kernel with Spring DM. On the other hand, it could be a relatively easy drop-in replacement.
Meanwhile, running Blueprint alongside Spring DM is a good way of running blueprint apps in Virgo.
As for Apache Karaf, yes there are several nice features that Virgo could learn from. We already have some bugzillas on the books which mention Karaf, but I would be delighted if you raised enhancement bugs for other Karaf capabilities that Virgo is missing. Feel free to send us patches too. 
As for the standardisation of custom namespaces in Blueprint, this is covered by OSGi RFC 155. Although this spec does not appear in the recent OSGi draft spec, it is referred to, and pre-req'd, by the draft specs for Blueprint Declarative Transactions and Blueprint Bean Interceptors.
Regards,
Glyn
|
|
|
Goto Forum:
Current Time: Wed Apr 24 18:14:51 GMT 2024
Powered by FUDForum. Page generated in 0.06109 seconds |
] 
Search
Help
Register
Login
Home
