Hi Eranda, Thank you for providing brief introduction on the project. It would be better, if you can explain on changes which will take place in existing JMS inbound-endpoint. And how you are going to make it ready for "Shared Topic Subscription". Also need to know is "Shared Topic Subscription" going to support both durable & non-durable ?
Thank you! On Fri, May 8, 2015 at 5:19 PM, eranda rajapaksha <erand...@gmail.com> wrote: > Hi, > > I am Eranda Rajapakshe, GSoC 2015 participant for the project JMS 2.0 > support for WSO2 ESB JMS transport and inbound endpoint. First of all thank > you for giving me this valuable opportunity. > > After selecting my GSoC project I had a initial discussion with the ESB > team. In there I was asked to do the JMS 2.0 listener implementations on > JMS inbound endpoint and sender implementations on JMS transport sender, > because the transport listeners are soon to be deprecated from ESB. > > Following is the summary of my project plan, more detailed GSoC proposal > can be found in here. [1] ( Access is restricted for the authorized > personals ) > > Mainly the JMS 2.0 comes with a new API ( simplified API ) and some > additional functionalities. But it continue to support earlier APIs too. > > 1. Shared Topic Subscription > > Earlier the topic subscription was restricted to one subscriber, but to > improve the scalability they have made it to be shared in the new version. > > 2. JMSXDeliveryCount > > This value is to indicate the number of times the message got redelivered. > Even though this is not a new header value for JMS, setting this was not > mandatory in earlier versions. I am planning to use JMSXDeliveryCount value > to satisfy new use cases. > > 3. Delivery Delay > > Using this message publishing client can specify the delay interval and > the JMS provider will not forward the messages to the consumers until the > given delay time is reached. I am planning to implement this on WSO2 ESB > Transport Sender. > > Other than the implementation I have planned to, > > i. create integration tests > > ii. do performance tests > > iii. create simple samples > > iv. make documentation > > on above new feature implementations. > > [1]. > https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015/erandacr/5766466041282560 > > Thank you! > > -- > *Eranda Rajapakshe* > Computer Science and Engineering Undergraduate, > University of Moratuwa. > Tel : +94784822608 > Email : erand...@gmail.com <eran...@wso2.com> > -- Buddhima Wijeweera Software Engineer; WSO2 Inc.; http://wso2.com , Mobile: +94 71 427 9966 Email: buddh...@wso2.com Blog: https://buddhimawijeweera.wordpress.com GitHub Profile: https://github.com/Buddhima
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
