Re: [ebxmlms-develop] Setup of ApplicationContexts

[Patrick Y. <kc...@ce...>]

RE: [ebxmlms-develop] Setup of ApplicationContextsPeter,

This is a normal behaviour. For error messages, we tried our best to =
deliver them to the sender. We do that by following the trace of =
RefToMessageID.

In your case, we suggest you to send out the messages using the Request =
with AppContext (*,*,*,*). You can send out any messages using Request =
with any AppContext. The AppContext only governs the receiving patterns.

For the ToPartyID bug, please check out the latest CVS copy. We have =
fixed that some time ago.

Regards, -Patrick
  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: 'ebx...@li...'=20
  Sent: Tuesday, April 01, 2003 2:47 PM
  Subject: RE: [ebxmlms-develop] Setup of ApplicationContexts


  I have a listener servlet registered with Hermes using =
ApplicationContext("*", "*", "*", "*"). I want this servlet to receive =
*all* incoming messages.

  In the Loopback application (which I've augmented over time), I create =
a Request using=20

  ApplicationContext("__"+cpaID, "__"+conversationID, "__"+service, =
"__"+action);=20

  The underlines are there to create an ApplicationContext that I should =
never receive. I then create a message with=20

              header.setCpaId(cpaID);=20
              header.setConversationId(conversationID);=20
              header.setService("myService", "myType");=20
              header.setAction("myAction");=20

          mshReq.setSign("alias", "password".toCharArray(), "keystore"); =


  and send the message. Because the message isn't verified (which is a =
separate problem), I get an error response. However, the error message =
(with action "MessageError" and service =
"urn:oasis:names:tc:ebxml-msg:service" as per the specification) is =
getting delivered to my Loopback program, *not* to my listener servlet. =
Since my Loopback program runs only long enough to send the message, I =
don't want it to ever receive a message.

  From previous discussion in this thread, my assumption is that the =
Loopback program should *not* be getting  the incoming error message =
delivered to it, particularly since I can guarantee that I have never =
registered for action "MessageError" or service =
"urn:oasis:names:tc:ebxml-msg:service" in Loopback.

  What's going on here?=20

  (Incidentally, there's a possible bug here. I use=20

  header.addToPartyId("99999999999", "ABN");=20

  to build the message, but the error message I get back has a null =
type. Ditto for the frompartyId.)=20

  PJDM=20
  --=20
  Peter Mayne=20
  Technology Consultant=20
  Spherion Technology Solutions=20
  Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602=20
  T: 61 2 62689727  F: 61 2 62689777=20

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.