Re: [ebxmlms-develop] Sending/receiving acknowledgements

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

MessageI mean the programming model of Hermes is somehow biased to CPA. =
We will probably have different CPA, i.e. different sets of parameters, =
per trade partner. The programming model tends to mandate one Request =
per CPA. In other words, we probably don't have a CPA which drives a =
"global, universal" receiver.

The routing mechanism is not rely on synchronous/asynchronous nature. =
Instead, it's the nature of the status response. When there are many =
applications sharing the MSH server, the status response message is =
meaningful *only* to the sender application. So, we try to route the =
response to the sender only.

Regards, -Patrick
  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: 'ebx...@li...'=20
  Sent: Wednesday, April 30, 2003 7:37 AM
  Subject: RE: [ebxmlms-develop] Sending/receiving acknowledgements


  Sorry, I don't understand this.

  The backend shouldn't care if a message is received synchronously or =
asynchronously. Why shouldn't synchronous messages be routed in the same =
way that asynchronous messages are?

  What do you mean by "separated receiver programs per trade partner"?

  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: Tuesday, 29 April 2003 8:09 PM
    To: ebx...@li...
    Subject: Re: [ebxmlms-develop] Sending/receiving acknowledgements


    Unfortunately, the status response message will not go through the =
message routing mechanism. When we view it using CPA perspective, it is =
more common to have separated receiver programs per trade partner.

    Regards, -Patrick

      ----- Original Message -----=20
      From: Mayne, Peter=20
      To: 'ebx...@li...'=20
      Sent: Tuesday, April 29, 2003 7:49 AM
      Subject: RE: [ebxmlms-develop] Sending/receiving acknowledgements


      <quote>=20
      2. We have done the flowing the ACK to message listener long time =
ago.. :-) To use it, please turn on the "PositiveAcknowledgment" option =
in msh.properties.xml. When turned on and upon receiving the MSH-level =
ACK, Hermes will generate a StatusResponse message to message listener, =
with the RefToMessageID pointing to the referenced message. Prophetic =
feature, huh? ;-)

      </quote>=20

      I would never have figured this out from the comment in =
msh.properties.xml.=20

      I set this to true, and send a message using Loopback, and it =
works, but the StatusResponse message is being received by Loopback =
(which is using ApplicationContext("_","_","_","_")), instead of my =
Listener (ApplicationContext("*","*","*","*")).

      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.