Re: [ebxmlms-develop] Non-delivery notification

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 content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I agree with your point. I think the service type need not be
configurable as we only have a fixed number of types. It makes sense
for Hermes to "control" (or "hardcode") the service types, the
applications can then receive those error/notification messages using
specific listeners, or using an all-in-one listener, of their own
choices.<br>
<br>
Regards, -Patrick<br>
<br>
<br>
Mayne, Peter wrote:<br>
<blockquote
 cite="mid...@s-..."
 type="cite">
  <meta http-equiv="Content-Type" content="text/html; ">
  <title>Message</title>
  <meta content="MSHTML 6.00.2800.1264" name="GENERATOR">
  <div><span class="196104003-30032004"><font face="Arial" size="2">In
my case (as you probably know :-), I'm happy to have a single listener
for everything, because I want the back end to sort everything out.</font></span></div>
  <div><span class="196104003-30032004"></span>&nbsp;</div>
  <div><span class="196104003-30032004"><font face="Arial" size="2">Given
that an ApplicationContext (which&nbsp;provides the context for a listener)
already uses "service" as a&nbsp;parameter, it seems to me&nbsp;that you could
already distinguish extra Hermes-only message types for a "special"
listener by inventing a "CECID:Hermes:local-service-type:xyzzy"
service, for instance. (It might be good to make this special service
type customisable in msh.properties.xml, just in case.)&nbsp;There's no hard
programming here (beyond just another listener if required): a back end
that already recognises several service types shouldn't be too hard
pressed to recognise one more.</font></span></div>
  <div><span class="196104003-30032004"></span>&nbsp;</div>
  <div><span class="196104003-30032004"><font face="Arial" size="2">Any
messages have to be sent to a listener&nbsp;using some kind of message
format, and I don't see any need to invent&nbsp;a new format&nbsp;when
we're&nbsp;already using a perfectly good one. :-)</font></span></div>
  <div>&nbsp;</div>
  <div><span class="196104003-30032004"><font face="Arial" size="2">PJDM<br>
  </font></span><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> </div>
  <blockquote
 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> Patrick Yee [<a class="moz-txt-link-freetext" href="mailto:kc...@ce...">mailto:kc...@ce...</a>] <br>
    <b>Sent:</b> Tuesday, 30 March 2004 1:35 PM<br>
    <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a><br>
    <b>Subject:</b> Re: [ebxmlms-develop] Non-delivery notification<br>
    <br>
    </font></div>
Yes, I mean additional listeners to receive such information. Having
more listeners may make programming harder, but clearer.<br>
Regards, -Patrick</blockquote>
</blockquote>
<br>
</body>
</html>