|
From: Patrick Y. <kc...@ce...> - 2003-04-03 04:05:19
|
MessageYou can download the latest source at http://www.freebxml.org/. How stable? It depends. Generally, we will test Hermes against quite a = number of test cases before making a release. And the nightly build of = course hasn't run through those test cases. On the other hand, you can = obtain prompt bug fix in nightly build. BTW, we want to setup a testbed to check the nightly build against test = cases. But due to resource limitation, we are slow on that. :-( Regards, -Patrick ----- Original Message -----=20 From: Mayne, Peter=20 To: 'ebx...@li...'=20 Sent: Thursday, April 03, 2003 7:14 AM Subject: RE: [ebxmlms-develop] Setup of ApplicationContexts Sounds excellent. I'm looking forward to getting the nightly build. = How stable is it in general? PJDM -- Peter Mayne Technology Consultant Spherion Technology Solutions Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 T: 61 2 62689727 F: 61 2 62689777=20 -----Original Message----- From: Patrick Yee [mailto:kc...@ce...]=20 Sent: Wednesday, 2 April 2003 8:24 PM To: ebx...@li... Subject: Re: [ebxmlms-develop] Setup of ApplicationContexts In that case, there will be only one error handler. This would be = fine for your application. But in the case of multiple clients = connecting to the same hermes server, we should make it more flexible. = That's the argument for us to find the AppContext based on ref to = message ID. How about we solve it this way: 1. Set up a receiver with app context (*,*,*,*) and a normal message = listener. This way, the request will poll hermes server from time to = time for new messages and call onMessage() to deliver the message to = application. 2. Set up a sender with app context (*,*,*,*) and pass = NoMessageListenerImpl as message listener. This is a newly created = message listener implementation which is "compatible" with a normal = message listener. But it will stop the request from polling hermes = server. The good thing is that even you will "override" the receiver's = registration by this action, the receiver can still poll the messages = successfully. This is what we mean by "compatible". :-) What do you think about this? You can find NoMessageListenerImpl in = the latest source. We will work on a nightly source tarball and put it = onto our web site tomorrow. Regards, -Patrick The information contained in this email and any attachments to it: (a) may be confidential and if you are not the intended recipient, any = interference with,=20 use, disclosure or copying of this material is unauthorised and = prohibited; and (b) may contain personal information of the recipient and/or the sender = as defined=20 under the Privacy Act 1988 (Cth). Consent is hereby given by the = recipient(s) to=20 collect, hold and use such information and any personal information = contained in a=20 response to this email, for any reasonable purpose in the ordinary = course of=20 Spherion's=20 business, including forwarding this email internally or disclosing it to = a third party. All=20 personal information collected by Spherion will be handled in accordance = with=20 Spherion's Privacy Policy. If you have received this email in error, = please notify the=20 sender and delete it. (c) you agree not to employ or arrange employment for any candidate(s) = supplied in=20 this email and any attachments without first entering into a contractual = agreement with=20 Spherion. You further agree not to divulge any information contained in = this document=20 to any person(s) or entities without the express permission of Spherion. |