Quoting from David description of the connector:
“The javaspace: component is a transport for working with any JavaSpace compliant implementation, this component has been tested with both the Blitz implementation and the GigaSpace implementation .
This component can be used for sending and receiving any object
inheriting from the Jini Entry class, it’s also possible to pass an id
(Spring Bean) of a template that can be used for reading/taking the
entries from the space.
This component can be also used for sending/receiving any serializable
object acting as a sort of generic transport. The JavaSpace component
contains a special optimization for dealing with the BeanExchange. It
can be used, then, for invoking remotely a POJO using as a transport a
This latter feature can be used for an easy implementation of the
master/worker pattern where a POJO provides the business logic for the
Look at the test cases for seeing the various usage option for this component.”
Interestingly enough I’m seeing more the use of space based transport used to drive this new type scale-out integration frameworks. Beyond the space transport i believe that Camel users can leverage the fact that they can use the space as a data-store for sharing the state between the various services without needing to go to database just for that purpose.
Nice work David!