Menu
▾
▴
ebxmlms-develop — Development discussions
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
|
Dec
(21) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(22) |
Feb
(41) |
Mar
(100) |
Apr
(113) |
May
(70) |
Jun
(89) |
Jul
(79) |
Aug
(17) |
Sep
(16) |
Oct
(9) |
Nov
(7) |
Dec
(22) |
| 2004 |
Jan
(42) |
Feb
(2) |
Mar
(20) |
Apr
(35) |
May
(18) |
Jun
(14) |
Jul
(12) |
Aug
(3) |
Sep
(5) |
Oct
(3) |
Nov
|
Dec
(1) |
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(3) |
Jun
(9) |
Jul
(18) |
Aug
(10) |
Sep
(12) |
Oct
(4) |
Nov
(4) |
Dec
(9) |
| 2006 |
Jan
(10) |
Feb
(2) |
Mar
(3) |
Apr
(3) |
May
(4) |
Jun
(9) |
Jul
(1) |
Aug
(1) |
Sep
(10) |
Oct
(29) |
Nov
(27) |
Dec
(14) |
| 2007 |
Jan
(9) |
Feb
(23) |
Mar
(3) |
Apr
(9) |
May
(21) |
Jun
(24) |
Jul
(21) |
Aug
(22) |
Sep
(11) |
Oct
(5) |
Nov
(3) |
Dec
(4) |
| 2008 |
Jan
(2) |
Feb
(5) |
Mar
(3) |
Apr
(22) |
May
(18) |
Jun
(14) |
Jul
(27) |
Aug
(20) |
Sep
(16) |
Oct
(17) |
Nov
(26) |
Dec
(48) |
| 2009 |
Jan
(37) |
Feb
(14) |
Mar
(39) |
Apr
(66) |
May
(140) |
Jun
(127) |
Jul
(78) |
Aug
(26) |
Sep
(24) |
Oct
(34) |
Nov
(10) |
Dec
(20) |
| 2010 |
Jan
(6) |
Feb
(7) |
Mar
(51) |
Apr
(49) |
May
(71) |
Jun
(57) |
Jul
(42) |
Aug
(53) |
Sep
(21) |
Oct
(4) |
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
(2) |
May
(3) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(1) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2012 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2014 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(4) |
Jun
(2) |
Jul
(4) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
(2) |
Dec
(6) |
| 2015 |
Jan
(1) |
Feb
(4) |
Mar
(11) |
Apr
(15) |
May
(12) |
Jun
(13) |
Jul
(7) |
Aug
(7) |
Sep
(5) |
Oct
(3) |
Nov
(5) |
Dec
(15) |
| 2016 |
Jan
(8) |
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(4) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
(6) |
Jul
(15) |
Aug
|
Sep
(1) |
Oct
(3) |
Nov
(3) |
Dec
(7) |
| 2018 |
Jan
(6) |
Feb
(8) |
Mar
(12) |
Apr
(6) |
May
(5) |
Jun
(3) |
Jul
(4) |
Aug
(6) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
(2) |
| 2019 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2021 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2022 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(9) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(29) |
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Patrick Y. <kc...@ce...> - 2003-05-27 04:32:20
|
<!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>
Peter,<br>
<br>
getPendingMessages() is for admin purpose. It lets you see how many
messages are in the "outbox" and lets you make a correct decision on
whether you should stop Hermes or not. <br>
<br>
getReceivedMessageIds() is for message receiving purpose. That is, if
you use NoMessageListenerImpl, there will be no URL posting to you, nor
onMessage() callback. You have to call that function to find out how
many messages are in the "inbox".<br>
<br>
So as you see, they are in two different categories. We don't see
inconsistency here.<br>
<br>
If I got it right, you want 2 independent components, one for message
receiving, another for status query. In that case, how about using
NoMessageListenerImpl in both. In the message receiving component, you
can call getReceivedMessageIds() and receive() to get the message. In
the status query component, you can always getReceivedMessageIds() and
check the status, and you never get the message out. What do you think
about this?<br>
<br>
The reason for using string for retry interval is historical. We want
to support string like "P2M" initially. Of course, it's still pending.<br>
<br>
getSentMessageIds() and getGivenUpMessageIds() do not exist now. <br>
<br>
Regards, -Patrick<br>
<br>
<br>
<font size="2"></font><br>
Mayne, Peter wrote:<br>
<blockquote type="cite"
cite="mid...@s-...">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator"
content="MS Exchange Server version 5.5.2654.45">
<title>Request musings (including nasty catch)</title>
<p><font size="2">I've just written a status servlet so I can display
the status of messages. There seems to be a rather nasty catch.</font> </p>
<p><font size="2">Request.getPendingMessages() ignores the
ApplicationContext, whereas Request.getReceivedMessageIds() requires
the ApplicationContext. In particular, getReceivedMessageIds() seems to
only return the messages that match the Request's ApplicationContext.</font></p>
<p><font size="2">Firstly, this seems to be inconsistent. Why should
getPendingMessages() return all the messages, whereas
getReceivedMessageIds() returns only what matches the
ApplicationContext?</font></p>
<p><font size="2">Secondly, and much more importantly, if I want to
discover all of the received messages, I have to specify the
ApplicationContext("*","*","*","*"). However, creating a Request with
this ApplicationContext registers this servlet as the global message
listener. Since this servlet only exists to look at the status of
messages, and particularly since I'm using the NoMessageListenerImpl
listener, all incoming messages are now thrown away until I reregister
my proper global listener.</font></p>
<p><font size="2">I really need a version of Request that doesn't
register the ApplicationContext, because without it, I can't look at
message statuses. Looking through the code, I see that I get registered
in Request if appContext!=null, and I also get registered when I send a
message using send()/sendReliably(), whether I like it or not (and I'm
pretty sure I don't like it).</font></p>
<p><font size="2">It would be much better if registering an
ApplicationContext was a separate function that is only done when I
want it to be, and not when something else feels like it. How about
making Request.register() a public method taking MessageListener and
ApplicationContext arguments, and not calling it from anywhere in
Hermes, including send()/sendReliably()?</font></p>
<p><font size="2">Other musings:</font> </p>
<p><font size="2">Why is the retryInterval passed to Request a
String? Why not just make it a long?</font> </p>
<p><font size="2">Request has a getPendingMessages() and
getReceivedMessageIds() (slightly inconsistent naming). Am I missing a
getSentMessageIds() and getGivenUpMessageIds(), or do they just not
exist?</font></p>
<p><font size="2">Request requires that I pass a toMSHUrl, even
though it is ovbiously not required. Passing null causes a
RequestException later. I'm not entirely sure that a message listener
and a transport type are required, either.</font></p>
<p><font size="2">PJDM</font> <br>
<font size="2">-- </font> <br>
<font size="2">Peter Mayne</font> <br>
<font size="2">Technology Consultant</font> <br>
<font size="2">Spherion Technology Solutions</font> <br>
<font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br>
<font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p>
<font size="3" color="BLUE">
<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>
</body>
</html>
|
|
From: Patrick Y. <kc...@ce...> - 2003-05-27 03:42:56
|
<!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>
Sorry for belated response. Thanks for your suggestion and we have
added a similar trick (just some property name change) to the nightly
build.<br>
<br>
Regards, -Patrick<br>
<br>
<br>
Mayne, Peter wrote:<br>
<blockquote type="cite"
cite="mid...@s-...">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator"
content="MS Exchange Server version 5.5.2654.45">
<title>RE: [ebxmlms-develop] Logging configuration</title>
<p><font size="2">Well, that turned out to be rather easy. In
Utility.java, replace configureLogger() and configureClientLogger with
the following. (Add a static boolean, make the methods synchronized,
detect "MSH/Log/log4jProperties", leave everything else as is.)</font></p>
<p><font size="2">Can this (or similar) go in the nightly build as
well, please?</font> </p>
<p><font size="2">-- BEGIN --</font> <br>
<font size="2"> static boolean loggingConfigured = false;</font> <br>
<font size="2"> public static synchronized void
configureLogger(Property prop, String umbrella) </font> <br>
<font size="2"> throws InitializationException {</font> </p>
<p><font size="2"> String log4j =
prop.get("MSH/Log/log4jProperties");</font> <br>
<font size="2"> if(log4j!=null)</font> <br>
<font size="2"> {</font> <br>
<font size="2"> if(!loggingConfigured)</font> <br>
<font size="2"> {</font> <br>
<font size="2"> System.err.println("Info: MSH log4j
properties file at " + log4j);</font> <br>
<font size="2">
org.apache.log4j.PropertyConfigurator.configure(log4j);</font> <br>
<font size="2"> loggingConfigured = true;</font> <br>
<font size="2"> }</font> <br>
<font size="2"> return;</font> <br>
<font size="2"> }</font> </p>
<p><font size="2"> String logPath =
prop.get(Constants.PROPERTY_LOG_PATH);</font> <br>
<font size="2"> String logFile =
prop.get(Constants.PROPERTY_LOG_FILE);</font> <br>
<font size="2"> String logLevel =
prop.get(Constants.PROPERTY_LOG_LEVEL);</font> <br>
<font size="2"> String logSize =
prop.get(Constants.PROPERTY_MAX_LOG_SIZE);</font> </p>
<p><font size="2"> setLogger(logPath, logFile, logLevel,
logSize, umbrella);</font> <br>
<font size="2"> }</font> </p>
<p><font size="2"> public static synchronized void
configureClientLogger(Property prop, String umbrella)</font> <br>
<font size="2"> throws InitializationException {</font> </p>
<p><font size="2"> String log4j =
prop.get("MSH/Log/log4jProperties");</font> <br>
<font size="2"> if(log4j!=null)</font> <br>
<font size="2"> {</font> <br>
<font size="2"> if(!loggingConfigured)</font> <br>
<font size="2"> {</font> <br>
<font size="2"> System.err.println("Info: MSH
log4j properties file at " + log4j);</font> <br>
<font size="2">
org.apache.log4j.PropertyConfigurator.configure(log4j);</font> <br>
<font size="2"> loggingConfigured = true;</font> <br>
<font size="2"> }</font> <br>
<font size="2"> return;</font> <br>
<font size="2"> }</font> </p>
<p><font size="2"> String logPath =
prop.get(Constants.PROPERTY_REQUEST_LOG_PATH);</font> <br>
<font size="2"> String logFile =
prop.get(Constants.PROPERTY_REQUEST_LOG_FILE);</font> <br>
<font size="2"> String logLevel =
prop.get(Constants.PROPERTY_REQUEST_LOG_LEVEL);</font> <br>
<font size="2"> String logSize =
prop.get(Constants.PROPERTY_REQUEST_MAX_LOG_SIZE);</font> </p>
<p><font size="2"> setLogger(logPath, logFile, logLevel,
logSize, umbrella);</font> <br>
<font size="2"> }</font> <br>
<font size="2">-- END --</font> </p>
<p><font size="2">PJDM</font> <br>
<font size="2">--</font> <br>
<font size="2">Peter Mayne</font> <br>
<font size="2">Technology Consultant</font> <br>
<font size="2">Spherion Technology Solutions</font> <br>
<font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br>
<font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p>
<font size="3" color="BLUE">
<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>
</body>
</html>
|
|
From: Patrick Y. <kc...@ce...> - 2003-05-27 01:50:13
|
<!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> 4.1.x is usable, as Peter said, you need to do some patching. Please refer to:<br> <a class="moz-txt-link-freetext" href="http://sourceforge.net/mailarchive/message.php?msg_id=3837643">http://sourceforge.net/mailarchive/message.php?msg_id=3837643</a><br> <br> for more information.<br> <br> Regards, -Patrick<br> <br> <br> Jeff A. Manning wrote:<br> <blockquote type="cite" cite="mid002201c323b1$88626840$6401a8c0@TheSun"> <meta http-equiv="Content-Type" content="text/html; "> <title>Message</title> <meta content="MSHTML 6.00.2600.0" name="GENERATOR"> <div><span class="157262617-26052003"><font face="Arial" color="#0000ff" size="2"><em>Hi Patrick,</em></font></span></div> <div><span class="157262617-26052003"><em></em></span> </div> <div><span class="157262617-26052003"><em><font face="Arial" color="#0000ff" size="2">Thanks for your time to reply to my question.</font></em></span></div> <div><span class="157262617-26052003"><em></em></span> </div> <div><span class="157262617-26052003"><em><font face="Arial" color="#0000ff" size="2">I'm currently using qmail and am most interested in knowing the version of Tomcat</font></em></span></div> <div><span class="157262617-26052003"><em><font face="Arial" color="#0000ff" size="2">you recommend for ebxmlms? </font></em></span></div> <div><span class="157262617-26052003"><em></em></span> </div> <div><span class="157262617-26052003"><em><font face="Arial" color="#0000ff" size="2">I have been unable to use 4.1.24 but successful if I down grade to 4.0.6 Tomcat.</font></em></span></div> <div><span class="157262617-26052003"><em></em></span> </div> <div><span class="157262617-26052003"><em><font face="Arial" color="#0000ff" size="2">I'd appreciate your insights on the version you're currently using.</font></em></span></div> <div><span class="157262617-26052003"><em></em></span> </div> <div><span class="157262617-26052003"><em><font face="Arial" color="#0000ff" size="2">Thanks!</font></em></span></div> <div><span class="157262617-26052003"><em></em></span> </div> <div><span class="157262617-26052003"><em><font face="Arial" color="#0000ff" size="2">Jeff Manning</font></em></span></div> <blockquote style="margin-right: 0px;"> <div class="OutlookMessageHeader" lang="en-us" dir="ltr" align="left"><font face="Tahoma" size="2">-----Original Message-----<br> <b>From:</b> <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> [<a class="moz-txt-link-freetext" href="mailto:ebx...@li...">mailto:ebx...@li...</a>] <b>On Behalf Of </b>Patrick Yee<br> <b>Sent:</b> Monday, May 26, 2003 3:37 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] RE: Version of Tomcat<br> <br> </font></div> In our testing environment, we use the IMAP package from Washington U. <br> <a class="moz-txt-link-freetext" href="http://www.washington.edu/imap/">http://www.washington.edu/imap/</a><br> <br> And we have confidence that Hermes can work with QMail also. That part is pretty standard.<br> <br> Regards, -Patrick<br> <br> <br> Jeff Manning wrote:<br> <blockquote cite="mid000d01c31faf$8800d680$0401a8c0@TheSun" type="cite"> <pre wrap="">Hi CY, Which email server are you using? Jeff -----Original Message----- From: Ng Chi Yuen [Cyng] [<a class="moz-txt-link-freetext" href="mailto:cy...@cs...">mailto:cy...@cs...</a>] Sent: Wednesday, May 21, 2003 8:30 AM To: <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> Cc: Jeff Manning Subject: RE: Version of Tomcat Hi Jeff, </pre> <blockquote type="cite"> <pre wrap="">I'm fairly new (48 hrs) with Postgres. I'm an Oracle person. Since my last email I found the tables under supplier, have dropped them, and rerun the RunLoop script. Now I'm fighting with qmail user logins and passwords. I'm trying to setup vmailmgr (what a pain) to have a simpler gui for dealing with qmail - though I am about to toss qmail for something simpler. </pre> </blockquote> <pre wrap=""><!----> Would you share with us how your project makes use of Hermes and qmail? I know nothing about qmail at all </pre> <blockquote type="cite"> <pre wrap="">I'm cautiously optimistic that I'll have this running shortly - due in large part to your help! I appreciate your time to reply to my pitiful pleas! </pre> </blockquote> <pre wrap=""><!----> From now on, you can simply email to <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> or <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> We have all friends around and we can share our experience and problems. Hope you will like Hermes. </pre> <blockquote type="cite"> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">Discovering this, I've restarted tomcat and initially found that postgres was not running. After restarting postgres I now receive (I've only included the 'root cause' portion of the trace): </pre> </blockquote> <blockquote type="cite"> <pre wrap=""> root cause hk.hku.cecid.phoenix.message.handler.MessageServiceHandlerExceptio n: ERROR: Relation 'mshconfig' already exists </pre> </blockquote> <pre wrap=""> This is due to the fact that some tables have already exist in your DB with old table schema. Please drop all tables and restart </pre> </blockquote> </blockquote> <pre wrap=""><!----> </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">Tomcat and Hermes and the new tables will be created again. </pre> </blockquote> </blockquote> <pre wrap=""><!----> Regards, CY ------------------------------------------------------------------------ ---- Ng Chi Yuen, CY. <a class="moz-txt-link-abbreviated" href="mailto:cy...@ce...">cy...@ce...</a> <a class="moz-txt-link-freetext" href="http://www.cecid.hku.hk/">http://www.cecid.hku.hk/</a> Technology Officer, Centre for E-Commerce Infrastructure Development, The University of Hong Kong ------------------------------------------------------------------------ ---- ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. <a class="moz-txt-link-freetext" href="http://www.objectstore.net/sourceforge">http://www.objectstore.net/sourceforge</a> _______________________________________________ ebxmlms-develop mailing list <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a> </pre> </blockquote> ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. <a class="moz-txt-link-freetext" href="http://www.objectstore.net/sourceforge">http://www.objectstore.net/sourceforge</a> _______________________________________________ ebxmlms-develop mailing list <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a> </blockquote> </blockquote> </body> </html> |
|
From: Jeff A. M. <Je...@VM...> - 2003-05-26 18:04:42
|
Hi Patrick, Thanks for your time to reply to my question. I'm currently using qmail and am most interested in knowing the version of Tomcat you recommend for ebxmlms? I have been unable to use 4.1.24 but successful if I down grade to 4.0.6 Tomcat. I'd appreciate your insights on the version you're currently using. Thanks! Jeff Manning -----Original Message----- From: ebx...@li... [mailto:ebx...@li...] On Behalf Of Patrick Yee Sent: Monday, May 26, 2003 3:37 AM To: ebx...@li... Subject: Re: [ebxmlms-develop] RE: Version of Tomcat In our testing environment, we use the IMAP package from Washington U. http://www.washington.edu/imap/ And we have confidence that Hermes can work with QMail also. That part is pretty standard. Regards, -Patrick Jeff Manning wrote: Hi CY, Which email server are you using? Jeff -----Original Message----- From: Ng Chi Yuen [Cyng] [mailto:cy...@cs...] Sent: Wednesday, May 21, 2003 8:30 AM To: ebx...@li... Cc: Jeff Manning Subject: RE: Version of Tomcat Hi Jeff, I'm fairly new (48 hrs) with Postgres. I'm an Oracle person. Since my last email I found the tables under supplier, have dropped them, and rerun the RunLoop script. Now I'm fighting with qmail user logins and passwords. I'm trying to setup vmailmgr (what a pain) to have a simpler gui for dealing with qmail - though I am about to toss qmail for something simpler. Would you share with us how your project makes use of Hermes and qmail? I know nothing about qmail at all I'm cautiously optimistic that I'll have this running shortly - due in large part to your help! I appreciate your time to reply to my pitiful pleas! From now on, you can simply email to ebx...@li... or ebx...@li... We have all friends around and we can share our experience and problems. Hope you will like Hermes. Discovering this, I've restarted tomcat and initially found that postgres was not running. After restarting postgres I now receive (I've only included the 'root cause' portion of the trace): root cause hk.hku.cecid.phoenix.message.handler.MessageServiceHandlerExceptio n: ERROR: Relation 'mshconfig' already exists This is due to the fact that some tables have already exist in your DB with old table schema. Please drop all tables and restart Tomcat and Hermes and the new tables will be created again. Regards, CY ------------------------------------------------------------------------ ---- Ng Chi Yuen, CY. cy...@ce... http://www.cecid.hku.hk/ Technology Officer, Centre for E-Commerce Infrastructure Development, The University of Hong Kong ------------------------------------------------------------------------ ---- ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ ebxmlms-develop mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ ebxmlms-develop mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop |
|
From: Patrick Y. <kc...@ce...> - 2003-05-26 10:59:08
|
<!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> Yes Hermes is doing that.<br> How about to write a simple program which involves the XSLT and CANONICALIZATION using exactly the way as Hermes. And then try to verfiy the signature generated by that program by using BusinessConnect. I guess it will be simpler to modify the XSLT/Canonicalization parameters, and test back and forth, in that program. Just my $0.02.<br> <br> Regards, -Patrick<br> <br> Mayne, Peter wrote:<br> <blockquote type="cite" cite="mid...@s-..."> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 5.5.2654.45"> <title>Digital signatures</title> <p><font size="2">We're sending signed ebXML messages to Tibco BusinessConnect. However, BusinesConnect isn't verifying the signatures.</font> </p> <p><font size="2">The response from Tibco is</font> </p> <p><font size="2"><quote></font> <br> <font size="2">-----------------------------------------------------------------------</font> <br> <font size="2">The Digest value for the envelope fails to match.</font> </p> <p><font size="2"> The process of Digest Calculation is as follows.</font> <br> <font size="2"> a> Apply optional list of transforms which can include XPATH, XSLT, CANONICALIZATION.</font> <br> <font size="2"> b> Use the algorithm mentioned in DigestMethod to calculate the digest.</font> <br> <font size="2"> Note that if step (a) is omitted and a plain digest is calculated, the signature verification will fail.</font> <br> <font size="2">-----------------------------------------------------------------------</font> <br> <font size="2"></quote></font> </p> <p><font size="2">I presume Hermes is doing this? What can we do to facilitate checking digital signature verification with BusinessConnect?</font></p> <p><font size="2">PJDM</font> <br> <font size="2">-- </font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p> <font size="3" color="BLUE"> <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> </body> </html> |
|
From: Patrick Y. <kc...@ce...> - 2003-05-26 10:39:35
|
<!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> In our testing environment, we use the IMAP package from Washington U. <br> <a class="moz-txt-link-freetext" href="http://www.washington.edu/imap/">http://www.washington.edu/imap/</a><br> <br> And we have confidence that Hermes can work with QMail also. That part is pretty standard.<br> <br> Regards, -Patrick<br> <br> <br> Jeff Manning wrote:<br> <blockquote type="cite" cite="mid000d01c31faf$8800d680$0401a8c0@TheSun"> <pre wrap="">Hi CY, Which email server are you using? Jeff -----Original Message----- From: Ng Chi Yuen [Cyng] [<a class="moz-txt-link-freetext" href="mailto:cy...@cs...">mailto:cy...@cs...</a>] Sent: Wednesday, May 21, 2003 8:30 AM To: <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> Cc: Jeff Manning Subject: RE: Version of Tomcat Hi Jeff, </pre> <blockquote type="cite"> <pre wrap="">I'm fairly new (48 hrs) with Postgres. I'm an Oracle person. Since my last email I found the tables under supplier, have dropped them, and rerun the RunLoop script. Now I'm fighting with qmail user logins and passwords. I'm trying to setup vmailmgr (what a pain) to have a simpler gui for dealing with qmail - though I am about to toss qmail for something simpler. </pre> </blockquote> <pre wrap=""><!----> Would you share with us how your project makes use of Hermes and qmail? I know nothing about qmail at all </pre> <blockquote type="cite"> <pre wrap="">I'm cautiously optimistic that I'll have this running shortly - due in large part to your help! I appreciate your time to reply to my pitiful pleas! </pre> </blockquote> <pre wrap=""><!----> From now on, you can simply email to <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> or <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> We have all friends around and we can share our experience and problems. Hope you will like Hermes. </pre> <blockquote type="cite"> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">Discovering this, I've restarted tomcat and initially found that postgres was not running. After restarting postgres I now receive (I've only included the 'root cause' portion of the trace): </pre> </blockquote> <blockquote type="cite"> <pre wrap=""> root cause hk.hku.cecid.phoenix.message.handler.MessageServiceHandlerExceptio n: ERROR: Relation 'mshconfig' already exists </pre> </blockquote> <pre wrap=""> This is due to the fact that some tables have already exist in your DB with old table schema. Please drop all tables and restart </pre> </blockquote> </blockquote> <pre wrap=""><!----> </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">Tomcat and Hermes and the new tables will be created again. </pre> </blockquote> </blockquote> <pre wrap=""><!----> Regards, CY ------------------------------------------------------------------------ ---- Ng Chi Yuen, CY. <a class="moz-txt-link-abbreviated" href="mailto:cy...@ce...">cy...@ce...</a> <a class="moz-txt-link-freetext" href="http://www.cecid.hku.hk/">http://www.cecid.hku.hk/</a> Technology Officer, Centre for E-Commerce Infrastructure Development, The University of Hong Kong ------------------------------------------------------------------------ ---- ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. <a class="moz-txt-link-freetext" href="http://www.objectstore.net/sourceforge">http://www.objectstore.net/sourceforge</a> _______________________________________________ ebxmlms-develop mailing list <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> <a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a> </pre> </blockquote> </body> </html> |
|
From: Simon L. <ky...@ce...> - 2003-05-26 03:43:11
|
Hi Peter,
Our comment in blue.
Best Regards,
Simon
----- Original Message -----=20
From: Patrick Yee=20
To: ebx...@li... ; Mayne, Peter ; =
ebm...@li...=20
Sent: Monday, May 26, 2003 11:02 AM
Subject: [ebmail-develop] Re: [ebxmlms-develop] ebMail comments
Peter,=20
I guess you have to send this mail to =
ebm...@li.... I have forwarded there. :-)
Regards, -Patrick
Mayne, Peter wrote:
I've just tried out ebMail built from source. Is anyone that you =
know of using it?=20
The instructions say that there are two directores "core" and =
"plugin". The source I downloaded had two directories "ebmail" and =
"poPlugin".
Substituting "ebmail" for "core", I built the ebmail jar with "ant =
compile" and "ant jar". That seemed to work, I could then run the =
application using "ant run".
Substituting "poPlugin" for "plugin", I then tried building the =
plugin. The instructions say to use "ant compile", but this didn't =
produce a plugin. I had to look at build.xml to figure out I have to do =
"ant build".
-------------------------------------------------------------------------=
---
Sorry for the misleading documentation and thanks for pointing these =
errors for us. We will fix the problem soon.
-------------------------------------------------------------------------=
---
When I send an email and look at the result on the mail server, =
there is only one attachment "Part 1.1" containing the SOAP envelope, =
with a reference to "cid:0". However, there is no other attachment =
containing the purchase order, which I assume is supposed to be there. =
(The "View Message Source" option shows the header and payload 1, but =
payload 1 obviously isn't being sent as an attachment.)
-------------------------------------------------------------------------=
---
I am not sure whether I get it correct. But as you see a reference =
to cid:0 has been added to the SOAP envelope, I guess the "PO" =
attachment data should be already there.
What is the way for you to see the message in the mail server? We =
use pine to look at the message, and look into the /var/mail/xxx file =
directly as well. There are 2 parts in the message, which are the SOAP =
envelope and the PO xml attachment. If you don't mind, could you use =
your ebmail to send a message to my mail address (ky...@ce...)?
-------------------------------------------------------------------------=
---
I couldn't figure out how to create another mail folder to move =
messages to.=20
-------------------------------------------------------------------------=
---
To create another folder, you could right click the "All Messages" =
node in the folder tree pane and select "Create Folder" and a new folder =
should be created. There are several ways to move messages into it, but =
the simplest one is to "drag and drop" the message into the destination =
folder.
-------------------------------------------------------------------------=
---
If there is a problem with the mail server and the message can't be =
sent, the newly created message vanishes and I have to start again. This =
is unacceptable.
-------------------------------------------------------------------------=
---
Actually we have planed to add this "retry" feature in our next =
version. Thanks for your comment!
-------------------------------------------------------------------------=
---
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.
=20
------------------------------------------------------- This SF.net =
email is sponsored by: ObjectStore. If flattening out C++ or Java code =
to make your application fit in a relational database is painful, don't =
do it! Check out ObjectStore. Now part of Progress Software. =
http://www.objectstore.net/sourceforge =
_______________________________________________ ebmail-develop mailing =
list ebm...@li... =
https://lists.sourceforge.net/lists/listinfo/ebmail-develop
|
|
From: Patrick Y. <kc...@ce...> - 2003-05-26 03:10:32
|
<!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> Peter, <br> <br> I guess you have to send this mail to <a class="moz-txt-link-abbreviated" href="mailto:ebm...@li...">ebm...@li...</a>. I have forwarded there. :-)<br> <br> Regards, -Patrick<br> <br> <br> Mayne, Peter wrote:<br> <blockquote type="cite" cite="mid...@s-..."> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 5.5.2654.45"> <title>ebMail comments</title> <p><font size="2">I've just tried out ebMail built from source. Is anyone that you know of using it?</font> </p> <p><font size="2">The instructions say that there are two directores "core" and "plugin". The source I downloaded had two directories "ebmail" and "poPlugin".</font></p> <p><font size="2">Substituting "ebmail" for "core", I built the ebmail jar with "ant compile" and "ant jar". That seemed to work, I could then run the application using "ant run".</font></p> <p><font size="2">Substituting "poPlugin" for "plugin", I then tried building the plugin. The instructions say to use "ant compile", but this didn't produce a plugin. I had to look at build.xml to figure out I have to do "ant build".</font></p> <p><font size="2">When I send an email and look at the result on the mail server, there is only one attachment "Part 1.1" containing the SOAP envelope, with a reference to <a class="moz-txt-link-rfc2396E" href="cid:0">"cid:0"</a>. However, there is no other attachment containing the purchase order, which I assume is supposed to be there. (The "View Message Source" option shows the header and payload 1, but payload 1 obviously isn't being sent as an attachment.)</font></p> <p><font size="2">I couldn't figure out how to create another mail folder to move messages to.</font> </p> <p><font size="2">If there is a problem with the mail server and the message can't be sent, the newly created message vanishes and I have to start again. This is unacceptable.</font></p> <p><font size="2">PJDM</font> <br> <font size="2">-- </font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p> <font size="3" color="BLUE"> <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> </body> </html> |
|
From: Ng C. Y. [Cyng] <cy...@cs...> - 2003-05-21 16:27:14
|
Hi Jeff,
> I'm fairly new (48 hrs) with Postgres. I'm an Oracle person.
>
> Since my last email I found the tables under supplier, have
> dropped them, and rerun the RunLoop script.
>
> Now I'm fighting with qmail user logins and passwords. I'm
> trying to setup vmailmgr (what a pain) to have a simpler
> gui for dealing with qmail - though I am about to toss
> qmail for something simpler.
Would you share with us how your project makes use of Hermes
and qmail? I know nothing about qmail at all
> I'm cautiously optimistic that I'll have this running
> shortly - due in large part to your help!
>
> I appreciate your time to reply to my pitiful pleas!
From now on, you can simply email to
ebx...@li... or
ebx...@li...
We have all friends around and we can share our experience and problems.
Hope you will like Hermes.
> > > Discovering this, I've restarted tomcat and initially found that
> > > postgres was not running. After restarting postgres I now receive
> > > (I've only included the 'root cause' portion of the trace):
> >
> > > root cause
> > > hk.hku.cecid.phoenix.message.handler.MessageServiceHandlerException:
> > > ERROR: Relation 'mshconfig' already exists
> >
> > This is due to the fact that some tables have already exist in
> > your DB with old table schema. Please drop all tables and restart
> > Tomcat and Hermes and the new tables will be created again.
Regards,
CY
----------------------------------------------------------------------------
Ng Chi Yuen, CY. cy...@ce... http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
----------------------------------------------------------------------------
|
|
From: Jeff M. <Je...@St...> - 2003-05-21 16:14:15
|
Hi CY,
Which email server are you using?
Jeff
-----Original Message-----
From: Ng Chi Yuen [Cyng] [mailto:cy...@cs...]
Sent: Wednesday, May 21, 2003 8:30 AM
To: ebx...@li...
Cc: Jeff Manning
Subject: RE: Version of Tomcat
Hi Jeff,
> I'm fairly new (48 hrs) with Postgres. I'm an Oracle person.
>
> Since my last email I found the tables under supplier, have dropped
> them, and rerun the RunLoop script.
>
> Now I'm fighting with qmail user logins and passwords. I'm trying to
> setup vmailmgr (what a pain) to have a simpler gui for dealing with
> qmail - though I am about to toss qmail for something simpler.
Would you share with us how your project makes use of Hermes and
qmail? I know nothing about qmail at all
> I'm cautiously optimistic that I'll have this running
> shortly - due in large part to your help!
>
> I appreciate your time to reply to my pitiful pleas!
From now on, you can simply email to
ebx...@li... or
ebx...@li...
We have all friends around and we can share our experience and problems.
Hope you will like Hermes.
> > > Discovering this, I've restarted tomcat and initially found that
> > > postgres was not running. After restarting postgres I now receive
> > > (I've only included the 'root cause' portion of the trace):
> >
> > > root cause
> > > hk.hku.cecid.phoenix.message.handler.MessageServiceHandlerExceptio
> > > n:
> > > ERROR: Relation 'mshconfig' already exists
> >
> > This is due to the fact that some tables have already exist
> > in your DB with old table schema. Please drop all tables and restart
> > Tomcat and Hermes and the new tables will be created again.
Regards,
CY
------------------------------------------------------------------------
----
Ng Chi Yuen, CY. cy...@ce... http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
------------------------------------------------------------------------
----
|
|
From: Patrick Y. <kc...@ce...> - 2003-05-19 07:16:13
|
<!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> Sorry I know nothing about JMS.. Are there any URL for JMS destinations?<br> I agree that the MessageServiceHandlerConfig (and thus the mechanism of MessageListener) should be modified. The current implementation is not that flexible. Do you have any idea on how the architecture should be?<br> <br> In the meantime, an adhoc solution is to implement JMS clients with "tunnelling" through HTTP clients, or "tunnelling" through in-process clients. :-)<br> <br> Regards, -Patrick<br> <br> <br> Mayne, Peter wrote:<br> <blockquote type="cite" cite="mid...@s-..."> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 5.5.2654.45"> <title>RE: [ebxmlms-develop] JMS receiver</title> <p><font size="2">Yes, but what about the details?</font> </p> <p><font size="2">Ideally, the MessageListener interface would allow anything to be plugged into it. However, it is constrained by having to use a URL, which obviously isn't suited for plugins such as JMS. The use of MessageListener.getClientUrl() isn't numerous throughout Hermes, but the idea that a MessageListener has a URL (which may be null), and that URL's scheme is one of "http", "https", or "smtp", is fairly embedded. This precludes using an alternative plugin for JMS, FTP, etc.</font></p> <p><font size="2">For instance, the MessageServiceHandlerConfig constructor has a transportType parameter (I'm not sure why, I would have thought the transport type was implicit in the MessageListener), which must be one of the above schemes. There is no allowance for anything else.</font></p> <p><font size="2">Providing for different MessageListeners might be more difficult than it looks.</font> </p> <p><font size="2">PJDM</font> <br> <font size="2">--</font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p> <font size="3" color="BLUE"> <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> </body> </html> |
|
From: Ronald v. K. <rv...@ab...> - 2003-05-16 09:57:46
|
I think it would be pretty much the same as with imap/smtp. Using a factory to load the jms provider (for specific jms servers, mq, sonic, jbosmq) and then specifying a server, queue and additionally a username/password for security. -----Oorspronkelijk bericht----- Van: Mayne, Peter [mailto:Pet...@ap...] Verzonden: vrijdag 16 mei 2003 6:33 Aan: 'ebx...@li...' Onderwerp: [ebxmlms-develop] JMS receiver Adding a JMS receiver to Hermes sounds like a resonable addition to me. If a JMS receiver was to be added (in addition to the filesystem and HTTP receivers), how would it be specified? PJDM -- Peter Mayne Technology Consultant Spherion Technology Solutions Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 T: 61 2 62689727 F: 61 2 62689777 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. |
|
From: Patrick Y. <kc...@ce...> - 2003-05-13 10:12:48
|
<!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> The patch is added now. Thanks for the patch and reminder. <br> Regards, -Patrick<br> <br> Gait Boxman wrote:<br> <blockquote type="cite" cite="mid008701c31936$25626680$cc04140a@gaitlap"> <meta http-equiv="Content-Type" content="text/html; "> <meta content="MSHTML 6.00.2800.1170" name="GENERATOR"> <style></style> <div><font face="Arial" size="2">I believe I sent this patch before, but it doesn't appear to be committed in CVS:</font></div> <div><font size="2"><font face="Arial">per ebMS2, the Actor attribute on the SyncReply element is mandatory to be set to </font><a href="http://schemas.xmlsoap.org/soap/actor/next"><font face="Arial">http://schemas.xmlsoap.org/soap/actor/next</font></a><font face="Arial">,</font></font></div> <div> </div> <div><font face="Arial" size="2">the diff is below</font></div> <div><font size="2"> <p>cvs diff SyncReply.java (in directory <a class="moz-txt-link-freetext" href="C:\temp\ebxmlms\src\hk\hku\cecid\phoenix\message\packaging\">C:\temp\ebxmlms\src\hk\hku\cecid\phoenix\message\packaging\</a>)</p> <p>Index: SyncReply.java</p> <p>===================================================================</p> <p>RCS file: /cvsroot/ebxmlms/ebxmlms/src/hk/hku/cecid/phoenix/message/packaging/SyncReply.java,v</p> <p>retrieving revision 1.3</p> <p>diff -r1.3 SyncReply.java</p> <p>96a97,99</p> </font><font color="#0000ff" size="2"> <p>> static final String ACTOR_NEXT_MSH_SCHEMAS =</p> <p>> <a class="moz-txt-link-rfc2396E" href="http://schemas.xmlsoap.org/soap/actor/next">"http://schemas.xmlsoap.org/soap/actor/next"</a>;</p> <p>> </p> </font><font size="2"> <p>99a103</p> </font><font color="#0000ff" size="2"> <p>> setActor( ACTOR_NEXT_MSH_SCHEMAS );</p> </font></div> <div><font face="Arial" size="2">~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br> Gait Boxman<br> Manager Advanced Technology & Standards<br> TIE Product Development BV<br> Amsterdam, The Netherlands<br> Tel: +31 20 658 9091 Fax: +31 20 658 9945<br> E-mail: <a href="mailto:gai...@ti...">gai...@ti...</a> WWW: <a href="http://www.TIEglobal.com">www.TIEglobal.com</a><br> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</font></div> </blockquote> </body> </html> |
|
From: Gait B. <gai...@ti...> - 2003-05-13 09:53:56
|
I believe I sent this patch before, but it doesn't appear to be = committed in CVS: per ebMS2, the Actor attribute on the SyncReply element is mandatory to = be set to http://schemas.xmlsoap.org/soap/actor/next, the diff is below cvs diff SyncReply.java (in directory = C:\temp\ebxmlms\src\hk\hku\cecid\phoenix\message\packaging\) Index: SyncReply.java =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: = /cvsroot/ebxmlms/ebxmlms/src/hk/hku/cecid/phoenix/message/packaging/SyncR= eply.java,v retrieving revision 1.3 diff -r1.3 SyncReply.java 96a97,99 > static final String ACTOR_NEXT_MSH_SCHEMAS =3D > "http://schemas.xmlsoap.org/soap/actor/next"; >=20 99a103 > setActor( ACTOR_NEXT_MSH_SCHEMAS ); ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Gait Boxman Manager Advanced Technology & Standards TIE Product Development BV Amsterdam, The Netherlands Tel: +31 20 658 9091 Fax: +31 20 658 9945 E-mail: gai...@ti... WWW: www.TIEglobal.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
|
From: Gait B. <gai...@ti...> - 2003-05-13 06:40:17
|
RE: [ebxmlms-develop] Using alternative signing key algorithmsthnx = Peter, that was the section that I remembered triggering me on the MSH = signing earlier. Yes, per the spec it is the MSH that must sign the message, and the = client (application) may sign it as well. When the client signs the = message, the MSH must as well. When you send something to another party, you can only send it to the = endpoint URL, so the acknowledgment will have to be signed by the MSH = (message acks are never signed by the app as it is not involved, = however, a separate business ack may be sent and signed by the app, but = that's a regular message as far as ebMS is concerned). Still, this does not imply that only one key pair is in use for any = given MSH. While the ack key will be exactly one per MSH, the key for = outgoing messages might be different. Which signatures you accept only = depends on the certificates that are trusted. There may be a key K1 = saying 'MSH Y on behalf of client A' and another K2 saying 'MSH Y on = behalf of client B'. For the ack, the only thing you need to say is 'MSH = Y' (K3), since the ack does not imply routing to either client A or B, = just that MSH Y got the message intact. Then, partners of client A will = only trust the certificates for their partner (K1 and K3) while partners = of client B will only trust certificates for K2 and K3. And yet, it is still the MSH that must do the signing of the message, at = least for the first dsig entry in the message, so we need to change the = behaviour such that: Request provides a way to add one or more client signature(s) to the = message before sending it over to the MSH (suggest addSignature...). Request provides a way to specifically request the MSH to add a = signature of its own (suggest setSigned...) Request provides a way to specify an alternate key location fo the MSH = signature (could use setSign here) The MSH signs with a default key (from msh.properties.xml, we need = entries for this as it may not be the same as for acks) or provided key = (through setSign) whenever: - a signature was explicitly requested with setSigned(true), or - a signature was explicitly set with setSign(....), or - a client signature was added with addSignature or directly on the = EbxmlMessage. And we need to make sure that when the MSH adds a signature, it adds it = before any client signatures. sorry, no patches on this one, I have to revert back to my paid project. One open issue is who should verify the client sigs, the MSH or the = client? Anyway we probably also need a version of EbxmlMessage.verify = that verifies a specific signature. --Gait. Request.setSign merely forwards these parameters to the MSH, while the = MSH does the actual signing prior to sending out the message (I would = suggest having another property signed that triggers the signing by the = MSH). Client signing is to be done on the EbxmlMessage directly prior to = sending, .=20 ----- Original Message -----=20 From: Mayne, Peter=20 To: 'ebx...@li...'=20 Sent: Tuesday, May 13, 2003 4:16 AM Subject: RE: [ebxmlms-develop] Using alternative signing key = algorithms From the ebXML spec:=20 <quote>=20 1.2.4 Modes of operation=20 Security Services - digital signature creation and=20 verification, encryption, authentication and authorization.=20 These services MAY be used by other components of the=20 MSH including the Header Processing and Header Parsing=20 components.=20 4.1.1 Signature Element=20 If there is more than one Signature element contained=20 within the SOAP Header, the first MUST represent the digital signature = of the ebXML Message as signed=20 by the From Party MSH in conformance with section 4.1.=20 </quote>=20 A casual reading of the above would lead me to believe that the = message must be signed by the MSH, not by a client. Admittedly, I = couldn't find anywhere that says what certificates may be used, so I = suspect that doing it the way that it is makes no difference. A consequence is that I can send a message to Party A (the actual = trading partner), and get an acknowledgement from Party B (the MSH). Do = you allow for that? 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 -----Original Message-----=20 From: Patrick Yee [mailto:kc...@ce...]=20 Sent: Tuesday, 13 May 2003 11:22 AM=20 To: ebx...@li...=20 Subject: Re: [ebxmlms-develop] Using alternative signing key = algorithms=20 For this, we had a debate internally before. We concluded that the = nature of message signing and acknowledgement signing are different. = Message signing is used to testify the message (and the most important, = the payloads) is sent by the real sender. Acknowledgement signing is = used to testify the message has been safely arrived at the real = destination (i.e. the real MSH). Following this model, we can accept all = applications to "share" the private key for signing acknowledgement = messages. While at the same time, we think the non-repudiation property = of message signing drives us to think carefully about holding all keys = in a central point. Basically our concept is following the ASP model. As = a result, as you can see in the current desi gn, we perform the signing = in Request object, i.e. in the client side. Regards, -Patrick=20 Mayne, Peter wrote:=20 >> I agree that there should also be a way of having the MSH sign the = outgoing message, so there wouldn't=20 >> need to be more than one copy of the private key lying around.=20 >=20 > Yes and no. It may be more handy. But I'm just feeling a bit = unsecured to have MSH to hold the private=20 > key for the application. What do you think?=20 But Hermes already has the private key for message signing = (MSH/DigitalSignature/AckSign/KeyStore) so it can sign acknowledgements. = I don't see any way around that. Given that the MSH must have a copy of the private key (like it or = not), it makes sense under some circumstances to have that be the only = copy of the private key. As usual, there's more than one configuration to think about.=20 1) One single key at the MSH to do all outgoing message signing = (including originals and acknowledgements). This makes sense for a = single business sending messages to trading partners. 2) All messages signed by the message clients. This makes sense for = Gait's suggestion of running the MSH in ASP mode for different clients. = The trouble with this is that message acknowledgements are still signed = by the MSH, rather than a client's key, so running Hermes in ASP mode = won't currently work. 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:=20 (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=20 (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.=20 (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.=20 =20 ------------------------------------------------------- Enterprise = Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only = event dedicated to issues related to Linux enterprise solutions = www.enterpriselinuxforum.com = _______________________________________________ ebxmlms-develop mailing = list ebx...@li... = https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop |
|
From: Patrick Y. <kc...@ce...> - 2003-05-13 01:42:59
|
<!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> Hmm.. the specification permits us to do what we are doing now, right? If this is true, how come the TIBCO one rejects a legal message? :-) OK, let's accept it as is, and the only thing we can change now is Hermes.<br> <br> It seems that it is no easy way. It is not related to PublicKeyFinder. Let's call it "key info formatter". So, does it make sense to add another hook (!!) to customize this part?<br> <br> What do you think about the "external hook" approach? Are there too many?<br> <br> Regards, -Patrick<br> <br> <br> Mayne, Peter wrote:<br> <blockquote type="cite" cite="mid...@s-..."> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 5.5.2654.45"> <title>RE: [ebxmlms-develop] Initialisation + customisation</title> <p><font size="2">No. When I'm sending a signed message, I want to determine whether the <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo"><ds:KeyInfo></a> section is included in the message or not.</font></p> <p><font size="2">Given that Hermes currently has no database of CPA parameters (which is a discussion for another day), it might make sense to provide a parameter to Request.setSign() (and therefore to EbXmlMessage.sign(), and therefore to Signature.sign(), and therefore to PKISignatureImpl.sign(), and therefore (finally) to ApacheXMLDSigner.sign()) to specify whether the <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo"><ds:KeyInfo></a> section is added or not. Hmm, that's a long chain of changes...</font></p> <p><font size="2">For now, I've just commented out the section of code in ApacheXMLDSigner that does the "signature.addKeyInfo((X509Certificate) certificates[i]);", but that only works while we have a single trading partner.</font></p> <p><font size="2">Incidentally, the trading partner's MSH is TIBCO BusinessConnect, which seems to have some interesting assumptions of it's own. For instance, where Hermes (pre-PublicKeyFinder) requires that the <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo"><ds:KeyInfo></a> section is present, BusinessConnect requires that it *isn't* present. Hence, this new requirement for Hermes.</font></p> <p><font size="2">PJDM</font> <br> <font size="2">--</font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777 </font> <br> <font size="2">-----Original Message-----</font> <br> <font size="2">From: Patrick Yee [<a href="mailto:kc...@ce...">mailto:kc...@ce...</a>]</font> <br> <font size="2">Sent: Tuesday, 13 May 2003 1:34 AM</font> <br> <font size="2">To: <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a></font> <br> <font size="2">Subject: Re: [ebxmlms-develop] Initialisation + customisation</font> </p> <br> <p><font size="2">Sorry, I am not sure about what you want it to be. Do you mean you want to make the verification of digital signature optional, on a per-CPA basis?</font></p> <p><font size="2">Regards, -Patrick</font> <br> <font size="2">Our trading partner can't accept messages with <a class="moz-txt-link-rfc2396E" href="ds:KeyInfo"><ds:KeyInfo></a> in them. It's easy enough to comment out this bit of code, but it would be nice to do it on a per-CPA basis. However, I'm not sure what the best way of specifying this would be. Any suggestions?</font></p> <font size="3" color="BLUE"> <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> </body> </html> |
|
From: Patrick Y. <kc...@ce...> - 2003-05-13 01:21:46
|
<!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> For this, we had a debate internally before. We concluded that the nature of message signing and acknowledgement signing are different. Message signing is used to testify the message (and the most important, the payloads) is sent by the real sender. Acknowledgement signing is used to testify the message has been safely arrived at the real destination (i.e. the real MSH). Following this model, we can accept all applications to "share" the private key for signing acknowledgement messages. While at the same time, we think the non-repudiation property of message signing drives us to think carefully about holding all keys in a central point. Basically our concept is following the ASP model. As a result, as you can see in the current design, we perform the signing in Request object, i.e. in the client side.<br> <br> Regards, -Patrick<br> <br> <br> Mayne, Peter wrote:<br> <blockquote type="cite" cite="mid...@s-..."> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 5.5.2654.45"> <title>RE: [ebxmlms-develop] Using alternative signing key algorithms</title> <p><font size="2">>> I agree that there should also be a way of having the MSH sign the outgoing message, so there wouldn't</font> <br> <font size="2">>> need to be more than one copy of the private key lying around.</font> <br> <font size="2">></font> <br> <font size="2">> Yes and no. It may be more handy. But I'm just feeling a bit unsecured to have MSH to hold the private</font> <br> <font size="2">> key for the application. What do you think?</font> </p> <p><font size="2">But Hermes already has the private key for message signing (MSH/DigitalSignature/AckSign/KeyStore) so it can sign acknowledgements. I don't see any way around that.</font></p> <p><font size="2">Given that the MSH must have a copy of the private key (like it or not), it makes sense under some circumstances to have that be the only copy of the private key.</font></p> <p><font size="2">As usual, there's more than one configuration to think about.</font> </p> <p><font size="2">1) One single key at the MSH to do all outgoing message signing (including originals and acknowledgements). This makes sense for a single business sending messages to trading partners.</font></p> <p><font size="2">2) All messages signed by the message clients. This makes sense for Gait's suggestion of running the MSH in ASP mode for different clients. The trouble with this is that message acknowledgements are still signed by the MSH, rather than a client's key, so running Hermes in ASP mode won't currently work.</font></p> <p><font size="2">PJDM</font> <br> <font size="2">--</font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p> <font size="3" color="BLUE"> <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> </body> </html> |
|
From: Patrick Y. <kc...@ce...> - 2003-05-12 16:03:50
|
MessageMy comment in blue. -Patrick
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Monday, May 12, 2003 02:29 PM
Subject: RE: [ebxmlms-develop] Using alternative signing key =
algorithms
> The setSign method to sign the EbxmlMessage through Request, though =
you could do it manually on the
> EbxmlMessage as well.
I think I recall someone saying that Request.setSign() is the =
preferred method, because it ensures that the message is signed after =
everything is added.
That's me. Yes, Request.setSign() is preferred as it makes sure that =
signing is the last step after all changes to the message have been =
made.
I agree that there should also be a way of having the MSH sign the =
outgoing message, so there wouldn't need to be more than one copy of the =
private key lying around.
Yes and no. It may be more handy. But I'm just feeling a bit unsecured =
to have MSH to hold the private key for the application. What do you =
think?
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: Gait Boxman [mailto:gai...@ti...]=20
Sent: Monday, 12 May 2003 4:26 PM
To: ebx...@li...
Subject: Re: [ebxmlms-develop] Using alternative signing key =
algorithms
Was writing a completely different message, and discovered things =
are a bit different than I thought originally. The setSign method to =
sign the EbxmlMessage through Request, though you could do it manually =
on the EbxmlMessage as well. The KeyAlg algorithm for acknowledgments =
was added per my request a couple of weeks ago, I never bother with =
signing messages at that point. From the looks of it, your proposed =
change is right on the spot.
I guess it's ok that the signature params can be set by the client. =
That way we can use the MSH in ASP mode so that it can be used with =
different sigs for different companies sharing the MSH (for instance)
--Gait.
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Monday, May 12, 2003 1:09 AM
Subject: RE: [ebxmlms-develop] Using alternative signing key =
algorithms
I agree with you, but how do I do it? Where do I tell Hermes to =
sign the message at the MSH on the way out, rather than having it signed =
by the client?
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: Gait Boxman [mailto:gai...@ti...]=20
Sent: Friday, 9 May 2003 8:07 PM
To: ebx...@li...
Subject: Re: [ebxmlms-develop] Using alternative signing key =
algorithms
Hi Peter,
why would you want the clients to sign messages? The purpose of =
the sig as I read it from the spec is non-repudiation of origin *from =
the MSH*, not from the client. While I can see a point in having the =
client (or effectively the business app/user) sign the message as well, =
this does not replace the MSH signature. I wouldn't place such support =
on the Request, but rather on the ebXMLMessage (probably already is =
there, maybe not public).
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Friday, May 09, 2003 3:15 AM
Subject: [ebxmlms-develop] Using alternative signing key =
algorithms
If I'm using an RSA key, there's no way to tell =
Request.setSign() to use a different algorithm from the default when =
creating a message. (The msh.properties.xml file has =
"MSH/DigitalSignature/AckSign/KeyStore/Algorithm" so Hermes can sign =
messages, but it appears to have been overlooked so Hermes clients can =
sign messages.)
I fixed this by adding another definition of Request.setSign:=20
-- BEGIN --=20
/**=20
* Set keystore properties.=20
*=20
* @param alias Alias of the keystore.=20
* @param password Keystore password.=20
* @param keyStoreFile Keystore file.=20
* @param keyAlgorithm Key algorithm.=20
*/=20
public void setSign(String alias, char[] password, String =
keyStoreFile, String keyAlgorithm) {=20
this.alias =3D alias;=20
this.password =3D password;=20
this.keyStoreFile =3D keyStoreFile;=20
this.keyAlgorithm =3D keyAlgorithm;=20
}=20
-- END --=20
(This obviously requires a private String keyAlgorithm to be =
defined in Request.)=20
In the two places in Request where the signing actually =
happens, replace the existing code with:=20
-- BEGIN --=20
if (alias !=3D null && password !=3D null && =
keyStoreFile !=3D null) {=20
try{=20
if(keyAlgorithm=3D=3Dnull)=20
{=20
ebxmlMessage.sign(alias, password, =
keyStoreFile);=20
}=20
else=20
{=20
ebxmlMessage.sign(alias, password, =
keyStoreFile, keyAlgorithm);=20
}=20
}=20
catch (Exception e) {=20
throw new RequestException(e.getMessage());=20
}=20
}=20
-- END --=20
Can you please add this (or similar) to the nightly build.=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.
|
|
From: Patrick Y. <kc...@ce...> - 2003-05-12 16:00:12
|
Using alternative signing key algorithmsThanks for the patch. Again, we =
have added the code fragment into the latest source tree.
Regards, -Patrick
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Friday, May 09, 2003 09:15 AM
Subject: [ebxmlms-develop] Using alternative signing key algorithms
If I'm using an RSA key, there's no way to tell Request.setSign() to =
use a different algorithm from the default when creating a message. (The =
msh.properties.xml file has =
"MSH/DigitalSignature/AckSign/KeyStore/Algorithm" so Hermes can sign =
messages, but it appears to have been overlooked so Hermes clients can =
sign messages.)
I fixed this by adding another definition of Request.setSign:=20
-- BEGIN --=20
/**=20
* Set keystore properties.=20
*=20
* @param alias Alias of the keystore.=20
* @param password Keystore password.=20
* @param keyStoreFile Keystore file.=20
* @param keyAlgorithm Key algorithm.=20
*/=20
public void setSign(String alias, char[] password, String =
keyStoreFile, String keyAlgorithm) {=20
this.alias =3D alias;=20
this.password =3D password;=20
this.keyStoreFile =3D keyStoreFile;=20
this.keyAlgorithm =3D keyAlgorithm;=20
}=20
-- END --=20
(This obviously requires a private String keyAlgorithm to be defined =
in Request.)=20
In the two places in Request where the signing actually happens, =
replace the existing code with:=20
-- BEGIN --=20
if (alias !=3D null && password !=3D null && keyStoreFile !=3D =
null) {=20
try{=20
if(keyAlgorithm=3D=3Dnull)=20
{=20
ebxmlMessage.sign(alias, password, keyStoreFile);=20
}=20
else=20
{=20
ebxmlMessage.sign(alias, password, keyStoreFile, =
keyAlgorithm);=20
}=20
}=20
catch (Exception e) {=20
throw new RequestException(e.getMessage());=20
}=20
}=20
-- END --=20
Can you please add this (or similar) to the nightly build.=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.
|
|
From: Patrick Y. <kc...@ce...> - 2003-05-12 15:47:27
|
Added initialisation codeThanks for the patch. We have added the code =
fragment into the latest source tree.
Regards, -Patrick
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Thursday, May 08, 2003 09:41 AM
Subject: [ebxmlms-develop] Added initialisation code
I've added the following code to my copy of the MessageServiceHandler =
constructor. It allows for a class with a public static =
configure(Property) method to be specified in msh.properties.xml. The =
configure(Property) method of this class is called after the =
MessageServiceHandler constructor has configured various other classes.
(With this in place, I am able to use my local code to install my own =
TrustManager.)=20
Can you please add this (or something similar) to the nightly build.=20
Thanks.=20
public MessageServiceHandler() throws =
MessageServiceHandlerException {=20
super();=20
Property prop =3D null;=20
try {=20
try {=20
prop =3D =
Property.load(Constants.MSH_SERVER_PROPERTY_FILE);=20
:=20
:=20
:=20
}=20
catch (InitializationException e) {=20
throw new MessageServiceHandlerException(e.getMessage());=20
}=20
// Call a specified class to do local configuration.=20
// The MSH/Config/Local property from the properties file is =
the=20
// name of a class with a static configure(Property) method.=20
// (We can't use an interface here because interfaces can't =
have static methods,=20
// so we have to use reflection.)=20
//=20
final String className =3D prop.get("MSH/Config/Local");=20
if(className!=3Dnull)=20
{=20
logger.debug("Calling " + className + =
".configure(Property)");=20
try=20
{=20
Class c =3D Class.forName(className);=20
java.lang.reflect.Method m =3D =
c.getMethod("configure", new Class[]{Property.class});=20
m.invoke(null, new Object[]{prop});=20
}=20
catch(Throwable t)=20
{=20
logger.error("Couldn't call " + className + =
".configure(Property)", t);=20
throw new =
MessageServiceHandlerException(t.getMessage());=20
}=20
}=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.
|
|
From: Patrick Y. <kc...@ce...> - 2003-05-12 15:32:28
|
Initialisation + customisationSorry, I am not sure about what you want = it to be. Do you mean you want to make the verification of digital = signature optional, on a per-CPA basis? Regards, -Patrick Our trading partner can't accept messages with <ds:KeyInfo> in them. = It's easy enough to comment out this bit of code, but it would be nice = to do it on a per-CPA basis. However, I'm not sure what the best way of = specifying this would be. Any suggestions? |
|
From: Gait B. <gai...@ti...> - 2003-05-12 06:22:57
|
MessageWas writing a completely different message, and discovered things =
are a bit different than I thought originally. The setSign method to =
sign the EbxmlMessage through Request, though you could do it manually =
on the EbxmlMessage as well. The KeyAlg algorithm for acknowledgments =
was added per my request a couple of weeks ago, I never bother with =
signing messages at that point. From the looks of it, your proposed =
change is right on the spot.
I guess it's ok that the signature params can be set by the client. That =
way we can use the MSH in ASP mode so that it can be used with different =
sigs for different companies sharing the MSH (for instance)
--Gait.
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Monday, May 12, 2003 1:09 AM
Subject: RE: [ebxmlms-develop] Using alternative signing key =
algorithms
I agree with you, but how do I do it? Where do I tell Hermes to sign =
the message at the MSH on the way out, rather than having it signed by =
the client?
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: Gait Boxman [mailto:gai...@ti...]=20
Sent: Friday, 9 May 2003 8:07 PM
To: ebx...@li...
Subject: Re: [ebxmlms-develop] Using alternative signing key =
algorithms
Hi Peter,
why would you want the clients to sign messages? The purpose of the =
sig as I read it from the spec is non-repudiation of origin *from the =
MSH*, not from the client. While I can see a point in having the client =
(or effectively the business app/user) sign the message as well, this =
does not replace the MSH signature. I wouldn't place such support on the =
Request, but rather on the ebXMLMessage (probably already is there, =
maybe not public).
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Friday, May 09, 2003 3:15 AM
Subject: [ebxmlms-develop] Using alternative signing key =
algorithms
If I'm using an RSA key, there's no way to tell Request.setSign() =
to use a different algorithm from the default when creating a message. =
(The msh.properties.xml file has =
"MSH/DigitalSignature/AckSign/KeyStore/Algorithm" so Hermes can sign =
messages, but it appears to have been overlooked so Hermes clients can =
sign messages.)
I fixed this by adding another definition of Request.setSign:=20
-- BEGIN --=20
/**=20
* Set keystore properties.=20
*=20
* @param alias Alias of the keystore.=20
* @param password Keystore password.=20
* @param keyStoreFile Keystore file.=20
* @param keyAlgorithm Key algorithm.=20
*/=20
public void setSign(String alias, char[] password, String =
keyStoreFile, String keyAlgorithm) {=20
this.alias =3D alias;=20
this.password =3D password;=20
this.keyStoreFile =3D keyStoreFile;=20
this.keyAlgorithm =3D keyAlgorithm;=20
}=20
-- END --=20
(This obviously requires a private String keyAlgorithm to be =
defined in Request.)=20
In the two places in Request where the signing actually happens, =
replace the existing code with:=20
-- BEGIN --=20
if (alias !=3D null && password !=3D null && keyStoreFile =
!=3D null) {=20
try{=20
if(keyAlgorithm=3D=3Dnull)=20
{=20
ebxmlMessage.sign(alias, password, =
keyStoreFile);=20
}=20
else=20
{=20
ebxmlMessage.sign(alias, password, =
keyStoreFile, keyAlgorithm);=20
}=20
}=20
catch (Exception e) {=20
throw new RequestException(e.getMessage());=20
}=20
}=20
-- END --=20
Can you please add this (or similar) to the nightly build.=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.
|
|
From: Gait B. <gai...@ti...> - 2003-05-09 10:03:23
|
Using alternative signing key algorithmsHi Peter,
why would you want the clients to sign messages? The purpose of the sig =
as I read it from the spec is non-repudiation of origin *from the MSH*, =
not from the client. While I can see a point in having the client (or =
effectively the business app/user) sign the message as well, this does =
not replace the MSH signature. I wouldn't place such support on the =
Request, but rather on the ebXMLMessage (probably already is there, =
maybe not public).
----- Original Message -----=20
From: Mayne, Peter=20
To: 'ebx...@li...'=20
Sent: Friday, May 09, 2003 3:15 AM
Subject: [ebxmlms-develop] Using alternative signing key algorithms
If I'm using an RSA key, there's no way to tell Request.setSign() to =
use a different algorithm from the default when creating a message. (The =
msh.properties.xml file has =
"MSH/DigitalSignature/AckSign/KeyStore/Algorithm" so Hermes can sign =
messages, but it appears to have been overlooked so Hermes clients can =
sign messages.)
I fixed this by adding another definition of Request.setSign:=20
-- BEGIN --=20
/**=20
* Set keystore properties.=20
*=20
* @param alias Alias of the keystore.=20
* @param password Keystore password.=20
* @param keyStoreFile Keystore file.=20
* @param keyAlgorithm Key algorithm.=20
*/=20
public void setSign(String alias, char[] password, String =
keyStoreFile, String keyAlgorithm) {=20
this.alias =3D alias;=20
this.password =3D password;=20
this.keyStoreFile =3D keyStoreFile;=20
this.keyAlgorithm =3D keyAlgorithm;=20
}=20
-- END --=20
(This obviously requires a private String keyAlgorithm to be defined =
in Request.)=20
In the two places in Request where the signing actually happens, =
replace the existing code with:=20
-- BEGIN --=20
if (alias !=3D null && password !=3D null && keyStoreFile !=3D =
null) {=20
try{=20
if(keyAlgorithm=3D=3Dnull)=20
{=20
ebxmlMessage.sign(alias, password, keyStoreFile);=20
}=20
else=20
{=20
ebxmlMessage.sign(alias, password, keyStoreFile, =
keyAlgorithm);=20
}=20
}=20
catch (Exception e) {=20
throw new RequestException(e.getMessage());=20
}=20
}=20
-- END --=20
Can you please add this (or similar) to the nightly build.=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.
|
|
From: Ng C. Y. [Cyng] <cy...@cs...> - 2003-05-08 10:07:41
|
Hi Gait,
> I would still strongly propose to pass the message to xmlsec as a string,
> simply to avoid issues with JAXM and dom4j. In fact, for received messages I
> believe it's the only way. both JAXM and Axis do 'something' that renders
> the received message different from the one passed to xmlsec. For
> verification, you must pass in the received data as is to have any chance of
> succesful verification. It's not a big deal to plug in a call to
> getContent() and rewrapping xml sec to support string based verification,
> and will solve at least that part of the problem.
> But even for outgoing messages, I'd still propose to first render the
> message and then pass it on to xmlsec for signing. If not, you need to be
> sure that whatever is passed to xmlsec is identical to what's sent out on
> the wire, otherwise the hash will mismatch and verification is bound to fail
> again.
I ever think of this solution before and would take this as the
"last" resort. Again, ideally speaking, if JAXM, Axis or xmlsec does not
have those "nice" features in rendering XML representation, using JAXP
transformer (from SOAP to DOM) would be really a simple and natural one.
Now, if we switch to string, which is supposed to be a byte-by-byte faithful
representation, we have to do more tasks as follows.
In verification, instead of manipulating the SOAP object (which is
a parsed representation of a message), the received message stream from HTTP
or persisted file stream has to be extracted (for SOAPPart bytes and
payload bytes) and fed into xmlsec.
In signing, one is not going to sign the SOAP object but has to
sign what is anticipated to be serialized in the network stream.
I ever did an experiment several days ago on the sample file and
X509 certificate that Peter Mayne sent us before. The sample file is
supposed to be generated by other XML security implementation. I copy
and modify the VerifySignature.java example bundled with xmlsec to verify
this sample file. The result is that the digest for URI="" and URI for
payload are successfully verified but the signature value fails!!!
Sigh... I wonder which XML security implementation can be used
as a reference and I don't know if xmlsec is doing the right thing.
So, the conclusion is that we may go for String feeding into
xmlsec to remove the "uncertainty" of JAXM or Axis. But it is not guaranteed
whether the result really works and is interoperable with other
implementations.
> just my EUR 0.02.
Ha.... EUR 0.02 ~= HK 0.176, your suggestion is far more than
2 cents. :-)
Regards,
CY
----------------------------------------------------------------------------
Ng Chi Yuen, CY. cy...@ce... http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
----------------------------------------------------------------------------
|
|
From: Jason v. Z. <ja...@ze...> - 2003-05-07 08:07:04
|
On Wed, 2003-05-07 at 02:53, Gait Boxman wrote:
> Hi Jason,
>
> this is the message I used to get from SAAJ on HTTP responses before I
> plugged an extra try catch block. Reason for the error: SAAJ was built for
> synchronous HTTP messaging and expects a SOAP message (with content type
> text/xml) coming back on the HTTP Response when sending something out. But
> since ebXML defaults to async messaging, you can not rely on a SOAP message
> coming back on any but the 500 response. In fact, any 2xx response must be
> accepted as a successful send (unless you force sync acks). To fix it, you
> actually need to patch SAAJ, see the copy of that message below.
>
> Kind Regards, Gait.
Much appreciated.
Though is this necessary between two instances of Hermes? I am simply
trying to send messages between Hermes instances on the same machine.
I've built my little system and prototyped it with the xmlrpc and now
that I have switched over I wish that SOAP was never invented :-)
At any rate, I don't have any choice. Everything in the system is
working now except this so I'll be here until I resolve it.
Peter is helping me out a great deal and I intend not to just whine.
I'll write some docs when I'm done. I know all too well how OSS projects
work where docs are sorely lacking and the docs are confusing. There is
no test suite checked in and the loopback example doesn't really serve
as a 'real world' example.
I'm sure it's very likely that I have a misconfiguration that's crept
in, but I have no idea given the overall exception handler. Most likely
SAAJ is the culprit.
> -- my original posted fix -------
> Hi,
>
> I've observed the same problem while doing some tests against other
> receivers. In my case, the other party was responding with a 200 OK message,
> and a nice HTML document telling me my message was well received. Very
> friendly, but not what the Sun JAXM implementation was expecting. According
> to the specs, the response is valid unless you're running synchronous
> communications. In fact, any 2XX response is fine when using async
> responses. So I ended up patching JAXM to catch the error on the response
> message.
> Get JAXM 1.1 from SUN, and change line 333 of
> jaxm1.1-scsl\jaxm-ri\src\com\sun\xml\messaging\saaj\client\p2p\HttpSoapConne
> ction.java to look like:
>
> try {
> response = messageFactory.createMessage(headers, in);
> } catch (SOAPException ex) {
> if( responseCode== HttpURLConnection.HTTP_INTERNAL_ERROR ) {
> throw ex;
> }
> response = null;
> }
>
> then rebuild jaxm, and copy the patched saaj-ri.jar into your ebxmlms. That
> should do the trick.
> Of course, this will also catch the error while doing synchronous
> communications, which is probably not what we want.
> As an aside, be aware that the createMessage call will print a stack trace
> before the error is caught, so don't worry if you still get the error trace
> in the tomcat console.
>
> --Gait.
>
> ----------
>
> ----- Original Message -----
> From: "Jason van Zyl" <ja...@ze...>
> To: <ebx...@li...>
> Sent: Tuesday, May 06, 2003 7:26 PM
> Subject: [ebxmlms-develop] SOAPException: unable to internalize message
> (invalid content type: text/html)
>
>
> > Hi,
> >
> > I see some mention of this being fixed and I tried the latest nightly
> > download and I'm getting the error. CVS has been dead all day from where
> > I am. Has this issue been resolved?
> >
> > Maybe it is something I have to look for in my setup, I'm using Jetty
> > not Tomcat.
> >
> > --
> > jvz.
> >
> > > Jason van Zyl
> > > ja...@ze...
> > > http://tambora.zenplex.org
> > >
> > > In short, man creates for himself a new religion of a rational
> > > and technical order to justify his work and to be justified in it.
> > >
> > > -- Jacques Ellul, The Technological Society
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> > > The only event dedicated to issues related to Linux enterprise solutions
> > > www.enterpriselinuxforum.com
> > >
> > > _______________________________________________
> > > ebxmlms-develop mailing list
> > > ebx...@li...
> > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> >
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
--
jvz.
Jason van Zyl
ja...@ze...
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
|
1574 messages has been excluded from this view by a project administrator.
