I was asked a question related to JBI(Java Business Integration) from one of my customers.
I'm not good at JBI, so when I searched web, it describes as such:
JSR 208: JavaTM Business Integration (JBI)
Java Business Integration JSR (JBI) extends J2EE and J2SE with business integration SPIs. These SPIs enable the creation of a Java business integration environment for specifications such as WSCI, BPEL4WS and the W3C Choreography Working Group.
The industry is currently on the path to define standards for business integration that form a new layer of standard metadata in the web services stack. While this work is not complete as yet, the general shape of this standard metadata can be seen in the WSCI and BPEL4WS proposals. The industry needs a standard in this space and we look to the recently chartered W3C Choreography Working Group to drive the convergence of these and other related efforts. The JBI SPIs will reflect the industry consensus that emerges from this work.......................
Strange to say, Sun is leading the specification, and many J2EE supporting companies are working for the specification, EXCEPT IBM. They already published final release of this specification last August.
So, I'd like to know what is IBM's supporting strategy for JBI?
----------------------------
안녕하세요. calmglow입니다.
제가 알고 있는 바로는,
JBI는 자바에서 EAI와 B2B 분야를 아우르는 표준 프레임워크를 구축하고자 하는 움직임이고 오픈소스 진영에서 관심이 매우 많은 표준인 것으로 알고 있습니다.
아직 개발하고 있지는 않지만 티맥스의 경우 이 JBI에 기반하여 ESB엔진을 개발할 계획인 것으로 알고 있으며
오픈소스 JBI 구현체로는 ObjectWeb의 Celtix가 이 JBI의 대표적인 구현물입니다.
또한 아파치에서 진행 중인 ESB (이젠 아파치가 ESB까지 손을 대는군요.) 구현체인 Synapse 역시 부분적으로 이 JBI를 지원할 예정으로 알고 있습니다.
또한 이 JBI는 차기 J2EE 6 버전에서는 기본 탑재될 예정입니다.
따라서 이 JBI를 IBM에서도 지원하지 않을 수는 없겠으나
일단 JSR 208에 대한 참여 투표에서 IBM과 Bea는 거부의사를 밝혔습니다.
IBM이 투표에서 거부하면서 남긴 Comment는 다음과 같습니다.
http://www.jcp.org/en/jsr/results?id=3226
On 2005-06-20 IBM voted Abstain with the following comment:
IBM abstains because the JBI specification doesn't represent a sufficient step forward in terms of what we believe our customers need, and above what they can already do. Many technologies and open specifications are available to the Java programmer today with more compelling interoperability and better mechanisms for component composition. IBM's priority is to enable integration with the broadest range of platforms, applications, and existing business assets. This demands a language-neutral approach using today's Web Services standards, and simpler programming and application models.
또한 Bea 역시 다음과 같은 거부 의사를 밝혔네요.
On 2005-06-20 BEA Systems voted Abstain with the following comment:
BEA believes that the JBI specification is an incomplete attempt to standardize the interfaces between multi-vendor infrastructure and contributes little to the usefulness of the Java platform for business application integration, one of the real pain point for our customers. It's unfortunate that it's name alone will result in significant confusion in the marketplace.
결국 ESB는 자바 표준으로서의 영역보다는 그 상위의, 관점에서 진행되어야할 부분이다라는 걸까요?
I'm not good at JBI, so when I searched web, it describes as such:
JSR 208: JavaTM Business Integration (JBI)
Java Business Integration JSR (JBI) extends J2EE and J2SE with business integration SPIs. These SPIs enable the creation of a Java business integration environment for specifications such as WSCI, BPEL4WS and the W3C Choreography Working Group.
The industry is currently on the path to define standards for business integration that form a new layer of standard metadata in the web services stack. While this work is not complete as yet, the general shape of this standard metadata can be seen in the WSCI and BPEL4WS proposals. The industry needs a standard in this space and we look to the recently chartered W3C Choreography Working Group to drive the convergence of these and other related efforts. The JBI SPIs will reflect the industry consensus that emerges from this work.......................
Strange to say, Sun is leading the specification, and many J2EE supporting companies are working for the specification, EXCEPT IBM. They already published final release of this specification last August.
So, I'd like to know what is IBM's supporting strategy for JBI?
----------------------------
안녕하세요. calmglow입니다.
제가 알고 있는 바로는,
JBI는 자바에서 EAI와 B2B 분야를 아우르는 표준 프레임워크를 구축하고자 하는 움직임이고 오픈소스 진영에서 관심이 매우 많은 표준인 것으로 알고 있습니다.
아직 개발하고 있지는 않지만 티맥스의 경우 이 JBI에 기반하여 ESB엔진을 개발할 계획인 것으로 알고 있으며
오픈소스 JBI 구현체로는 ObjectWeb의 Celtix가 이 JBI의 대표적인 구현물입니다.
또한 아파치에서 진행 중인 ESB (이젠 아파치가 ESB까지 손을 대는군요.) 구현체인 Synapse 역시 부분적으로 이 JBI를 지원할 예정으로 알고 있습니다.
또한 이 JBI는 차기 J2EE 6 버전에서는 기본 탑재될 예정입니다.
따라서 이 JBI를 IBM에서도 지원하지 않을 수는 없겠으나
일단 JSR 208에 대한 참여 투표에서 IBM과 Bea는 거부의사를 밝혔습니다.
IBM이 투표에서 거부하면서 남긴 Comment는 다음과 같습니다.
http://www.jcp.org/en/jsr/results?id=3226
On 2005-06-20 IBM voted Abstain with the following comment:
IBM abstains because the JBI specification doesn't represent a sufficient step forward in terms of what we believe our customers need, and above what they can already do. Many technologies and open specifications are available to the Java programmer today with more compelling interoperability and better mechanisms for component composition. IBM's priority is to enable integration with the broadest range of platforms, applications, and existing business assets. This demands a language-neutral approach using today's Web Services standards, and simpler programming and application models.
또한 Bea 역시 다음과 같은 거부 의사를 밝혔네요.
On 2005-06-20 BEA Systems voted Abstain with the following comment:
BEA believes that the JBI specification is an incomplete attempt to standardize the interfaces between multi-vendor infrastructure and contributes little to the usefulness of the Java platform for business application integration, one of the real pain point for our customers. It's unfortunate that it's name alone will result in significant confusion in the marketplace.
결국 ESB는 자바 표준으로서의 영역보다는 그 상위의, 관점에서 진행되어야할 부분이다라는 걸까요?
공유하기 버튼
|
|
최근 덧글