Re: [ebxmlms-develop] Hermes 1.0: CPA

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
We want to keep Hermes to be parameter driven, instead of CPA file
driven. <br>
<br>
In other words, we assume there is an external module which parse the
CPA file, all necessary CPA parameters should be fed to Hermes as
parameters. <br>
<br>
For sending, we have 2 kinds of parameters: set on SOAP message, and
not set on SOAP message. Therefore, we propose to set those parameters
on the EbxmlMessage object and also the send() method. CpaResolver is
not desirable as we don't want to touch on CPA file. What do you think?<br>
<br>
Regards, -Patrick<br>
<br>
<br>
pykoon wrote:<br>
<blockquote type="cite" cite="mid...@ce...">Dear all,<br>
Please note in the CPA Specification, the AckRequested,
DuplicateElimination
value can be defined as "perMessage", which the user should have to
specify
whether it needs AckRequested and DuplicateElimination. Therefore they
should
know about it if such CPA occurs.<br>
  <br>
Regards,<br>
Bob Koon<br>
  <br>
Mayne, Peter wrote:<br>
  <blockquote type="cite"
 cite="mid:5E9...@s-...">
    <title>Message</title>
    <meta content="MSHTML 6.00.2800.1141" name="GENERATOR">
    <div><span class="034015223-09072003"><font face="Arial" size="2">That's
why it requires more thought. :-) AckRequested, DuplicateElimination
are
physically specified in the SOAPMessage, but RetryInterval, Retries
aren't.</font></span></div>
    <div>&nbsp;</div>
    <div><span class="034015223-09072003"><font face="Arial" size="2">My
current
model has a central Sender process that is the funnel point for
outgoing
messages. A client that wants to send a message creates its payload,
and&nbsp;tells
the Sender (via JMS) "send message type X, using CPA Y, with this
payload
Z". The clients have no concept of an EbxmlMessage object,
or&nbsp;AckRequested,
or RetryInterval, etc. And why should they, since all that belongs in
the CPA.</font></span></div>
    <div>&nbsp;</div>
    <div><span class="034015223-09072003"><font face="Arial" size="2">PJDM</font></span></div>
<!-- Converted from text/plain format -->
    <p><font size="2">--<br>
Peter Mayne<br>
Technology Consultant<br>
Spherion Technology Solutions<br>
Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602<br>
T: 61 2 62689727&nbsp; F: 61 2 62689777</font></p>
    <blockquote dir="ltr"
 style="border-left: 2px solid rgb(0, 0, 0); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
      <div class="OutlookMessageHeader" lang="en-us" dir="ltr"
 align="left"><font face="Tahoma" size="2">-----Original Message-----<br>
      <b>From:</b> Ronald van Kuijk [<a class="moz-txt-link-freetext"
 href="mailto:rv...@ab...">mailto:rv...@ab...</a>] <br>
      <b>Sent:</b> Thursday, 10 July 2003 9:47 AM<br>
      <b>To:</b> '<a class="moz-txt-link-abbreviated"
 href="mailto:ebx...@li...">ebx...@li...</a>'<br>
      <b>Subject:</b> RE: [ebxmlms-develop] Hermes 1.0 my remarks<br>
      <br>
      </font></div>
      <div><font face="Arial" color="#0000ff" size="2">
      <div><span class="361055900-09072003"><font face="Arial"><font
 color="#0000ff"><font size="2"><span class="607403323-09072003">Correct
me if i'm wrong, but aren't RetryInterval, Retries etc as much
part of the message as SyncReply? And aren't AckRequested,
DuplicateElimination
not also defined in the CPA (E.5.2.2), just as role, service, action
etc....</span></font></font></font></span></div>
      <div>&nbsp;</div>
      <div><span class="361055900-09072003"><font face="Arial"><font
 color="#0000ff"><font size="2"><span class="607403323-09072003">This
make the 'this is CPA, this is Message' discussion not clearer.</span></font></font></font></span></div>
      <div>&nbsp;</div>
      <div><span class="361055900-09072003"><font face="Arial"><font
 color="#0000ff"><font size="2"><span class="607403323-09072003">I
agree that the sending MSH should (or must? ;-)) have knowledge of the
CPA.&nbsp;I'll&nbsp;look into&nbsp;what&nbsp;the ebXML TA says about this? (<a
 href="http://www.ebxml.org/specs/ebTA.pdf">
http://www.ebxml.org/specs/ebTA.pdf</a>
)</span></font></font></font></span></div>
      <div>&nbsp;</div>
      <div><span class="361055900-09072003"><font face="Arial"><font
 color="#0000ff"><font size="2"><span class="607403323-09072003">Ronald</span></font></font></font></span></div>
      </font></div>
      <blockquote dir="ltr"
 style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;">
        <div class="OutlookMessageHeader" dir="ltr" align="left"><font
 face="Tahoma" size="2">-----Oorspronkelijk bericht-----<br>
        <b>Van:</b> Mayne, Peter [<a class="moz-txt-link-freetext"
 href="mailto:Pet...@ap...">mailto:Pet...@ap...</a>]<br>
        <b>Verzonden:</b> donderdag 10 juli 2003 1:17<br>
        <b>Aan:</b> '<a class="moz-txt-link-abbreviated"
 href="mailto:ebx...@li...">ebx...@li...</a>'<br>
        <b>Onderwerp:</b> RE: [ebxmlms-develop] Hermes 1.0 my remarks<br>
        <br>
        </font></div>
        <div><span class="361055900-09072003"><span
 class="525021223-09072003"><font face="Arial" size="2">I said:</font></span></span></div>
        <div>&nbsp;</div>
        <div><span class="361055900-09072003"><font face="Arial"><font
 color="#0000ff"><font size="2">I think parameters should be carefully
classified. Those that are part
of a message (AckRequested, DuplicateElimination, etc) should be set
in the EbxmlMessage. Those that are part of the CPA (retries, retry
interval, etc), and are *not* part of the message, or of an individual
send(), should *not* be set in the message or as send()
parameters.&nbsp;Instead,
they should be provided by the CpaResolver.<br>
        </font></font></font></span></div>
        <div><span class="525021223-09072003"><font face="Arial"
 size="2">This
requires some more thought. For instance, even though syncReply is part
of the message, it is specified in the CPA, so a client shouldn't have
to set it.</font></span></div>
        <div>&nbsp;</div>
        <div><span class="525021223-09072003"><font face="Arial"
 size="2">Furthermore,
the spec says "<font face="Arial" size="2">This element MUST NOT be
used to override the value of </font><b><i><font
 face="Arial,BoldItalic" size="2">
syncReplyMode </font></i></b><font face="Arial" size="2">in the CPA</font><b><i><font
 face="Arial,BoldItalic" size="2">
. </font></i></b><font face="Arial" size="2">If the value of </font><b><i><font
 face="Arial,BoldItalic" size="2">
syncReplyMode </font></i></b><font face="Arial" size="2">is </font><b><i><font
 face="Arial,BoldItalic" size="2">
none </font></i></b><font face="Arial" size="2">and a </font><b><i><font
 face="Arial,BoldItalic" size="2">
SyncReply </font></i></b><font face="Arial" size="2">element is
present,
the </font><i><font face="Arial,Italic" size="2">Receiving MSH </font></i><font
 face="Arial" size="2">
should issue an error </font><font face="Arial" size="2">with </font><b><i><font
 face="Arial,BoldItalic" size="2">
errorCode </font></i></b><font face="Arial" size="2">of </font><b><i><font
 face="Arial,BoldItalic" size="2">
Inconsistent </font></i></b><font face="Arial" size="2">and a </font><b><i><font
 face="Arial,BoldItalic" size="2">
severity </font></i></b><font face="Arial" size="2">of </font><b><i><font
 face="Arial,BoldItalic" size="2">
Error</font></i></b></font></span><span class="525021223-09072003"><font
 face="Arial" size="2">
."</font></span></div>
        <div>&nbsp;</div>
        <div><span class="525021223-09072003"><font face="Arial"
 size="2">To
check incoming messages, the MSH must have access to the CPA.
Therefore,
it makes sense that the MSH should have access to the CPA to build
outgoing
messages as well.</font></span></div>
        <div>&nbsp;</div>
        <div><span class="525021223-09072003"><font face="Arial"
 size="2">PJDM</font></span></div>
<!-- Converted from text/plain format -->
        <div><font face="Arial" size="2">--<br>
Peter Mayne<br>
Technology Consultant<br>
Spherion Technology Solutions<br>
Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602<br>
T: 61 2 62689727&nbsp; F: 61 2 62689777</font></div>
        <font color="blue" size="3">
        <pre>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, 
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 
under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to 
collect, hold and use such information and any personal information contained in a 
response to this email, for any reasonable purpose in the ordinary course of 
Spherion's 
business, including forwarding this email internally or disclosing it to a third party. All 
personal information collected by Spherion will be handled in accordance with 
Spherion's Privacy Policy. If you have received this email in error, please notify the 
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s)
 supplied in 
this email and any attachments without first entering into a contractual agreement with 
Spherion. You further agree not to divulge any information contained in this document 
to any person(s) or entities without the express permission of Spherion.

        </pre>
        </font></blockquote>
    </blockquote>
  </blockquote>
  <br>
</blockquote>
</body>
</html>