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 the URL I need to change each. [1] https://docs.google.com/document/d/1AqiLBLenl68WTKwoC0HLliYPfIBSWCFMy8BH7Vh8ZNw/edit [2] https://docs.google.com/document/d/17Q6B60KYrU53YfxPyML_YKZftCrNWH_YTtG8r7bBwcA/edit On Wed, Jun 8, 2016 at 1:40 AM, Ravindra Ranwala <ravin...@wso2.com> wrote: > 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 > Endpoints only. If you have lots of JMS proxies we may need to migrate them > into JMS Inbound Endpoints. > > > Thanks & Regards, > > On Wed, Jun 8, 2016 at 11:00 AM, Vijitha Ekanayake <vijit...@wso2.com> > wrote: > >> 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 details. >> >> [1]. [Architecture] [GSoC] JMS 2.0 support for WSO2 ESB JMS Inbound >> Endpoint and JMS Transport >> >> Thanks. >> >> On Wed, Jun 8, 2016 at 8:58 AM, Dilshani Subasinghe <dilsh...@wso2.com> >> wrote: >> >>> 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. >>> >>> >>> */** Should this service use JMS 1.1 ? (when false, defaults to 1.0.2b) >>> */ private boolean jmsSpec11 = true;* >>> >>> @Vijitha - Hope you may explain the actual scenario ? >>> >>> Regards, >>> Dilshani >>> >>> >>> On Wed, Jun 8, 2016 at 1:25 AM, Manuranga Perera <m...@wso2.com> wrote: >>> >>>> 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 >>>> >>> >>> >>> >>> -- >>> Best Regards, >>> >>> Dilshani Subasinghe >>> Software Engineer - QA >>> WSO2, Inc.;http://wso2.com/ >>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ> >>> lean.enterprise.middleware >>> Mobile: +94773375185 >>> Blog: dilshanilive.blogspot.com >>> >> >> >> >> -- >> Vijitha Ekanayake >> Software Engineer*, *WSO2, Inc.; http://wso2.com/ >> Mobile : +94 777 24 73 39 | +94 718 74 44 08 >> lean.enterprise.middleware >> > > > > -- > Ravindra Ranwala > Software Engineer > WSO2, Inc: http://wso2.com > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> > Mobile: +94714198770 > > -- 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
