ServiceOrientedComponentModelInNetBeans65

Service-Oriented Component Model In NetBeans 6.5

1 Service-Oriented Component Model In NetBeans 6.5

1. Introduction

Since NetBeans 5.5, the SOA project systems has been developed based on the service component model introduced in the JBI 1.0 spec (JSR-208). This model defined in terms of service endpoint, service connection, service unit (SU), and service assembly (SA) is a coarse-grained model designed to describe SOA deployment artifacts. It works well in many scenarios. However, after 2 years and 3 releases (5.5, 6.0, and 6.1), we have experienced several limiting issues with this model. For example, many users have expressed interests in working with service components at a finer grained level than service units, especially in the early design phase. Another key issue is that the WSDL-centric model can not be mapped easily to adapt other service oriented component technologies. In NetBeans 6.5, we plan to introduce a more generic service oriented component model. The new model will extend the existing JBI model to allow finer grained service components and other run-time supported service definition technologies in addition to WSDL.

Other Service Oriented Architectures

In addition to WSDL-based web services, another popular example of SOA is the OSGi service platform. The latest version, OSGi Service Platform Release 4, defines a service layer providing supports for bundles to publish, find, and bind services. There are several service oriented component model frameworks developed for this platform:

NetBeans Tracking Ticket

IZ# 133034

http://www.netbeans.org/issues/show_bug.cgi?id=133034

2. Proposed Features

The proposed NetBeans module will introduce a set of service oriented component (SOC) API for other SOA tooling modules to access, use, and manage service oriented components within NetBeans IDE. It will also provide a set of SOC SPI allowing plug-in extensions for, e.g., additional service definition technologies, be added to the component model framework. The following is a brief list of key requirements:

Key Requirements

Run-time: GlassFish v3 and OpenESB v3
Design-time: NetBeans IDE
Users: NetBeans IDE SOA tooling modules
Design-time SOC Model:

support hierarchical components of mix granularity
support extensible service definition technology
support multiple service component model frameworks
backward compatible with the JBI 1.0 component model

An advance goal of this proposal is to demonstrate that SOA tooling can be built to support multiple SOA technologies. To illustrate this, we will try to use the JBI 1.0 model and one of the OSGi model as test cases against the design and its implementation. This is to make sure that different SOA component frameworks can be support easily by the next generation of SOA tooling.

...more...