We need to define an abstraction so that different message brokers can be configured. We can use the same kind of parameters currently used in axis2 jms transport configuration.
Regards Nandika On Thu, Dec 3, 2015 at 10:49 AM, Chathura Ekanayake <[email protected]> wrote: > We can also support client acknowledgements where JMS events send > acknowledgements after performing variable assignments from the JMS > message. However, I think AUTO_ACK is fine for the first phase of the > implementation. > > - Chathura > > On Wed, Dec 2, 2015 at 12:02 PM, Sathya Bandara <[email protected]> wrote: > >> Hi Hasitha, >> >> Currently we are using AUTO_ACK as the acknowledgement type. This is >> because there are limitations in using client acknowledgements in BPMN. >> Thanks for the suggestions. >> >> >> >> On Wed, Dec 2, 2015 at 11:48 AM, Hasitha Hiranya <[email protected]> >> wrote: >> >>> Hi Dilini, >>> >>> What is the Acknowledgement Type you are hoping to use here? >>> Or is it configurable? >>> >>> Acknowledgment type changes the way JMS messages are acked. Once acked, >>> message is getting removed from the queue. i.e if you use AUTO_ACK message >>> will be acked no matter processing failed or not. If you need to preserve >>> message (and maybe re-try), you should consider other acknowledgement types. >>> >>> >>> http://wso2.com/library/articles/2013/01/jms-message-delivery-reliability-acknowledgement-patterns/ >>> >>> Thanks >>> >>> On Wed, Dec 2, 2015 at 11:41 AM, Dilini Mihindra <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> WSO2 BPS already contains a RESTInvokerTask to send a message from a >>>> BPMN process instance to a REST service. Similarly, we can provide a JMS >>>> transport support for BPMN. This includes the following tasks: >>>> >>>> * - JMSStartEvent* >>>> This activity consists of a reference to an external JMS manager >>>> configuration and specific queue information for the given process to >>>> listen to. >>>> >>>> *- JMSMessageEvent * >>>> Similar to the StartActiviti, but this has to include correlation >>>> processing logic in addition to the above start event properties. >>>> >>>> *-JMSInvokerTask* >>>> This is similar to RESTInvoker Task where, from the BPMN >>>> process instance, we will be putting a message into a pre-configured >>>> JMS queue or a topic. >>>> >>>> JMS provides a reliable way of communicating messages among clients and >>>> the receiving clients do not need to be online to retrieve messages. >>>> Currently, we are implementing the JMSInvokerTask. The following diagram >>>> depicts this: >>>> >>>> [image: Inline image 1] >>>> >>>> Best Regards, >>>> >>>> Dilini Mihindra Mampitiya Arachchi >>>> Intern - Software Engineer >>>> Mobile: +94 710 420 550 >>>> Email: [email protected] >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Hasitha Abeykoon* >>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>> *cell:* *+94 719363063* >>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Sathya Bandara* >> Software Engineering Intern >> Email: [email protected] >> Mobile: +94 715 360 421 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Nandika Jayawardana WSO2 Inc ; http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
