Last week i attended a seminar on "Application Integration based on Open Source (FUSE) " organized by Progress Software and Flusso.
The FUSE brand is based on a set of leading projects from the Apache Software Foundation.
They include products like FUSE ESB (based on Apache ServiceMix),
FUSE Message Broker (based on Apache ActiveMQ),
FUSE Services Framework (based on Apache CXF)
and FUSE Mediation Router (based on Apache Camel).
Besides these products they deliver a plugin for Eclipse...
For alsb development we both use the console and the workspace studio of bea.
So once in a while i need to do some changes in the console and import the sbconfig.jar back into the ide.
In the current workspace i delete all projects and 'try' to import the sbconfig.jar.
The next error pops up :
Import failed: Validation failed with diagnostic messages. Diagnostics for WSDL /WSDLs/
ERROR: Validation of WSDL /WSDLs/ failed:
The Open Group has released their SOA Source Book.
The introduction tells us "The Open Group's SOA Source Book is a collection of source material for use by enterprise architects working with Service-Oriented Architecture. The material reflects input from a large number of people from a wide range of Open Group member companies, including product vendors, consultancies, and users of SOA. In some cases, these people have brought concepts developed, not just by themselves, but by groups of...
At the moment i'm busy with a migration of an alsb 2.6 enviroment to an alsb 3.0 enviroment.
In the alsb processes extra functionality is invoked by making use of the java call outs.
Nothing wrong with this if you ask me, the only thing which i'm wondering is, wont these java call outs mess up the transactional context of alsb processes itself.
At the moment the libraries which are being used are deployed with every servicebus process itself.
So we have/had some sort of default structure...