Re: [ebxmlms-develop] MSH client: sending messages

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

MSH client: sending messagesHi Peter,

We got your point. However, currently we don't have another way for =
client-Hermes communication other than Java. Actually, to support =
non-Java client is already on our TODO list. We plan to add Web Service =
interface on Hermes (maybe as an external plug-in) for handling client =
requests. In this way, we can configure Hermes as a Web Service <-> =
ebXML gateway, to bridge between internal processes of a company and =
B2Bi between the company and its trade partner. This picture is big, and =
we target to work it out in a step-by-step manner.

In the meantime, we suggest you to use a loosely-coupled approach to =
facilitate non-Java client/Hermes integration:

1. Non-Java client put the message to be send in a folder
2. Write a generic Java program (as Hermes client) and poll for that =
folder. Once it successfully polls a message, it can send it out using =
Hermes Java API.
3. Use similar approach for handling incoming messages.

Thanks for your suggestion.

Cheers, -Patrick

  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: ebx...@li...=20
  Sent: Thursday, February 20, 2003 10:33 AM
  Subject: [ebxmlms-develop] MSH client: sending messages


  When a message is sent to Hermes using Request.send() (as in the =
LoopBack client), the message is sent by serialising the Java =
SOAPMessage object over an HTTP connection.

  This is fine for a Java client, but not for a non-Java client (for =
example, .NET).=20

  If we want to treat Hermes as a black box, there's no problem for =
incoming messages, because Hermes can be configured to forward them as =
SOAP messages to an HTTP server, which may be ASP.NET. However, for =
generating messages, it seems that a Java client must be used, because =
of the serialisation.

  Is there a non-Java-dependent way of sending SOAP/ebXML messages into =
Hermes?=20

  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.