Hi Ravindra/Dilshani,
Can we set transport.jms.JMSSpecVersion globally (ie: via axis2.xml)?
--
With regards,
*Manu*ranga Perera.
phone : 071 7 70 20 50
mail : m...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Hi Manuranga,
According to documentation, Yes we can set that. But I notice that, it
doesn't validate through the value given globally. For example, even I set
up JMS Version as 2.0 globally, it doesn't take that value.
Within the source (ServiceTaskManager.java) it seem to hard coded.
*/** Sho
Hi Manu/Dilshani,
According to the current implementation It seems, we haven't done any
changes in JMSTransportListener side. JMS 2.0 listener implementation is
supported as JMS inbound endpoint and sender implementation support on JMS
transport sender. You can refer mail thread[1] for more detail
Hi Manu,
Vijitha's comment is valid. As per the offline discussion I had with
ErandaR and PrabathAR, JMS 2.0 shared subscription feature is not
implemented for JMS Proxy services (in axis2 transport listener side) since
it will be deprecated in future. Therefore it is available for JMS Inbound
End
Hi Eranda,
In the doc, it shows how to setup JMS 2 listener proxy via inline parmas
[1] [2]. Which one is correct, the doc or above claim?
Hi ESB Team,
Please re-consider supporting JMS 2 via axis2 xml as well, since setting up
a large number of inbounds are hard to manage. Eg: If I need to change
Hi Manuranga,
JMS 2.0 listeners inside ESB should be configured as Inbound Endpoints. You
can refer [1] sample for the correct configuration. And I have updated the
document [2] as well so that there won't be any confusions.
[1].
https://docs.google.com/document/d/17Q6B60KYrU53YfxPyML_YKZftCrNWH
