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 154584 - Maven based Enterprise OSGi Projects managed by JMX
Summary: Maven based Enterprise OSGi Projects managed by JMX
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Venkat Chellasamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-04 11:25 UTC by mnachev
Modified: 2010-03-31 20:15 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mnachev 2008-12-04 11:25:25 UTC
I would like to share my view for the future Enterprise Applications which will replace existing model in Java EE 5/6
with Enterprise/Distributed OSGi Application model (RFC-119):
- http://bg-jug.googlegroups.com/web/OSGiCommunityEvent-DistOSGi.pdf?hl=en
- http://svn.apache.org/repos/asf/cxf/sandbox/dosgi
- http://servicemix.apache.org/
The resemblances between Java EE and Enterprise OSGi is very close except:
1. In Enterprise OSGi applications the system modules and application modules are running in common container - OSGi
Framework. All Java EE applications are running in separate container from Java EE system modules.
2. One Enterprise OSGi application is divided in many OSGi Bundles (100 and more) which reduce the risk and increase the
stability and re-usability. Java EE applications are divided on few modules only (EJB, Web, JWS Application);
3. Enterprise OSGi applications are based on Service Component Architecture (SCA) and each service can be local and/or
remote and that is hidden for the application.
4. The SCA helps for very easy implementation of Client callback mechanism where this is almost impossible in the Java
EE world (Client call some method on the Server and before to return Server can call some method on the client).

In the same time the reference implementation (the RI is designed from Oracle/BEA) of RFC-139 is almost ready, the
management of each OSGi Framework will be similar like in Java EE using JMX (JSR-77). This will help to all Enterprise
OSGi Applications to be monitored and managed like Java EE applications.

Having in mind the above it will be very good if NetBeans is the first IDE which support Enterprise OSGi application
support using Maven and JMX:
   [File][New Project][Enterprise OSGi]:
      - [Enterprise OSGi Application]
      - [OSGi Service Bundle] (like EJB Module)
      - [OSGi Library Bundle] (like Packaged Archive)
      - [Enterprise Web Bundle]
      - [Enterprise Application Client Bundle] (Java Web Start/JNLP based Swing/JavaFX Application) running inside of
OSGi Framework environment.

The management, debugging, logging and monitoring will be done through JMX in similar way as Java EE.


Miro.
Comment 1 mnachev 2008-12-04 13:02:53 UTC
Very good combination of maven plug-ins is BND Maven Plugin (org.apache.felix:maven-bundle-plugin) and iPOJO Maven
Plugin (org.apache.felix:maven-ipojo-plugin).
Comment 2 mnachev 2010-03-31 20:15:49 UTC
The official Enterprise OSGi specification is fact. So, it is good time to add similar functionality for developers like for Java EE 5/6.