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 133034

Summary: Service-Oriented Component Model In NetBeans 6.5
Product: soa Reporter: Tientien Li <tli>
Component: Composite ApplicationAssignee: Tientien Li <tli>
Status: NEW ---    
Severity: blocker CC: alexeyyarmolenko, ksorokin, slunegov
Priority: P1    
Version: 6.x   
Hardware: All   
OS: All   
URL: http://wiki.netbeans.org/ServiceOrientedComponentModelInNetBeans65
Issue Type: ENHANCEMENT Exception Reporter:

Description Tientien Li 2008-04-16 17:53:02 UTC 
Since NetBeans 5.5, the SOA project systems has been developed based on the service component model introduced in the 
JBI spec (JSR-208). This model defined in terms of service endpoint, service unit (SU), and service assembly (SA) is a 
coarse grind model. It works well in many scenarios. However, we have experienced some limiting issues with this 
model. For example, many users have expressed interests in working with service components at a finer grind than 
service units. 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 grind service components and other service 
definition technologies in addition to WSDL.
Comment 1 Tientien Li 2008-04-16 22:38:52 UTC 
Expanded version:

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 some limiting issues with 
this model. For example, 

- many users have expressed interests in working with service components at a fine-grained than service units, 
especially when in the 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 grind service components and other run-time supported service definition 
technologies in addition to WSDL.