2005IEEE Internet ComputingRequires access

Java Business Integration

Steve Vinoski

Open publisher page 37 citations

Abstract

Anyone intent on developing a Java-based framework for enterprise integration would do well to keep a few things in mind. One lesson is that today's Java programmers want to write Java, not stylized or otherwise "special" Java that must incorporate framework-specific artifacts. Another lesson is that standardizing a suitable integration-focused framework would be a good idea, given that the alternative is to add yet another proprietary system to a field already rife with stove-piped solutions that don't work together. The most important lesson, however, could well be that when it comes to integration, Java can't solve it all. Making it possible for solutions outside traditional Java programming to work within the framework is thus a necessity, not a nicety. One standards effort currently targeting the business-integration space is Java Specification Request 208, entitled "Java Business Integration" (JBI). Like other JSRs in the Java Community Process, JBI obviously has to work with the Java 2 platform - in this case, both the standard and enterprise editions (J2SE and J2EE, respectively). It also wisely goes beyond the Java-centric focus in most JSRs and aims to accommodate implementation alternatives outside the pure Java space. The approach underlying JBI is a bit unusual compared to other JSRs in that it uses Web services at its core. Rather than focusing on how to build Web services using Java, it promotes an architecture that's strongly based on Web services' principles and approaches.

About this research paper

What this paper is about

Anyone intent on developing a Java-based framework for enterprise integration would do well to keep a few things in mind. One lesson is that today's Java programmers want to write Java, not stylized or otherwise "special" Java that must incorporate framework-specific artifacts. Another lesson is that standardizing a suitable integration-focused framework would be a good idea, given that the alternative is to add yet another proprietary system to a field already rife with stove-piped solutions that don't work together. The most important lesson, however, could well be that when it comes to integration, Java can't solve it all. Making it possible for solutions outside traditional Java programming to work within the framework is thus a necessity, not a nicety. One standards effort currently targeting the business-integration space is Java Specification Request 208, entitled "Java Business Integration" (JBI). Like other JSRs in the Java Community Process, JBI obviously has to work with the Java 2 platform - in this case, both the standard and enterprise editions (J2SE and J2EE, respectively). It also wisely goes beyond the Java-centric focus in most JSRs and aims to accommodate implementation alternatives outside the pure Java space. The approach underlying JBI is a bit unusual compared to other JSRs in that it uses Web services at its core. Rather than focusing on how to build Web services using Java, it promotes an architecture that's strongly based on Web services' principles and approaches.

Why it matters

OpenAlex reports 37 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Anyone intent on developing a Java-based framework for enterprise integration would do well to keep a few things in mind. One lesson is that today's Java programmers want to write Java, not stylized or otherwise "special" Java that must incorporate framework-specific artifacts. Another lesson is that standardizing a suitable integration-focused framework would be a good idea, given that the alternative is to add yet another proprietary system to a field already rife with stove-piped solutions that don't work together. The most important lesson, however, could well be that when it comes to integration, Java can't solve it all. Making it possible for solutions outside traditional Java programming to work within the framework is thus a necessity, not a nicety. One standards effort currently targeting the business-integration space is Java Specification Request 208, entitled "Java Business Integration" (JBI). Like other JSRs in the Java Community Process, JBI obviously has to work with the Java 2 platform - in this case, both the standard and enterprise editions (J2SE and J2EE, respectively). It also wisely goes beyond the Java-centric focus in most JSRs and aims to accommodate implementation alternatives outside the pure Java space. The approach underlying JBI is a bit unusual compared to other JSRs in that it uses Web services at its core. Rather than focusing on how to build Web services using Java, it promotes an architecture that's strongly based on Web services' principles and approaches.

Key concepts: Java, Computer science, Real time Java, Java API for XML-based RPC, Java annotation, strictfp, Java applet, Java Card

Related papers

Back to paper searchBrowse research topicsOriginal source
Java Business Integration — Research Paper | ScholarLens