[JBIDE-9424] Provide the ability to deploy OSGi bundles - JBoss Issue Tracker

Details

Type: Feature Request
Status: Closed (View Workflow)
Priority: Major
Resolution: Done
Affects Version/s: None
Fix Version/s: 3.3.0.M3
Component/s: server
Labels:
None

Description

AS7 supports OSGi bundles as deployments, and Eclipse supports the creation of OSGi bundles through the built-in PDE tooling (see [1] for an example). However, OSGi bundles developed with Eclipse PDE can't be deployed via the JBDS to AS7 yet.

Support for deploying OSGi bundles to AS7 should be added to the JBoss Tooling.

[1] https://docs.jboss.org/author/display/AS7/Helloworld+OSGi+quickstart

Gliffy Diagrams

Options
- Sort By Name
- Sort By Date
- Ascending
- Descending
- Download All

Attachments

osgi-eclipse.png

8 kB

02/Aug/11 4:07 AM
Screen Shot 2011-07-29 at 14.00.26.png

164 kB

15/Aug/11 12:21 PM

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Fred Bricon added a comment - 29/Jul/11 8:52 AM

For your information, you can deploy the helloworld-osgi app from JBoss Tools
You need :

Eclipse Indigo Java EE
m2e, available from http://download.eclipse.org/releases/indigo
JBoss Archive Tools and JBossAS Tools, from http://download.jboss.org/jbosstools/updates/nightly/trunk/
m2eclipse-tycho from the m2e marketplace (Window > Preferences > Maven > Discovery > Open catalog)

You need to :

create a JBoss AS 7 server
import helloworld-osgi (from https://github.com/jbossas/quickstart/tree/master/helloworld-osgi) as a Maven Project in Eclipse
open the Project Archive View (Window > show view > other ...)
select the helloworld-osgi project
in the project archive view, right click on helloworld-osgi > New Archive > Jar
change the destination to /jboss-as-helloworld-osgi/target (to avoid polluting your source code)
choose exploded archive if you want
click finish
A Project archives node appears in the Project Explorer view, having a jboss-as-helloworld-osgi.jar node
right click on the jboss-as-helloworld-osgi.jar node (either in the Project Explorer or Project archives view), choose New Fileset
In the root directory input, enter target/classes (or select that folder via the Workspace button)
click finish
right click on the jboss-as-helloworld-osgi.jar node (either in the Project Explorer or Project archives view), Publish to server
select the AS7 instance, choose Always Publish and Autodeploy
In you servers view, start your AS7 instance
See how your bundle writes to the console.

And for the sweet part :

add a break point in your code
start AS7 in debug mode
once the thread hits your break point, change some code in your method (add/change a out.writeln(...))
See how it hot reloads your code \o/

Show

Fred Bricon added a comment - 29/Jul/11 8:52 AM For your information, you can deploy the helloworld-osgi app from JBoss Tools You need : Eclipse Indigo Java EE m2e, available from http://download.eclipse.org/releases/indigo JBoss Archive Tools and JBossAS Tools, from http://download.jboss.org/jbosstools/updates/nightly/trunk/ m2eclipse-tycho from the m2e marketplace (Window > Preferences > Maven > Discovery > Open catalog) You need to : create a JBoss AS 7 server import helloworld-osgi (from https://github.com/jbossas/quickstart/tree/master/helloworld-osgi ) as a Maven Project in Eclipse open the Project Archive View (Window > show view > other ...) select the helloworld-osgi project in the project archive view, right click on helloworld-osgi > New Archive > Jar change the destination to /jboss-as-helloworld-osgi/target (to avoid polluting your source code) choose exploded archive if you want click finish A Project archives node appears in the Project Explorer view, having a jboss-as-helloworld-osgi.jar node right click on the jboss-as-helloworld-osgi.jar node (either in the Project Explorer or Project archives view), choose New Fileset In the root directory input, enter target/classes (or select that folder via the Workspace button) click finish right click on the jboss-as-helloworld-osgi.jar node (either in the Project Explorer or Project archives view), Publish to server select the AS7 instance, choose Always Publish and Autodeploy In you servers view, start your AS7 instance See how your bundle writes to the console. And for the sweet part : add a break point in your code start AS7 in debug mode once the thread hits your break point, change some code in your method (add/change a out.writeln(...)) See how it hot reloads your code \o/

11 older comments

Hide

Permalink

Rob Stryker added a comment - 19/Aug/11 4:47 AM

It seems that the current implementation functions exactly as well as the OSGi launch configuration, and the export mechanism. They allow you to select which modules to include, but do no real dependency management in demanding a required bundle gets included. Export doesn't show an error if you try to export MasterBundle without exporting DependencyBundle. The launch config behaves similarly, without even a warning.

In this regard, I'd declare that this jira is closed.

It seems in the OSGi launch configuration, it pre-selects "Equinox" as the only possible implementation. I'd need a lot of help from an AS developer to learn how to launch an absolutely bare-bones AS7 OSGi configuration and include the selected bundles in it on-the-fly. I don't think that is something that can be addressed by this JIRA and is not feasible in the short term future. If you have specific ideas or details how that can be accomplished, please feel free to open another JIRA with that request

Show

Rob Stryker added a comment - 19/Aug/11 4:47 AM It seems that the current implementation functions exactly as well as the OSGi launch configuration, and the export mechanism. They allow you to select which modules to include, but do no real dependency management in demanding a required bundle gets included. Export doesn't show an error if you try to export MasterBundle without exporting DependencyBundle. The launch config behaves similarly, without even a warning. In this regard, I'd declare that this jira is closed. It seems in the OSGi launch configuration, it pre-selects "Equinox" as the only possible implementation. I'd need a lot of help from an AS developer to learn how to launch an absolutely bare-bones AS7 OSGi configuration and include the selected bundles in it on-the-fly. I don't think that is something that can be addressed by this JIRA and is not feasible in the short term future. If you have specific ideas or details how that can be accomplished, please feel free to open another JIRA with that request

Hide

Permalink

David Bosschaert added a comment - 22/Aug/11 3:35 AM - edited

Rob wrote: It seems that the current implementation functions exactly as well as the OSGi launch configuration, and the export mechanism. They allow you to select which modules to include, but do no real dependency management in demanding a required bundle gets included.

You are right that the OSGi launch configuration doesn't force you to do things, but it does help in some regard. By clicking the 'Add Required Bundles' it figures out (by walking Import-Package, Require-Bundle and Fragment-Host headers) what other bundles could be included to satisfy bundle dependencies and selects them for you.
Another useful aspect here is the ability to specify start levels and whether a bundle should be started at all.

However I agree that this is a larger piece of work and should probably be tracked in another bug

Show

David Bosschaert added a comment - 22/Aug/11 3:35 AM - edited Rob wrote: It seems that the current implementation functions exactly as well as the OSGi launch configuration, and the export mechanism. They allow you to select which modules to include, but do no real dependency management in demanding a required bundle gets included. You are right that the OSGi launch configuration doesn't force you to do things, but it does help in some regard. By clicking the 'Add Required Bundles' it figures out (by walking Import-Package, Require-Bundle and Fragment-Host headers) what other bundles could be included to satisfy bundle dependencies and selects them for you. Another useful aspect here is the ability to specify start levels and whether a bundle should be started at all. However I agree that this is a larger piece of work and should probably be tracked in another bug

Hide

Permalink

David Bosschaert added a comment - 29/Aug/11 11:33 AM

One thing I noticed is that if pax-runner seems to provide a nice integration for running OSGi frameworks through Eclipse. See here: http://eclipsesource.com/blogs/2009/08/14/eclipse-osgi-and-pax-runner/

It might be worth getting AS7 listed as an OSGi framework in Pax Runner as well, so we take advantage of this tooling...

Show

David Bosschaert added a comment - 29/Aug/11 11:33 AM One thing I noticed is that if pax-runner seems to provide a nice integration for running OSGi frameworks through Eclipse. See here: http://eclipsesource.com/blogs/2009/08/14/eclipse-osgi-and-pax-runner/ It might be worth getting AS7 listed as an OSGi framework in Pax Runner as well, so we take advantage of this tooling...

Hide

Permalink

Fred Bricon added a comment - 13/Sep/11 8:30 AM

Looks like it duplicates functionality with the Libra project : http://jaxenter.com/eclipse-libra-wtp-and-pde-working-together-37638.html

Show

Fred Bricon added a comment - 13/Sep/11 8:30 AM Looks like it duplicates functionality with the Libra project : http://jaxenter.com/eclipse-libra-wtp-and-pde-working-together-37638.html

Hide

Permalink

Libor Zoubek added a comment - 13/Sep/11 8:46 AM

verified on 3.3.0.M3-H18

Show

Libor Zoubek added a comment - 13/Sep/11 8:46 AM verified on 3.3.0.M3-H18

People

Assignee:

Libor Zoubek

Reporter:

David Bosschaert

Votes:

0 Vote for this issue

Watchers:

4 Start watching this issue

Dates

Created:

29/Jul/11 4:58 AM

Updated:

13/Sep/11 8:46 AM

Resolved:

19/Aug/11 4:47 AM

Development

Agile

View on Board