OpenESB and CAPS

OpenESB and CAPS contributed by Fred Aabedi



A future version of Java CAPS includes the Open ESB framework and components. The Open ESB framework is based on the Java Business Integration (JBI) standard (JSR208) and has been built in Open Source (https://open-esb.dev.java.net). The components have also been developed in Open Source, with contributions from partners and individuals who have been working with us on the Open JBI Components project (https://open-jbi-components.dev.java.net) and openesbaddons under the Enterprise project on netbeans.org.



We aim to achieve openness and greater interoperability in the area of integration that has lacked it in the past. For the first time, component developers can hope to be able to build components that will be able to plug in without change in multiple frameworks that are based on JBI. We have already experienced vendors who had built components for ServiceMix (another JBI ESB implementation) easily port their components to OpenESB. Doing so gives them and their potential customers the ability to take advantage of the enterprise features provided by JavaEE since OpenESB framework leverages those features. It also gives them the advantage of leveraging the Netbeans design time tooling and project system that is part of OpenESB.



Customers will have the choice of choosing best of breed JBI components from their favorite providers and plug them into their favorite JBI Bus (hopefully ours).



The fact that most JBI components including the ones built by external to Sun entities are done in Open Source, reduces duplication of effort and frees up resources for more innovation.



As a result we are experiencing new components being built by a consortium and close cooperation of several distinct entities that are quite interesting and address the new social networking and mobile communications needs the public demands. Examples are SIP (Voice Over IP), XMPP (Jabber), and RSS (Syndication feeds) components.



It also provides customers an alternative to proprietary ESB platforms and help prevent vendor lock in and allows independent software vendors to extend established open platforms with customized offerings to meet specific customer needs.



The merge of the OpenESB framework and some of JBI components into CAPS 5.2 brings exciting new possibilities to both our existing and new customers in the integration, composite applications, and SOA domains. A consolidated runtime environment based on the world class Glassfish platform allows the interoperability of our classic Java EE based components and new JBI based components. This combination is quite powerful and provides a lot of new options to our customers to solve their integration problems and build killer composite applications. Customers realize this ability to leverage existing proven solutions along with leading edge technologies by taking advantage of the Bi-directional Re-use features (JBI Bridge) that allow interoperability between the Java EE and JBI based components. In addition, standardization on the NetBeans 6.0 platform for all of the Java CAPS tooling gives developers a proven and effective platform on which to develop enterprise solutions.



To learn more about Project Open ESB, please visit http://open-esb.org.

For more information about JBI and integration technologies, please visit http://java.sun.com/integration.

For more information about Sun's Java CAPS commercial product, please

visit http://www.sun.com/javacaps



Comments:

Hi Fread,

I have the following issue with my openEsb test, please see if you can help me with it:

I have a client that sends 3 soap message in a loop to the openesb,
when I am run it in debug mode (it is very slow run because I am checking the code) - the esb get the 3 different messages and put it on 3 files (this is the bpel process that I defined).

But when I run it regular (without slow debuging) I am getting 3 files with the same last soap message.

It seems that there is a thread problem, when the scenario run fast it overload the previous message like a set method do it and when it runs slowly the object is terminated and the esb create a new instance with no problem.

Please advise!!!

Thanks in advance!!

Eliad Dahan

Posted by Eliad Dahan on September 03, 2007 at 09:29 PM PDT #

"standardization on the NetBeans 6.0 platform for all of the Java CAPS tooling " -- does this mean jcaps is moving to netbeans 6.0 platform ??

Posted by satguru srivastava on September 10, 2007 at 04:46 AM PDT #

Fred,
I found your information on LinkedIn. Please contact me!!!

Thank you
Cherie Lester
419-855-6003
clester@getvitalized.com

Posted by Cherie Lester on September 27, 2007 at 11:01 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

fredaabedi

Search

Top Tags
Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today