JCAPS 6.0 Released!!!!
By narayanaa on Jun 11, 2008
I read some of the review(s) some skeptical some encouraging with respect to customers, licensing charges, open-source etc..
But from a JCAPS/EAI/SOA developer's perspective what are the exiting and encouraging points lets have a peep.
All the old editors available in the latest version too.
Old projects since 5.0.5 can be migrated into 6.0 with the click of a mouse with out any changes
The build and deploy times coming down significantly with the power of support for latest JDK
Power of having the Glassfish or the Sun Application Server a.k.a. IS now on the Services tab of the NetBeans.
Power to manage resources on Application Server from the NetBeans IDE.
You have now the unified dev environment of NetBeans 6.0. This gives the power of developing other types of Applications along with CAPS applications
Power of Glassfish Application Server
Open-ESB container working with in glassfish giving the power of seamless talk to your existing applications. (You just need to have a facade of WS endpoint(s) for the existing applications to talk to the open-esb based Composite Applications)
We can bundle the old CAPS generated ear file along with the new service units of the open-esb components in a Service Assembly and deploy it to the Glassfish Application Server
You will not have a separate UDDI server rather it comes in a bundled along with the Application server as one more war file. So in effect we will have 1 installation less
Enterprise Manager still comes as a different server which needs to be started separately.
Repository is left as is. We can upload the sar files and can get the installation in the NetBeans 6.0. We can have the flexibility of having alternative storage for the project artifacts from with in the IDE instead of using a separate clients like CVS/SVN etc.., since NetBeans provides for alternatives for Version Control styles.
Installation gives the power of having all the nbms pre-installed in the NetBeans so that we do not need to connect to the repository during the first time running. This considerably reduces the installation time of JCAPS.
This release has one more advantage from the perspective of Adapters. They are available now “Outside the JCAPS environment”. This feature alone has lot of other implications like
Small Application developers can now just have a single adapter and can have their POJOs/EJBs / MDBs built around the adapter.
This gives more power with respect to the open-esb based integration. What I mean here is Open-esb components are XML/XSD based, so there is no provision to use the finer API's. Using these adapters will bridge the gap of finer API access.
Also deployment of single adapter from the Application Server stand point can have a single pool utilized by many J2EE components. Where as if we bundle the adapters as rar files for each of the rar file Application Server needs to create 1 connection pool consuming more system resources.
I will be posting more on JCAPS..