Alex has started to work on a binding component around axis some time ago.
I do not know the exact status, but it may be a good path to integrate all
axis2 related stuff (ws-* specs) in it.
Alex ?

Cheers,
Guillaume Nodet

Charles Souillard wrote:

Guillaume,

do you know how we can integrate/use into SM all the WS-* spec (WS-ReliableMessaging, WS-Adressing, WS-Security, ...) ?

Thanks,
Charles


Guillaume Nodet wrote:



Charles Souillard wrote:

Hi all,

I have a question concerning how we can configure BCs (if it is possible).

For example, int the case I use servicemix SOAP BC :
1) Is it possible to configure the list of authorized users ? How ?
2) Is it possible to define an encryption method for a given message ? For all messages ? How ?



ServiceMix do not have any built-in features for authentication and encryption yet.

3) Is it possible to have reliable messaging ?



You can use XA transactions inside ServiceMix, and each component would be responsible for
enlisting its resources within the transaction.
The transaction object is available on the MessageExchange.getProperty(MessageExchange.JTA_TRANSACTION_PROPERTY_NAME).


In an another way, is it possible to dynamically change the endpoint of a message ? For example, my SE is currently exchanging messages with a food provider called A. For any reason, the administrator of my SE wants to now deals with a new provider called B. Is it possible to change by configuration the endpoint of my partner from A to B ? This is perhaps a stupid question as I am not sure to well understand if the message my SE sends to a BC could or couldn't carry any information about the desired destination endpoint...



If your BC is able to understand a property (for example) set on the exchange, it could route it to the desired external endpoint. Your component can also discover endpoints at runtime (for example querying endpoints that implements a given interface)
or you could use a router component for that.

Cheers,
Guillaume Nodet



Thanks a lot for your answers.
Cheers,

Charles





Reply via email to