History of Java CAPS product lines
The release 6 of Java CAPS is coming and you can find a lot of information
on our product page
Java CAPS 6 will include Netbeans 6.1, Glassfish v2 and OpenESB v2. It will also include the Repository module coming from Java CAPS 5 so that you will be able to import Java CAPS 5 projects. You can integrate Java CAPS 5 projects with OpenESB and Java EE applications because all are running on the same Glassfish v2 application server. Jason has a good explanation of the differences between Java CAPS 6 and OpenESB In order to put the next Java CAPS release in perspective I have prepared a brief history of the SeeBeyond product lines. I was also inspired by this history of Glassfish
Significant events:
1989: SeeBeyond was incorporated under the name of STC: Software Technology Corp.
1999: release of e*Gate 4.0. This product introduces a new distributed architecture. The components message queues, message translators and application adapters are defined in a central repository. The components are instanciated at runtime in different processes and potentially different servers, all comunicating together. This distributed architecture can be easily scaled by replicating components to handle large throughput. The language used for message translation is a variant of LISP called Monk.
2000: SeeBeyond enters the stock market. The last release of the e*Gate 4.1.x line is out: 4.1.2. Already has some support for Java in addition to Monk.
2001: release of e*Gate 4.5.0. This release enhanced the support of Java so that it is the main language for programming the platform. A graphical environement for developing message handling (tranformation and routing) code is available. The message queuing engine is compatible with the standard JMS (Java Message Service).
2002: the last release of the 4.5.x line is out: 4.5.3
2003: release of Integrated Composite Application Network (ICAN) Suite v5.0 This suite introduces a new architecture based on J2EE. The development environement is based on Netbeans and is fully integrated amongst the various modules of the suite.
The Schema Runtime Environement (SRE) is a continuation of the 4.5.x product line. It includes a JMS Message server fully interoperable with ICAN J2EE. The "SRE" line continues to be supported with updates and fixes and provides a migration path for all projects since 4.0 using either Monk or Java. As of today we're at SRE 5.0.5 Update 1.
2004: The last release in the 5.0.x line is 5.0.5. This release continues to be supported and update with Rollup patches approximately twice a year. As of today we're at ICAN 5.0.5 Rollup 7.
2005: In August 2005 SUN acquired SeeBeyond.
2006: Java Composite Application Platform Suite (CAPS) 5.1.0 This is the first release of the suite after SUN acquisition. The runtime is based on SUN Application Server 8.0. The deployement and monitiring architecture is enhanced.
2007: The last release of the 5.1.x line is 5.1.3. This release continues to be supported and update with Rollup patches approximately twice a year. As of today we're at 5.1.3 Rollup 2.
2008: As of today, release candidate of Java CAPS 6.
Java CAPS 6 will include Netbeans 6.1, Glassfish v2 and OpenESB v2. It will also include the Repository module coming from Java CAPS 5 so that you will be able to import Java CAPS 5 projects. You can integrate Java CAPS 5 projects with OpenESB and Java EE applications because all are running on the same Glassfish v2 application server. Jason has a good explanation of the differences between Java CAPS 6 and OpenESB In order to put the next Java CAPS release in perspective I have prepared a brief history of the SeeBeyond product lines. I was also inspired by this history of Glassfish
Significant events:
1989: SeeBeyond was incorporated under the name of STC: Software Technology Corp.
1999: release of e*Gate 4.0. This product introduces a new distributed architecture. The components message queues, message translators and application adapters are defined in a central repository. The components are instanciated at runtime in different processes and potentially different servers, all comunicating together. This distributed architecture can be easily scaled by replicating components to handle large throughput. The language used for message translation is a variant of LISP called Monk.
2000: SeeBeyond enters the stock market. The last release of the e*Gate 4.1.x line is out: 4.1.2. Already has some support for Java in addition to Monk.
2001: release of e*Gate 4.5.0. This release enhanced the support of Java so that it is the main language for programming the platform. A graphical environement for developing message handling (tranformation and routing) code is available. The message queuing engine is compatible with the standard JMS (Java Message Service).
2002: the last release of the 4.5.x line is out: 4.5.3
2003: release of Integrated Composite Application Network (ICAN) Suite v5.0 This suite introduces a new architecture based on J2EE. The development environement is based on Netbeans and is fully integrated amongst the various modules of the suite.
The Schema Runtime Environement (SRE) is a continuation of the 4.5.x product line. It includes a JMS Message server fully interoperable with ICAN J2EE. The "SRE" line continues to be supported with updates and fixes and provides a migration path for all projects since 4.0 using either Monk or Java. As of today we're at SRE 5.0.5 Update 1.
2004: The last release in the 5.0.x line is 5.0.5. This release continues to be supported and update with Rollup patches approximately twice a year. As of today we're at ICAN 5.0.5 Rollup 7.
2005: In August 2005 SUN acquired SeeBeyond.
2006: Java Composite Application Platform Suite (CAPS) 5.1.0 This is the first release of the suite after SUN acquisition. The runtime is based on SUN Application Server 8.0. The deployement and monitiring architecture is enhanced.
2007: The last release of the 5.1.x line is 5.1.3. This release continues to be supported and update with Rollup patches approximately twice a year. As of today we're at 5.1.3 Rollup 2.
2008: As of today, release candidate of Java CAPS 6.
Hello Eric,
I was also reading your other article about "Create a Java EE Web service in Java CAPS 6 to connect SAP" and I'm wondering if the plain JEE5 way of doing things is not going to hide both eInsight and OpenESB at all. In recente times I was a lot involved in situation where eInsight solutions have been replaced by good, old eGate, as because of BPEL misuse. For the average developer, as you correctly mentioned, the JEE way looks much more natural. To be honest is true for me as well, as I think JBI, OpenESB and the CASA editor are pretty alien technologies and generally speaking looking more complex than JavaCAPS Repository-based previous approach. Still I've been hardly involved in situation where BPEL is used correctly, I wonder how are your feelings about the whole thing these days: are we going to a much more "traditional" development process? I wouldn't say this is a bad thing anyway.
Best regards, hope you are well
Posted by Maurizio on June 25, 2008 at 11:00 AM CEST #