|
From: Patrick Y. <kc...@ce...> - 2003-04-24 10:28:03
|
Sending/receiving acknowledgementsSorry for our late response.. you =
know, we hardly can find a break to breath recently.. :-(
1. We have added the ToUrlResolver interface (similar to Peter's =
suggestion) in the nightly build. We also added an implementation =
ToUrlResolverImpl. This implementation looks for URL from the ToPartyID. =
Of course, you can make your own implementation (to look up LDAP, etc.) =
and install the resolver in the msh.properties.xml. (Yes, this is a =
server-wide setting..., any objection?)
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? ;-)
Regards, -Patrick
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Tuesday, April 22, 2003 1:00 PM
Subject: [ebxmlms-develop] Sending/receiving acknowledgements
A two part question on acknowledgements.=20
First, I'd like to check some logic.=20
The party ids of our messages are not of the form=20
<eb:From>=20
<eb:PartyId>http://from/msh/</eb:PartyId>=20
</eb:From>=20
Instead, they look like this:=20
<eb:From>=20
<eb:PartyId eb:type=3D"ABN">123456789</eb:PartyId>=20
<eb:Role>Buyer</eb:Role>=20
</eb:From>=20
Normally, this doesn't seem to matter. However, when an =
acknowledgement is requested, MessageProcessor attempts to build the URL =
of the message recipient from the From PartyId. In our case, this is =
doomed to failure, and the acknowledgement message is sent to the local =
Hermes instead.
Is this correct? If so, I'll have to add some more code to resolve a =
destination URL from a partyid, and fix MessageProcessor to use it.
Second question: when an acknowledgement message is received, Hermes =
appears to swallow it, and doesn't send it on to my listener. How can I =
tell if an acknowledgement has arrived?
Thanks.=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.
|