Tuesday Sep 23, 2008

OpenESB about to hit a major milestone

Any parent will tell you there are major milestones that you, as a parent, mark in your child's life, like when she gets her first tooth, or first goes off to kindergarten (or college!). These moments can fill you with pride, and excited anticipation for what's next.

It is with similar parental feelings that I can announce that Project OpenESB is about to hit a major milestone in the life of an open-source enterprise software project: a commercially supported version is to be introduced. This indicates the the project is both mature enough and stable enough to be widely "used in anger." After about three years of development, project OpenESB has "grown up" enough to mark this important occasion.

Sun will be introducing a branded version of OpenESB, to be called GlassFish ESB (running atop the GlassFish v2 application server, so the name is quite descriptive). GlassFish ESB is essentially Open ESB (including most of its components), fully supported by Sun, with the 24/7, one-throat-to-choke type of support a lot of enterprises require for key production systems.

I know some OpenESB users have, in the past, requested this kind of support, and some have even gone into production without it, so I've known for quite a while OpenESB was ready for milestone. Congratulations to the whole OpenESB community! You make me proud. And I know this is only the beginning.

Monday Jun 04, 2007

ZapThink should rethink SCA and JBI

Jason Bloomberg has made some rather unkind remarks about SCA and JBI. While he is entitled to his opinion, his remarks are not well supported by any arguments or statements of fact that puts forward. Although he asserts that there must be a better way to do SOA, he is remarkably silent about what that would look like. He should share any constructive ideas he has on this subject. He should also take a closer look at the specification; he will find many things, including the fact that JBI and SCA are complementary technologies.[Read More]

Wednesday Apr 11, 2007

Relationship of SCA and JBI

There is an interesting white paper at the OSOA web site entitled "Relationship of SCA and JBI". Given the confusion about this subject in the recent past (which I have commented on), I'm glad to see something that is more informative on this subject, published by the Open SOA collaboration, which includes Sun, IBM, Oracle, SAP, BEA, and others. (Check out the Open SOA site for details.

Some interesting bits:

"Both SCA and JBI are focused on helping developers construct and compose services so it is natural to assume that they are competitors; however, this is not the case. While both can be used separately, they are also effective to use together because they focus on different aspects of the larger service composition problem.

"The reason this is possible is that SCA and JBI target different audiences. The SCA specifications target end users. They describe how to implement, assemble and deploy applications composed from services. As such, the target audience for these specifications is people working in the roles of developer, assembler and deployer respectively."

That pretty well summarizes the situation, as it exists with JBI 1.0. One of the possible outcomes of JSR 312 (JBI 2.0) is an improvement in the alignment between the two technologies. Such an improvement would allow the technologies not only to co-exist (as is the case today), but also would eliminate what small "impedance mismatches" exist in the areas of deployment and metadata.

About

rtenhove

Search

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