This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 160994 - Representing one EJB as single OSGi Bundle with Services
Summary: Representing one EJB as single OSGi Bundle with Services
Status: RESOLVED INCOMPLETE
Alias: None
Product: javaee
Classification: Unclassified
Component: Maven (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Janicek
URL:
Keywords:
Depends on: 149241
Blocks:
  Show dependency tree
 
Reported: 2009-03-24 11:02 UTC by mnachev
Modified: 2014-07-30 13:47 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mnachev 2009-03-24 11:02:35 UTC 
In the GlassFish v3 development mail list from Sahoo I was informed that the possibility to represent one EJB as single
OSGi Bundle will be realized/implemented soon. Now in the existing Maven Enterprise Application is not possible to have
many EJB modules (Maven OSGi Bundle projects). It will be very helpful and powerful if NetBeans support such kind of
sub-project organization.
Comment 1 Milos Kleint 2009-03-24 11:22:16 UTC 
well, I'm not sure what the problem is. You can have as many ejb modules in an ear as you want. just create an ejb
project and have the ear project include it as dependency.

On a general note, we cannot explicitly support every possible setup within the IDE. The fact that we don't provide
wizards for something doesn't imply it cannot be done with maven projects by manual configuration.
Comment 2 mnachev 2009-03-24 13:55:14 UTC 
The problem is that all JAR files which are OSGi Bundles should be started as OSGi Bundles not to be putted in the class
path as regular JAR files. This is valid for all: EJBs, WEBs and App-Client JAR files.
For these purposes can be used RFC-139 OSGi JMX Management (deploy, undeploy, start, stop, config, etc.).
Comment 3 Milos Kleint 2009-03-24 14:03:53 UTC 
related to issue 149241, if we decide to support OSGI lifecycle, then this is one of the items on the TODO list.
Comment 4 Antonin Nebuzelsky 2010-01-14 06:58:19 UTC 
Changing the default owner to issues@javaee.
Comment 5 Martin Janicek 2014-07-30 13:47:25 UTC 
Sorry, but I have no idea what this request means. Could you please try to explain it one more time for someone who has not a clue about the topic? Thanks!