Note that for an InOnly exchange, the exchange should be queued
twice, because the provider component has to send back a DONE
status. Also, the destinationService will never change for a given
exchange as it is the provider address.
So in the JmsIn -> JmsOut, the same exchange should be enqueued
ServiceMix WAR file unable to be deployed to JBoss due to ClassLoader issues
-
Key: SM-568
URL: https://issues.apache.org/activemq/browse/SM-568
Project: ServiceMix
The trunk is now 3.1-SNAPSHOT.
--
Cheers,
Guillaume Nodet
[ https://issues.apache.org/activemq/browse/SM-557?page=all ]
Guillaume Nodet updated SM-557:
---
Fix Version/s: 3.1
(was: 3.0.1)
> WSDL 1.1 message normalization for the servicemix-http component
> -
[ https://issues.apache.org/activemq/browse/SM-521?page=all ]
Guillaume Nodet updated SM-521:
---
Fix Version/s: 3.1
(was: 3.0.1)
> Tuning parameters configuration
> ---
>
> Key: SM-521
>
[ https://issues.apache.org/activemq/browse/SM-457?page=all ]
Guillaume Nodet resolved SM-457.
Fix Version/s: 3.0
(was: 3.0.1)
Resolution: Fixed
Assignee: Guillaume Nodet
> Classloader for XBean deployment should su
Refactor servicemix-common for ease of use
--
Key: SM-569
URL: https://issues.apache.org/activemq/browse/SM-569
Project: ServiceMix
Issue Type: Improvement
Components: servicemix-common