In "Use JBI components for integration: An introduction to Java Business Integration components," Adrien Louis discusses the Java Business Integration specification and describes more specifically the concept of "component" as defined in this specification. He also explains how components communicate through the JBI environment.

The Java Business Integration specification (Java Specification Request 208) defines a standard means for assembling integration components to create integration solutions that enable a service-oriented architecture (SOA) in an enterprise information system. These components are plugged into a JBI environment and can provide or consume services through it in a loosely coupled way. The JBI environment then routes the exchanges between those components and offers a set of technical services. A component is the main detail a user or developer faces when working in the JBI environment. Understanding how a component interacts with the JBI environment is just as important as understanding the environment black-box itself.

In many ways, the JBI components looks a lot like the Java Connector Architecture specification. Is the design workable for you? If not, is that really a concern? In other words, should developers focus primarily on business requirements for a service and leave integration with JBI or other technologies up to specialists?

An interested introduction to the JBI-Standard and their functionality. Today existing some good and stable solutions from the OSS-Area, how e.g. Apache ServiceMix, which has the JBI-Standard already integrated. But what I'am missing, is the Integration and Support of JBI in many comercial products. Many of the well-known manufacteres has collaborated by the definition of the JBI-Standard ... Because even today it's so difficult to develop a Component and their associated routing, transformation,... cabilities, which is really applicable - without code-changes and by a simple deployment - in the Evironment of the ESBs,... from manufacturer X, Y and Z ? Roland http://www.soa-competence-network.de

Expect to hear a lot more in the Middleware / workflow / Integration areas. This is the Enterprise Java 'Sweet spot' in the same way the sweet spot for Ruby on Rails is 'Standard' Web 2.0 applications. Paul , Technology in Plain English

public void stop() throws JBIException { // Just break the loop of our listener; the thread will stop listener.running= false; } 1) using a unsynchronized boolean to communicate between 2 threads is not reliable 2) the thread may not be actually stopped after the call to stop() which may cause unexpected behaviors Maybe Thread.interrupt() and Thread.join() should be used ...

We offer Search Marketing solutions to UK businesses looking to promote their websites on the internet and through the search engines.>Website Design Cumbria

<a href="http://fortyonemedia.com/">Techtalks</a>

Latest technology in science, engineering and  computer industry

Techtalks Latest technology in science, engineering and  computer industry