ebxmlms-develop — Development discussions

Re: [ebxmlms-develop] Re: Hermes interoperate with jwsdp 1.0.1

[Bob K. <py...@ce...>]

Sorry that there is typo-error. Please look at the inline message..

Regards,
Bob Koon

Bob Koon wrote:

>
> To send a ebxml message to another MSH using Hermes, the model should 
> be something like this:
>
> Client (runMonitor.bat) -- > Hermes MSH --> your MSH.
>
> Therefore the msh_client.properties.xml should be pointed to a Hermes 
> MSH, and Hermes MSH will help you to send the message to your in-house 
> MSH. The problem you encounter may be due to the case like:
>
> Client (runMonitor.bat) --> your MSH
>
> Please note that runMonitor.bat will only run a client to connect to 
> Hermes MSH,, and it will be startup the Hermes MSH itself.

I mean that runMonitor.bat "will not" startup the Hermes MSH itself.

>
> Regards,
> Bob Koon
>
> Rao Yerubandi wrote:
>
>> CY
>>
>>  
>>
>> Thanks for your reply
>>
>> i am trying to use runmonitor.bat to send a PO to our in-house 
>> implementation . it is using the msh_client.properties.xml  and it is 
>> pointing  to my local MSH.
>>
>> but from the hermes code i found out that prior to sending a ebxml 
>> message across , it is forming a command object with 
>> messageservicehandlerconfig information and trying to post it to our 
>> in-house implementation. but on ( our end ) jwsdp end it is failing 
>> with a Invalid content-type error.
>>
>>  
>>
>> From the code of Request.java i find that it is calling register() -> 
>> . I want to know if this
>>
>> sending of MSH ConfigInfo to other MSH is a mandatory step.
>>
>>  
>>
>> Just to be sure i will runMonitor.bat again and post a reply back to 
>> the list.
>>
>> -Venkat
>>
>>
>>
>> ebx...@li... wrote:
>>
>>     ,
>>
>>     > javax.xml.soap.SOAPException: Invalid
>>     Content-Type:application/octet-stream at
>>     > Cannot create request objects.
>>     > hk.hku.cecid.phoenix.message.handler.RequestException:
>>     > Failed to send query to MSH.
>>     > HTTP response code = 500
>>     > HTTP response message = Internal Server Error
>>     > at
>>     hk.hku.cecid.phoenix.message.handler.Request.expectMapResponse(Unknow
>>     > n Source)
>>     > javax.xml.soap.SOAPException: Invalid
>>     Content-Type:application/octet-stream
>>     >
>>     > so i was wondering if i need to change anything MIME related to
>>     make Hermes interoperate with jwsdp 1.0.1. i am not using SMTP .
>>
>>     application/octet-stream is the private Command object we define.
>>     Do you set up Hermes in this way: you create Request and
>>     msh_client.properties.xml properly points to your *local Hermes MSH*.
>>     Request serializes a Command obj! ect to local Hermes and it does
>>     the job
>>     on behalf of Request.
>>
>>     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
>>     ----------------------------------------------------------------------------
>>
>>
>>
>>
>>     --__--__--
>>
>>     _______________________________________________
>>     ebxmlms-develop mailing list
>>     ebx...@li...
>>     https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>>
>>
>>     End of ebxmlms-develop Digest
>>
>> ------------------------------------------------------------------------
>> Do you Yahoo!?
>> Yahoo! SiteBuilder 
>> <http://us.rd.yahoo.com/evt=10469/*http://sitebuilder.yahoo.com> - 
>> Free, easy-to-use web site design software 
>
>

Re: [ebxmlms-develop] Re: Hermes interoperate with jwsdp 1.0.1

[Bob K. <py...@ce...>]

To send a ebxml message to another MSH using Hermes, the model should be 
something like this:

Client (runMonitor.bat) -- > Hermes MSH --> your MSH.

Therefore the msh_client.properties.xml should be pointed to a Hermes 
MSH, and Hermes MSH will help you to send the message to your in-house 
MSH. The problem you encounter may be due to the case like:

Client (runMonitor.bat) --> your MSH

Please note that runMonitor.bat will only run a client to connect to 
Hermes MSH,, and it will be startup the Hermes MSH itself.

Regards,
Bob Koon

Rao Yerubandi wrote:

> CY
>
>  
>
> Thanks for your reply
>
> i am trying to use runmonitor.bat to send a PO to our in-house 
> implementation . it is using the msh_client.properties.xml  and it is 
> pointing  to my local MSH.
>
> but from the hermes code i found out that prior to sending a ebxml 
> message across , it is forming a command object with 
> messageservicehandlerconfig information and trying to post it to our 
> in-house implementation. but on ( our end ) jwsdp end it is failing 
> with a Invalid content-type error.
>
>  
>
> From the code of Request.java i find that it is calling register() -> 
> . I want to know if this
>
> sending of MSH ConfigInfo to other MSH is a mandatory step.
>
>  
>
> Just to be sure i will runMonitor.bat again and post a reply back to 
> the list.
>
> -Venkat
>
>
>
> ebx...@li... wrote:
>
>     ,
>
>     > javax.xml.soap.SOAPException: Invalid
>     Content-Type:application/octet-stream at
>     > Cannot create request objects.
>     > hk.hku.cecid.phoenix.message.handler.RequestException:
>     > Failed to send query to MSH.
>     > HTTP response code = 500
>     > HTTP response message = Internal Server Error
>     > at
>     hk.hku.cecid.phoenix.message.handler.Request.expectMapResponse(Unknow
>     > n Source)
>     > javax.xml.soap.SOAPException: Invalid
>     Content-Type:application/octet-stream
>     >
>     > so i was wondering if i need to change anything MIME related to
>     make Hermes interoperate with jwsdp 1.0.1. i am not using SMTP .
>
>     application/octet-stream is the private Command object we define.
>     Do you set up Hermes in this way: you create Request and
>     msh_client.properties.xml properly points to your *local Hermes MSH*.
>     Request serializes a Command obj! ect to local Hermes and it does
>     the job
>     on behalf of Request.
>
>     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
>     ----------------------------------------------------------------------------
>
>
>
>
>     --__--__--
>
>     _______________________________________________
>     ebxmlms-develop mailing list
>     ebx...@li...
>     https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>
>
>     End of ebxmlms-develop Digest
>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Yahoo! SiteBuilder 
> <http://us.rd.yahoo.com/evt=10469/*http://sitebuilder.yahoo.com> - 
> Free, easy-to-use web site design software 

[ebxmlms-develop] Re: Hermes interoperate with jwsdp 1.0.1

[Rao Y. <ra...@ya...>]

CY 
 
Thanks for your reply
i am trying to use runmonitor.bat to send a PO to our in-house implementation . it is using the msh_client.properties.xml  and it is pointing  to my local MSH.
but from the hermes code i found out that prior to sending a ebxml message across , it is forming a command object with messageservicehandlerconfig information and trying to post it to our in-house implementation. but on ( our end ) jwsdp end it is failing with a Invalid content-type error. 
 
From the code of Request.java  i find that it is calling register() -> . I want to know if this 
sending of MSH ConfigInfo to other MSH  is a mandatory step.
 
Just to be sure i will runMonitor.bat again and post a reply back to the list.
-Venkat


ebx...@li... wrote:
,

> javax.xml.soap.SOAPException: Invalid Content-Type:application/octet-stream at
> Cannot create request objects.
> hk.hku.cecid.phoenix.message.handler.RequestException:
> Failed to send query to MSH.
> HTTP response code = 500
> HTTP response message = Internal Server Error
> at hk.hku.cecid.phoenix.message.handler.Request.expectMapResponse(Unknow
> n Source)
> javax.xml.soap.SOAPException: Invalid Content-Type:application/octet-stream
>
> so i was wondering if i need to change anything MIME related to make Hermes interoperate with jwsdp 1.0.1. i am not using SMTP .

application/octet-stream is the private Command object we define.
Do you set up Hermes in this way: you create Request and
msh_client.properties.xml properly points to your *local Hermes MSH*.
Request serializes a Command object to local Hermes and it does the job
on behalf of Request.

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
----------------------------------------------------------------------------




--__--__--

_______________________________________________
ebxmlms-develop mailing list
ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop


End of ebxmlms-develop Digest

---------------------------------
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

Re: [ebxmlms-develop] Interop between Hermes and JWDSP 1.0.1 || Is it possible to change MIME types of an outgoing message

[Ng C. Y. [Cyng] <cy...@cs...>]

Hi,

> javax.xml.soap.SOAPException: Invalid Content-Type:application/octet-stream        at
> Cannot create request objects.
> hk.hku.cecid.phoenix.message.handler.RequestException:
>  Failed to send query to MSH.
>   HTTP response code = 500
>   HTTP response message = Internal Server Error
>         at hk.hku.cecid.phoenix.message.handler.Request.expectMapResponse(Unknow
> n Source)
> javax.xml.soap.SOAPException: Invalid Content-Type:application/octet-stream
>
> so i was wondering if i need to change anything MIME related to make Hermes interoperate with jwsdp 1.0.1. i am not using SMTP .

        application/octet-stream is the private Command object we define.
Do you set up Hermes in this way: you create Request and
msh_client.properties.xml properly points to your *local Hermes MSH*.
Request serializes a Command object to local Hermes and it does the job
on behalf of Request.

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
----------------------------------------------------------------------------

[ebxmlms-develop] Fwd: Interop between Hermes and JWDSP 1.0.1 || Is it possible to change MIME types of an outgoing message

[Rao Y. <ra...@ya...>]

i am trying to do a interop between our in-house implementation and Hermes.
we are using jwsdp1.0.1 . when i try to send a document from Hermes to our in-house implementation 
 
jaxm throws the following exception 
 
javax.xml.soap.SOAPException: Invalid Content-Type:application/octet-stream        at
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159)        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)         at
com.sun.xml.messaging.jaxm.util.ProfileMessage.<init>(ProfileMessage.java:38)     at
com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageImpl.<init>
EbXMLMessageImpl.java:119)        at
com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageFactoryImpl.createMessage(EbXMLMessageFactoryImpl.java:57)
        
on hermes  i see the following error message ( btw i am running runmonitor.bat )
 
Cannot create request objects.
hk.hku.cecid.phoenix.message.handler.RequestException:
 Failed to send query to MSH.
  HTTP response code = 500
  HTTP response message = Internal Server Error
        at hk.hku.cecid.phoenix.message.handler.Request.expectMapResponse(Unknow
n Source)
        at hk.hku.cecid.phoenix.message.handler.Request.sendMessageServiceHandle
rConfig(Unknown Source)
        at hk.hku.cecid.phoenix.message.handler.Request.register(Unknown Source)
        at hk.hku.cecid.phoenix.message.handler.Request.<init>(Unknown Source)
        at hk.hku.cecid.phoenix.message.handler.Request.<init>(Unknown Source)
        at hk.hku.cecid.phoenix.message.monitor.Monitor.setConfigParamenters(Unk
nown Source)
        at hk.hku.cecid.phoenix.message.monitor.Monitor.main(Unknown Source)

i checked the SAAJ source code for MessageImpl.java. 

-----------------------------------------------------------------------

Source of verify() in MessageImpl.java

----------------------------------------------------------------

String primary = contentType.getPrimaryType();

String sub = contentType.getSubType();



if (!primary.equalsIgnoreCase("multipart")) 

{

   if (primary.equalsIgnoreCase("text") && sub.equalsIgnoreCase("xml"))

      return 1;

else

     throw new SOAPException("Invalid Content-Type:"+primary+"/"+sub);

} 

else if (sub.equalsIgnoreCase("related")) 

{

   String type = contentType.getParameter("type").toLowerCase();

   if (type.startsWith("text/xml"))

      return 2;

   else

      throw new SOAPException("Content-Type needs to be Multipart/Related "+

"and with \"type=text/xml\"");

}

else 

    throw new SOAPException("Invalid Content-Type: "+primary+"/"+sub);

 
After going thru the checks it is throwing a SOAPException with the following message
 
 
javax.xml.soap.SOAPException: Invalid Content-Type:application/octet-stream        
 
so i was wondering if i need to change anything MIME related to make Hermes interoperate with jwsdp 1.0.1. i am not using SMTP .
-Venkat





---------------------------------
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

[ebxmlms-develop] Interop between Hermes and JWDSP 1.0.1 || Is it possible to change MIME types of an outgoing message

[Rao Y. <ra...@ya...>]

i am trying to do a interop between our in-house implementation and Hermes.
we are using jwsdp1.0.1 . when i try to send a document from Hermes to our in-house implementation 
 
jaxm throws the following exception 
 
javax.xml.soap.SOAPException: Invalid Content-Type:application/octet-stream        at
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159)        at
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)         at
com.sun.xml.messaging.jaxm.util.ProfileMessage.<init>(ProfileMessage.java:38)     at
com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageImpl.<init>
EbXMLMessageImpl.java:119)        at
com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageFactoryImpl.createMessage(EbXMLMessageFactoryImpl.java:57)
        
on hermes  i see the following error message ( btw i am running runmonitor.bat )
 
Cannot create request objects.
hk.hku.cecid.phoenix.message.handler.RequestException:
 Failed to send query to MSH.
  HTTP response code = 500
  HTTP response message = Internal Server Error
        at hk.hku.cecid.phoenix.message.handler.Request.expectMapResponse(Unknow
n Source)
        at hk.hku.cecid.phoenix.message.handler.Request.sendMessageServiceHandle
rConfig(Unknown Source)
        at hk.hku.cecid.phoenix.message.handler.Request.register(Unknown Source)
        at hk.hku.cecid.phoenix.message.handler.Request.<init>(Unknown Source)
        at hk.hku.cecid.phoenix.message.handler.Request.<init>(Unknown Source)
        at hk.hku.cecid.phoenix.message.monitor.Monitor.setConfigParamenters(Unk
nown Source)
        at hk.hku.cecid.phoenix.message.monitor.Monitor.main(Unknown Source)

i checked the SAAJ source code for MessageImpl.java. 

-----------------------------------------------------------------------

Source of verify() in MessageImpl.java

----------------------------------------------------------------

String primary = contentType.getPrimaryType();

String sub = contentType.getSubType();



if (!primary.equalsIgnoreCase("multipart")) 

{

   if (primary.equalsIgnoreCase("text") && sub.equalsIgnoreCase("xml"))

      return 1;

else

     throw new SOAPException("Invalid Content-Type:"+primary+"/"+sub);

} 

else if (sub.equalsIgnoreCase("related")) 

{

   String type = contentType.getParameter("type").toLowerCase();

   if (type.startsWith("text/xml"))

      return 2;

   else

      throw new SOAPException("Content-Type needs to be Multipart/Related "+

"and with \"type=text/xml\"");

}

else 

    throw new SOAPException("Invalid Content-Type: "+primary+"/"+sub);

 
After going thru the checks it is throwing a SOAPException with the following message
 
 
javax.xml.soap.SOAPException: Invalid Content-Type:application/octet-stream        
 
so i was wondering if i need to change anything MIME related to make Hermes interoperate with jwsdp 1.0.1. i am not using SMTP .
-Venkat


---------------------------------
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

[ebxmlms-develop] Extra bytes in message?

[Mayne, P. <Pet...@ap...>]

Content-Length: 5374=0A=
SOAPAction: ebXML=0A=
Content-Type: multipart/related; type=3D"text/xml"; =
boundary=3D"----=3D_BOUNDARY_01"; charset=3D"utf-8"; =
start=3D"<soappart>"=0A=
User-Agent: Java/1.4.1_01=0A=
Host: b2bbroker-test.telstra.com:6707=0A=
Accept: text/html, image/gif, image/jpeg, *; q=3D.2, */*; q=3D.2=0A=
Connection: keep-alive=0A=
=0A=
------=3D_BOUNDARY_01
Content-Type: text/xml
Content-Id: <soappart>
Content-Transfer-Encoding: binary

<?xml version=3D"1.0" encoding=3D"UTF-8"?>=0A=
<soap-env:Envelope =
xmlns:soap-env=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:xlink=3D"http://www.w3.org/1999/xlink" =
xsi:schemaLocation=3D"http://schemas.xmlsoap.org/soap/envelope/ =
http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soa=
p-env:Header =
xsi:schemaLocation=3D"http://www.oasis-open.org/committees/ebxml-msg/sch=
ema/msg-header-2_0.xsd =
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd=
"><eb:MessageHeader =
xmlns:eb=3D"http://www.oasis-open.org/committees/ebxml-msg/schema/msg-he=
ader-2_0.xsd" soap-env:mustUnderstand=3D"1" soap-env:actor=3D"" =
eb:version=3D"2.0"><eb:From><eb:PartyId =
eb:type=3D"ABN">85006904187</eb:PartyId><eb:Role>Seller</eb:Role></eb:Fr=
om><eb:To><eb:PartyId =
eb:type=3D"ABN">33051775556</eb:PartyId><eb:Role>Buyer</eb:Role></eb:To>=
<eb:CPAId>2.0</eb:CPAId><eb:ConversationId>8oEFOjwemgquEUbis7zzy6Gkzzw</=
eb:ConversationId><eb:Service =
eb:type=3D"Order">urn:Telstra:Procurement$2.0</eb:Service><eb:Action>Rec=
eiptAcknowledgment</eb:Action><eb:MessageData><eb:MessageId>20030804-123=
244-r7E8OzrmlP</eb:MessageId><eb:Timestamp>2003-08-04T02:32:44Z</eb:Time=
stamp><eb:RefToMessageId>EeGR6GG4mgquEEbis6zzy6Gkzzw</eb:RefToMessageId>=
</eb:MessageData></eb:MessageHeader><eb:AckRequested =
xmlns:eb=3D"http://www.oasis-open.org/committees/ebxml-msg/schema/msg-he=
ader-2_0.xsd" soap-env:mustUnderstand=3D"1" =
soap-env:actor=3D"urn:oasis:names:tc:ebxml-msg:actor:toPartyMSH" =
eb:version=3D"2.0" eb:signed=3D"false"/><eb:SyncReply =
xmlns:eb=3D"http://www.oasis-open.org/committees/ebxml-msg/schema/msg-he=
ader-2_0.xsd" soap-env:mustUnderstand=3D"1" =
soap-env:actor=3D"http://schemas.xmlsoap.org/soap/actor/next" =
eb:version=3D"2.0"/><ds:Signature =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#">=0A=
<ds:SignedInfo>=0A=
<ds:CanonicalizationMethod =
Algorithm=3D"http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>=0A=
<ds:SignatureMethod =
Algorithm=3D"http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>=0A=
<ds:Reference URI=3D"">=0A=
<ds:Transforms>=0A=
<ds:Transform =
Algorithm=3D"http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>=0A=
<ds:Transform =
Algorithm=3D"http://www.w3.org/TR/1999/REC-xpath-19991116">=0A=
<ds:XPath>not(ancestor-or-self::node()[@soap-env:actor=3D"urn:oasis:name=
s:tc:ebxml-msg:actor:nextMSH"] | =
ancestor-or-self::node()[@soap-env:actor=3D"http://schemas.xmlsoap.org/s=
oap/actor/next"])</ds:XPath>=0A=
</ds:Transform>=0A=
<ds:Transform =
Algorithm=3D"http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/>=0A=
</ds:Transforms>=0A=
<ds:DigestMethod =
Algorithm=3D"http://www.w3.org/2000/09/xmldsig#sha1"/>=0A=
<ds:DigestValue>XQhIGYsgvi7nniMSrHldpeedfVg=3D</ds:DigestValue>=0A=
</ds:Reference>=0A=
<ds:Reference URI=3D"cid:attachment0">=0A=
<ds:DigestMethod =
Algorithm=3D"http://www.w3.org/2000/09/xmldsig#sha1"/>=0A=
<ds:DigestValue>nfW4Xokhu2eVAhzHsEhATZYQxGc=3D</ds:DigestValue>=0A=
</ds:Reference>=0A=
</ds:SignedInfo>=0A=
<ds:SignatureValue>=0A=
woL5RhCpAAMlv2ygQqzHsEWZ7AlfNSMc+9XQ72+TULJzYdMtgWhY2qH/x9LUy24kMdcDW2uH=
TE0Y=0A=
aBUDM8Fopmt29MhYWi68VTbaP1oIm6xtu+Hri2HrSXhtNStUCAkad1VwjQcqw4rKmDA3uimY=
xkPE=0A=
v64mcozZZL9E1d6H2qc=3D=0A=
</ds:SignatureValue>=0A=
</ds:Signature></soap-env:Header><soap-env:Body =
xsi:schemaLocation=3D"http://www.oasis-open.org/committees/ebxml-msg/sch=
ema/msg-header-2_0.xsd =
http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd=
"><eb:Manifest =
xmlns:eb=3D"http://www.oasis-open.org/committees/ebxml-msg/schema/msg-he=
ader-2_0.xsd" eb:version=3D"2.0"><eb:Reference eb:id=3D"attachment0" =
xlink:type=3D"simple" xlink:href=3D"cid:attachment0" =
xlink:role=3D"ReceiptAcknowledgment"><eb:Description =
xml:lang=3D"en-US">ReceiptAcknowledgment</eb:Description></eb:Reference>=
</eb:Manifest></soap-env:Body></soap-env:Envelope>
------=3D_BOUNDARY_01
Content-Type: text/xml
Content-Id: <attachment0>
Content-Transfer-Encoding: binary

<?xml version=3D"1.0" encoding=3D"UTF-8"?>=0A=
<bpsrcptack:ReceiptAcknowledgment =
xmlns:bpsrcptack=3D"http://www.ebxml.org/BusinessProcess/BPSS_SIGNALS" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:xlink=3D"http://www.w3.org/1999/xlink" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">=0A=
  =
<bpsrcptack:OriginalMessageIdentifier>EeGR6GG4mgquEEbis6zzy6Gkzzw</bpsrc=
ptack:OriginalMessageIdentifier>=0A=
  <bpsrcptack:NonRepudiationInformation>=0A=
    <bpsrcptack:MessagePartNRInformation>=0A=
      =
<bpsrcptack:MessagePartIdentifier>cid:oPRgQ04lmgqukEbis8zzy6Gkzzw</bpsrc=
ptack:MessagePartIdentifier>=0A=
    </bpsrcptack:MessagePartNRInformation>=0A=
  </bpsrcptack:NonRepudiationInformation>=0A=
  <bpsrcptack:FromPartyInfo =
bpsrcptack:type=3D"ABN">85006904187</bpsrcptack:FromPartyInfo>=0A=
  <bpsrcptack:ToPartyInfo =
bpsrcptack:type=3D"ABN">33051775556</bpsrcptack:ToPartyInfo>=0A=
  <bpsrcptack:FromRole bpsrcptack:name=3D"Seller" =
xlink:href=3D"urn:SpherionEdu:Procurement$1.0#Seller" =
xlink:type=3D"simple"/>=0A=
  <bpsrcptack:ToRole bpsrcptack:name=3D"Buyer" =
xlink:href=3D"urn:Telstra:Procurement$1.0#Buyer" =
xlink:type=3D"simple"/>=0A=
  =
<bpsrcptack:OriginalMessageDateTime>2003-08-04T02:33:55.158Z</bpsrcptack=
:OriginalMessageDateTime>=0A=
  =
<bpsrcptack:ThisMessageDateTime>2003-08-04T02:32:44Z</bpsrcptack:ThisMes=
sageDateTime>=0A=
  <bpsrcptack:ProcessSpecificationInfo bpsrcptack:name=3D"Procurement" =
bpsrcptack:uuid=3D"urn:Telstra:Procurement$1.0" =
bpsrcptack:version=3D"1.0" xlink:href=3D"urn:Telstra:Procurement$1.0" =
xlink:type=3D"simple"/>=0A=
</bpsrcptack:ReceiptAcknowledgment>=0A=

------=3D_BOUNDARY_01--

Re: [ebxmlms-develop] Hermes MSH eats my Pong reply...

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

Daniel,
Thanks for your contribution. My colleagues are now examining the root cause
of the problem and your patch.
Regards, -Patrick


----- Original Message ----- 
From: "Daniel Bergh" <Dan...@os...>
To: <ebx...@li...>
Sent: Friday, August 01, 2003 06:06 PM
Subject: [ebxmlms-develop] Hermes MSH eats my Pong reply...


>
> Hi,
>
> I have made a small program that uses Hermes to send a Ping request to
> another MSH implementation and waits for a Pong reply. The problem is that
I
> never get the Pong reply. The log tells me that Hermes actually gets the
> Pong reply but the reply is never sent to my client (other messages gets
to
> the client, so there's nothing wrong with it...).
>
> I have attached a snipp from the log that confirms that Hermes actually
gets
> the reply. I have also attached my client code (I have just made small
> modifications to the loopback example).
>
> Looking into the code I can see that Pong replies get a special treatment.
A
> Delivery thread is attached to the Transaction object, but since I use the
> polling scenario (the first one described in the user documentation) this
> thread does nothing. As far as I can see the message isn't saved at all,
so
> obviously my polling client never finds it. Shouldn't the message be
stored
> on the messageServer just like any other messages?
>
> MessageServiceHandler.java version 1.173 Line 4914
>             else if (isPong) {
>                 String pingMessageId = ebxmlMessage.getMessageHeader().
>                     getRefToMessageId();
>                 appContext = messageServer.getApplicationContext
>                     (pingMessageId, tx);
>                 mshConnection = (MessageServiceHandlerConnection)
>                     mshConnectionTable.get(appContext);
>                 Delivery delivery = new Delivery(this, appContext,
>                     mshConnection.getMessageServiceHandlerConfig().
>                     getMessageListener(), ebxmlMessage);
>                 tx.addThread(delivery);
>                 logger.info("Pong message is received");
>             }
>
> Maybe this code should be changed to something like the following (WARNING
I
> haven't tested this at all).
>
>             else if (isPong) {
>                 String pingMessageId = ebxmlMessage.getMessageHeader().
>                     getRefToMessageId();
>                 appContext = messageServer.getApplicationContext
>                     (pingMessageId, tx);
>                 mshConnection = (MessageServiceHandlerConnection)
>                     mshConnectionTable.get(appContext);
>                 messageServer.store(ebxmlMessage, appContext,
>                     MessageServer.STATE_RECEIVED, false, tx);
>
>                 Delivery delivery = new Delivery(this, appContext,
>                     mshConnection.getMessageServiceHandlerConfig().
>                     getMessageListener(), ebxmlMessage);
>                 tx.addThread(delivery);
>                 logger.info("Pong message is received");
>             }
>
> Comments to the code: I have just tried my client on the 0931-release, but
> the current Pong handling code in the CVS repository doesn't seem to have
> changed...
>
> Regards
>
> Daniel Bergh
>
>

[ebxmlms-develop] Hermes MSH eats my Pong reply...

[Daniel B. <Dan...@os...>]

Hi,

I have made a small program that uses Hermes to send a Ping request to
another MSH implementation and waits for a Pong reply. The problem is that I
never get the Pong reply. The log tells me that Hermes actually gets the
Pong reply but the reply is never sent to my client (other messages gets to
the client, so there's nothing wrong with it...).

I have attached a snipp from the log that confirms that Hermes actually gets
the reply. I have also attached my client code (I have just made small
modifications to the loopback example).

Looking into the code I can see that Pong replies get a special treatment. A
Delivery thread is attached to the Transaction object, but since I use the
polling scenario (the first one described in the user documentation) this
thread does nothing. As far as I can see the message isn't saved at all, so
obviously my polling client never finds it. Shouldn't the message be stored
on the messageServer just like any other messages?

MessageServiceHandler.java version 1.173 Line 4914
            else if (isPong) {
                String pingMessageId = ebxmlMessage.getMessageHeader().
                    getRefToMessageId();
                appContext = messageServer.getApplicationContext
                    (pingMessageId, tx);
                mshConnection = (MessageServiceHandlerConnection)
                    mshConnectionTable.get(appContext);
                Delivery delivery = new Delivery(this, appContext,
                    mshConnection.getMessageServiceHandlerConfig().
                    getMessageListener(), ebxmlMessage);
                tx.addThread(delivery);
                logger.info("Pong message is received");
            }

Maybe this code should be changed to something like the following (WARNING I
haven't tested this at all).

            else if (isPong) {
                String pingMessageId = ebxmlMessage.getMessageHeader().
                    getRefToMessageId();
                appContext = messageServer.getApplicationContext
                    (pingMessageId, tx);
                mshConnection = (MessageServiceHandlerConnection)
                    mshConnectionTable.get(appContext);
                messageServer.store(ebxmlMessage, appContext,
                    MessageServer.STATE_RECEIVED, false, tx);

                Delivery delivery = new Delivery(this, appContext,
                    mshConnection.getMessageServiceHandlerConfig().
                    getMessageListener(), ebxmlMessage);
                tx.addThread(delivery);
                logger.info("Pong message is received");
            }

Comments to the code: I have just tried my client on the 0931-release, but
the current Pong handling code in the CVS repository doesn't seem to have
changed...

Regards

Daniel Bergh

RE: [ebxmlms-develop] Signature and axis

[Ronald v. K. <rv...@ab...>]

Sorry, no. I haven't had a system set up that works with Signatures. If
you want to know I can set it up, but have no other options to test
against than Hermes. (no Tibco/Fujitsu or others)

Ronald

> -----Oorspronkelijk bericht-----
> Van: Patrick Yee [mailto:kc...@ce...]
> Verzonden: dinsdag 29 juli 2003 4:39
> Aan: ebx...@li...
> Onderwerp: Re: [ebxmlms-develop] Signature and axis
> 
> 
> Hi Ronald,
> Any news about this? :-)
> Thanks very much, -Patrick
> 
> 
> 
> Ronald van Kuijk wrote:
> 
> > Hi,
> >
> > In the PKISignatureImpl.java you do the following:
> >
> >       DocumentResult docResult = new DocumentResult();
> >       TransformerFactory.newInstance().newTransformer().
> >           transform(soapPart.getContent(), docResult);
> >       ByteArrayOutputStream baos = new ByteArrayOutputStream();
> >       (new XMLWriter(baos)).write(docResult.getDocument());
> >       DocumentBuilderFactory factory = DocumentBuilderFactory.
> >           newInstance();
> >       factory.setNamespaceAware(true);
> >       // soapPartDocument is a DOM equivilance of soapPart
> >       final Document soapPartDocument = 
> factory.newDocumentBuilder().
> >           parse(new ByteArrayInputStream(baos.toByteArray()));
> >
> >
> > Just to get from a soapPart to a soapPartDocument. According to the 
> > specs (well the tutorial at least):
> >
> > Moreover, the |SOAPPart| of a |SOAPMessage| is also a DOM Level 2 
> > |Document|, and can be manipulated as such by applications, 
> tools and 
> > libraries that use DOM. See Chapter 6 
> > 
> <http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JAXPDOM.html#wp79996> 
> > for details about DOM. See Adding Content to the SOAPPart Object 
> > <http://java.sun.com/j2ee/1.4/docs/tutorial/doc/SAAJ3.html#wp64119> 
> > and Adding a Document to the SOAP Body 
> > <http://java.sun.com/j2ee/1.4/docs/tutorial/doc/SAAJ3.html#wp78963> 
> > for details on how to use DOM documents with the SAAJ API.
> >
> >       final Document soapPartDocument = (Document) soapPart;
> >
> >
> > Should work as well.  Maybe the 'axis' problem is solved 
> then as well.
> > Eclipse does not complain about the casting and is really good at 
> > checking this, I'll try running it later (have currently no server 
> > configured for using certificates).
> >
> > Ronald
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Free pre-built ASP.NET 
> sites including
> > Data Reports, E-commerce, Portals, and Forums are available now.
> > Download today and enter to win an XBOX or Visual Studio .NET.
> > 
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_06
> 1203_01/01
> > _______________________________________________
> > ebxmlms-develop mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet
> _072303_01/01
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> 

Re: [ebxmlms-develop] Signature and axis

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

Hi Ronald,
Any news about this? :-)
Thanks very much, -Patrick



Ronald van Kuijk wrote:

> Hi,
>
> In the PKISignatureImpl.java you do the following:
>
>       DocumentResult docResult = new DocumentResult();
>       TransformerFactory.newInstance().newTransformer().
>           transform(soapPart.getContent(), docResult);
>       ByteArrayOutputStream baos = new ByteArrayOutputStream();
>       (new XMLWriter(baos)).write(docResult.getDocument());
>       DocumentBuilderFactory factory = DocumentBuilderFactory.
>           newInstance();
>       factory.setNamespaceAware(true);
>       // soapPartDocument is a DOM equivilance of soapPart
>       final Document soapPartDocument = factory.newDocumentBuilder().
>           parse(new ByteArrayInputStream(baos.toByteArray()));
>
>
> Just to get from a soapPart to a soapPartDocument. According to the 
> specs (well the tutorial at least):
>
> Moreover, the |SOAPPart| of a |SOAPMessage| is also a DOM Level 2 
> |Document|, and can be manipulated as such by applications, tools and 
> libraries that use DOM. See Chapter 6 
> <http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JAXPDOM.html#wp79996> 
> for details about DOM. See Adding Content to the SOAPPart Object 
> <http://java.sun.com/j2ee/1.4/docs/tutorial/doc/SAAJ3.html#wp64119> 
> and Adding a Document to the SOAP Body 
> <http://java.sun.com/j2ee/1.4/docs/tutorial/doc/SAAJ3.html#wp78963> 
> for details on how to use DOM documents with the SAAJ API.
>
>       final Document soapPartDocument = (Document) soapPart;
>
>
> Should work as well.  Maybe the 'axis' problem is solved then as well.
> Eclipse does not complain about the casting and is really good at 
> checking this, I'll try running it later (have currently no server 
> configured for using certificates).
>
> Ronald
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop

Re: [ebxmlms-develop] Digital signature interoperability

[Ng C. Y. <cy...@cs...>]

Hi,

> I've noticed a few commits that seem to be relevant to signatures. Is it 
> worth getting the latest code and trying again?

         I just incorporate the change in 1.0 into 0.9.3.1 as Bob has 
succeeded testing with Boxman last week. Now, it is obvious to say that 
xmlsec 1.0.4 has bugs in canonicalization algorithm (xml:lang removed). It 
is worthwhile to try the latest commit.

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
----------------------------------------------------------------------------

Re: [ebxmlms-develop] KeyInfo in outgoing messages

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Come on Peter, could you do us a favour and help to test it? We need
your comment. Moreover, that tool is not an alpha-release monster... :-)<br>
-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] KeyInfo in outgoing messages</title>
  <p><font size="2">If more testing will only take a week or so, I'll
wait until you release it. We're multitasking at the moment. :-)</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&nbsp; 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: Thursday, 24 July 2003 4:55 PM</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] KeyInfo in outgoing
messages</font>
  </p>
  <br>
  <p><font size="2">Peter,</font>
  </p>
  <p><font size="2">We just have our tool ready.. yet it depends on
xmlsec library to do canonicalization and transformation. For the other
steps, e.g. digest generation, etc, we do it ourselves. It takes in a
MIME multipart message and generate the intermediate documents.</font></p>
  <p><font size="2">The whole tool takes 2.5MB in zip format... do you
have a ftp account so that I can upload it to you? We will open source
the tool after some more testing.</font></p>
  <p><font size="2">Regards, -Patrick</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>

Re: [ebxmlms-develop] KeyInfo in outgoing messages

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Peter,<br>
<br>
We just have our tool ready.. yet it depends on xmlsec library to do
canonicalization and transformation. For the other steps, e.g. digest
generation, etc, we do it ourselves. It takes in a MIME multipart
message and generate the intermediate documents.<br>
<br>
The whole tool takes 2.5MB in zip format... do you have a ftp account
so that I can upload it to you? We will open source the tool after some
more testing.<br>
<br>
Regards, -Patrick<br>
<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] KeyInfo in outgoing messages</title>
  <p><font size="2">We're still can't validate digital signatures in
either direction. Obviously the xmlsec thing would have affected this,
but recent versions of Hermes have been using the later version.</font></p>
  <p><font size="2">I'll have a think, but I'm otherwise engaged at the
moment.</font>
  </p>
  <p><font size="2">We had a discussion with our patner on Tuesday.
Tibco are asking for exactly the same information that your new tool
will provide (the state of the document at various stages of signing),
so we're eager to try it out.</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&nbsp; 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: Wednesday, 23 July 2003 6:03 PM</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] KeyInfo in outgoing
messages</font>
  </p>
  <br>
  <p><font size="2">arrr yes... agreed. Peter, do you think it is
possible for you to do this?</font>
  <br>
  <font size="2">BTW, how is the result of digital signature
interoperability between Hermes and Tibco, with you adhoc quick fix?</font>
  <br>
  <font size="2">Regards, -Patrick</font>
  </p>
  <br>
  <br>
  <p><font size="2">Mayne, Peter wrote:</font>
  </p>
  <p><font size="2">Adding a parameter to sign() doesn't handle signed
acks sent by Hermes, so I think the hook would be better.</font>
  <br>
  <font size="2">&nbsp;</font>
  <br>
  <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&nbsp; 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: Wednesday, 23 July 2003 1:31 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] KeyInfo in outgoing
messages </font>
  </p>
  <br>
  <p><font size="2">Agreed. Two approaches: </font>
  <br>
  <font size="2">1. add an optional parameter at ebxmlMessage.sign() to
control whether to add KeyInfo or not. </font>
  <br>
  <font size="2">2. write a hook to do digital signature </font>
  <br>
  <font size="2">Comment? </font>
  <br>
  <font size="2">Regards, -Patrick </font>
  <br>
  <font size="2">The information contained in this email and any
attachments to it:</font>
  </p>
  <p><font size="2">(a) may be confidential and if you are not the
intended recipient, any interference with, </font>
  <br>
  <font size="2">use, disclosure or copying of this material is
unauthorised and prohibited; and</font>
  </p>
  <p><font size="2">(b) may contain personal information of the
recipient and/or the sender as defined </font>
  <br>
  <font size="2">under the Privacy Act 1988 (Cth). Consent is hereby
given by the recipient(s) to </font>
  <br>
  <font size="2">collect, hold and use such information and any
personal information contained in a </font>
  <br>
  <font size="2">response to this email, for any reasonable purpose in
the ordinary course of </font>
  <br>
  <font size="2">Spherion's </font>
  <br>
  <font size="2">business, including forwarding this email internally
or disclosing it to a third party. All </font>
  <br>
  <font size="2">personal information collected by Spherion will be
handled in accordance with </font>
  <br>
  <font size="2">Spherion's Privacy Policy. If you have received this
email in error, please notify the </font>
  <br>
  <font size="2">sender and delete it.</font>
  </p>
  <p><font size="2">(c) you agree not to employ or arrange employment
for any candidate(s) supplied in </font>
  <br>
  <font size="2">this email and any attachments without first entering
into a contractual agreement with </font>
  <br>
  <font size="2">Spherion. You further agree not to divulge any
information contained in this document </font>
  <br>
  <font size="2">to any person(s) or entities without the express
permission of Spherion.</font>
  </p>
  <br>
  <p><font size="2">&nbsp; </font>
  <br>
  <font size="2">-------------------------------------------------------
This SF.net email is sponsored by: VM Ware With VMware you can run
multiple operating systems on a single machine. WITHOUT REBOOTING! Mix
Linux / Windows / Novell virtual machines at the same time. Free trial
click here: <a href="http://www.vmware.com/wl/offer/345/0"
 target="_blank">http://www.vmware.com/wl/offer/345/0</a>
_______________________________________________ ebxmlms-develop mailing
list <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> <a
 href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop"
 target="_blank">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a></font></p>
</blockquote>
</body>
</html>

RE: [ebxmlms-develop] channels, classes, jndi etc.

[Ronald v. K. <rv...@ab...>]

Reed between the lines

> -----Oorspronkelijk bericht-----
> Van: Patrick Yee [mailto:kc...@ce...]
> Verzonden: woensdag 23 juli 2003 10:29
> Aan: ebx...@li...
> Onderwerp: Re: [ebxmlms-develop] channels, classes, jndi etc.
> 
> 
> We don't like lock-in to a particular app server. 

Me neither. At work we use WebLogic, at home I use Jboss and Tomcat.
Therefore I want it to be standards compliant as well 

> Configuration is an 
> issue. If the configuration complexity is on Hermes, then we 
> can make it 
> easier by providing more tools. 

Hmm.. configuring a datasource/connectionpool is AppServer specific,
using a connectionpool with transactions isn't. That's standard java
(subset of j2ee)

But if the complexity is on 
> the external 
> server, it will be hard to solve the problem.

Just like now? Several JDK's, several tomcat issues etc? It won't become
more complex; configuring a datasource on Tomcat, JBoss, Weblogic,
Websphere is just as simpel as it is now in Hermes
> 
> A raw connection is a connection created directly, bypassing the 
> connection pool manager. You know, in the past we have a mechanism to 
> check the validity of a connection before checking out from the 
> connection pool. The checking method is to do a "select 1" on a 
> particular table. Obviously, before that table is created 
> (e.g. in the 
> early init state of Hermes), we need to get a connection 
> which bypassed 
> the connection pool checking.
> 

Ok
> Cheers, -Patrick
> 
> 
> 
> Ronald van Kuijk wrote:
> 
> >For using ejb's etc I can understand that a little, we 
> ourselves do not
> >use the env parameters to pass values to ejb's, we use 
> config files as
> >well. 
> >
> >For datasources and app servers in general, I hope you do 
> not mean that
> >configuring a datasource on a j2ee appserver is to difficult 
> and should
> >prevent Hermes from using them? 
> >
> >Even Tomcat supports connectionpools and transactions. 
> Configuring them
> >is easy, just as easy as it is in Hermes. 
> >
> >Ronald
> >
> >btw, can you confirm that the rawconnection is only needed to do
> >database things outside of a transaction?
> >
> >  
> >
> >>-----Oorspronkelijk bericht-----
> >>Van: Patrick Yee [mailto:kc...@ce...]
> >>Verzonden: dinsdag 22 juli 2003 17:43
> >>Aan: ebx...@li...
> >>Onderwerp: Re: [ebxmlms-develop] channels, classes, jndi etc.
> >>
> >>
> >>One of the concerns for using more J2EE services (we are 
> >>suffering this in
> >>another product we are doing now..) is configuration. We can 
> >>assume that the
> >>J2EE services provided by different app servers can be 
> >>accessed without
> >>modifying any code. But the configuration way of different 
> >>app servers would
> >>be different, even when JMX is used. There is no a standard way to
> >>configure. This makes the configuration work complicated, and 
> >>eventually
> >>leads to difficult deployment.
> >>
> >>Any experience to share in this direction?
> >>
> >>-Patrick
> >>
> >>----- Original Message ----- 
> >>From: "Ronald van Kuijk" <rv...@ab...>
> >>To: <ebx...@li...>
> >>Sent: Monday, July 14, 2003 05:55 AM
> >>Subject: Re: [ebxmlms-develop] channels, classes, jndi etc.
> >>
> >>
> >>    
> >>
> >>>While I was working on a small example of looking up connectors for
> >>>channels (shouldn't we standardize on a name for these?) 
> >>>      
> >>>
> >>together with
> >>    
> >>
> >>>their configuration, it really started to look like I was 
> >>>      
> >>>
> >>implementing
> >>    
> >>
> >>>sessionbeans. I started from
> >>>
> >>>      
> >>>
> >>http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources
> >>-howto.html#Adding%20Custom%20Resource%20Factories
> >>    
> >>
> >>>and then had to add some other functionality. Eventually 
> >>>      
> >>>
> >>the list was
> >>    
> >>
> >>>- Looking-up components by their JNDI name
> >>>- writing some config mechanism these components could use 
> >>>      
> >>>
> >>(deployment
> >>    
> >>
> >>>descriptors)
> >>>- having it work with transactions
> >>>- limiting the amount of simultaneous use (to prevent the
> >>>application/backend to become overloaded)
> >>>- .....
> >>>
> >>>At that moment I stopped, took a good night sleep and came 
> >>>      
> >>>
> >>up with the
> >>    
> >>
> >>>following.
> >>>
> >>>I think that Hermes should support two different approaches:
> >>>- Lightweight, just running on a servlet engine
> >>>- Running on a j2ee server (more complex in some parts, simpeler in
> >>>      
> >>>
> >>others)
> >>    
> >>
> >>>The reason I bring this up again, becomes clear by the 
> >>>      
> >>>
> >>following table
> >>    
> >>
> >>>which contains current and future functionality:
> >>>
> >>>Feature                     Hermes              Tomcat *1  
>     Jetty
> >>>Plus *2     j2ee
> >>>ConnectionPool, with jndi   No, Proprietary     standard    
> >>>      
> >>>
> >>   standard
> >>    
> >>
> >>>         standard
> >>>Transactions                Proprietary         standard *3 
> >>>      
> >>>
> >>   standard
> >>    
> >>
> >>>*3       standard *3
> >>>authent. / author.          Proprietary         jaas           jaas
> >>>         jaas
> >>>Monitoring (jmx?)           No                  yes *4      
> >>>      
> >>>
> >>   yes *5
> >>    
> >>
> >>>         yes
> >>>                            (curr. proprietary)
> >>>Clustering                  No                  No (t yet *6)  No
> >>>         standard
> >>>JavaMail                    Yes,(other config)  yes            yes
> >>>        yes
> >>>JCA *7                      n/a                 No             No
> >>>         Yes
> >>>
> >>>*1 : http://jakarta.apache.org/tomcat/
> >>>*2 : http://jetty.mortbay.com/jetty/plus/
> >>>*3 : JTA
> >>>*4 : Tomcat 4.1 and newer
> >>>*5: http://jetty.mortbay.com/jetty/jmx/index.html
> >>>*6: http://www.onjava.com/pub/a/onjava/2002/07/17/tomcluster.html
> >>>*7: Java Connector Architecture, for furture integration with SAP,
> >>>Siebel, JDEdwards, PeopleSoft, Oracle, DBs, CICS, IMS, MQSeries
> >>>
> >>>With this table, I do not, not at all, want to shed a 
> >>>      
> >>>
> >>negative light on
> >>    
> >>
> >>>Hermes. The opposite, I'd like it to be what it currently 
> >>>      
> >>>
> >>is, a great
> >>    
> >>
> >>>and stable ebXML MSH. All the other functionality, like 
> >>>      
> >>>
> >>connectionpools,
> >>    
> >>
> >>>transaction managers etc, which do work without a problem, 
> should be
> >>>build by those people that have that as their core 
> >>>      
> >>>
> >>(opensource-) business.
> >>    
> >>
> >>>Whatever the difference will be between the 'lightweight' 
> and 'j2ee'
> >>>versions, providing the hooks to choose either path is 
> >>>      
> >>>
> >>needed the most.
> >>    
> >>
> >>>The step from using the build-in jta,jdbc, etc functionality of a
> >>>servlet engine to using a j2ee-server is small.
> >>>
> >>>Any comment?
> >>>
> >>>Highest Regards
> >>>
> >>>Ronald
> >>>
> >>>Ronald van Kuijk wrote:
> >>>
> >>>      
> >>>
> >>>>While developing the small example with JNDI, some 
> >>>>        
> >>>>
> >>questions came to
> >>    
> >>
> >>>>mind. What I was doing looked alot like implementing what 
> >>>>        
> >>>>
> >>can be done
> >>    
> >>
> >>>>with session-beans in a j2ee server.
> >>>>
> >>>>Without thinking of ejb's, the questions this raises for me are:
> >>>>
> >>>>   * How dynamic should new classes (file/url/jms/....) be loaded.
> >>>>         o  Should they be deployed expanded e.g. in a expanded
> >>>>           deployed msh.war directory?
> >>>>         o Is a restart acceptible?
> >>>>   * Where and how should they be pre-configured (url, username,
> >>>>     password, certificate etc).
> >>>>   * Does each AppContext has it's own set of maximum of 
> >>>>        
> >>>>
> >>3 'channel
> >>    
> >>
> >>>>     connectors'  (message, error, notify) or should the be shared
> >>>>     between AppContexts?
> >>>>   * Where is the dynamic configuration persisted (if at all?) in
> >>>>     relation to the AppContext (JNDI?, Database?)
> >>>>   * Should there be a limit in maximum connections to 
> >>>>        
> >>>>
> >>the receiving
> >>    
> >>
> >>>>     application?    * etc...
> >>>>
> >>>>please comment..
> >>>>
> >>>>Regards,
> >>>>
> >>>>Ronald
> >>>>
> >>>>
> >>>>
> >>>>-------------------------------------------------------
> >>>>This SF.Net email sponsored by: Parasoft
> >>>>Error proof Web apps, automate testing & more.
> >>>>Download & eval WebKing and get a free book.
> >>>>www.parasoft.com/bulletproofapps1
> >>>>_______________________________________________
> >>>>ebxmlms-develop mailing list
> >>>>ebx...@li...
> >>>>https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> >>>>        
> >>>>
> >>>
> >>>
> >>>
> >>>-------------------------------------------------------
> >>>This SF.Net email sponsored by: Parasoft
> >>>Error proof Web apps, automate testing & more.
> >>>Download & eval WebKing and get a free book.
> >>>www.parasoft.com/bulletproofapps1
> >>>_______________________________________________
> >>>ebxmlms-develop mailing list
> >>>ebx...@li...
> >>>https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> >>>
> >>>      
> >>>
> >>
> >>-------------------------------------------------------
> >>This SF.net email is sponsored by: VM Ware
> >>With VMware you can run multiple operating systems on a 
> >>single machine.
> >>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual 
> >>machines at the
> >>same time. Free trial click here: 
> http://www.vmware.com/wl/offer/345/0
> >>_______________________________________________
> >>ebxmlms-develop mailing list
> >>ebx...@li...
> >>https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> >>
> >>    
> >>
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a 
> single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual 
> machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> 

Re: [ebxmlms-develop] channels, classes, jndi etc.

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

We don't like lock-in to a particular app server. Configuration is an 
issue. If the configuration complexity is on Hermes, then we can make it 
easier by providing more tools. But if the complexity is on the external 
server, it will be hard to solve the problem.

A raw connection is a connection created directly, bypassing the 
connection pool manager. You know, in the past we have a mechanism to 
check the validity of a connection before checking out from the 
connection pool. The checking method is to do a "select 1" on a 
particular table. Obviously, before that table is created (e.g. in the 
early init state of Hermes), we need to get a connection which bypassed 
the connection pool checking.

Cheers, -Patrick



Ronald van Kuijk wrote:

>For using ejb's etc I can understand that a little, we ourselves do not
>use the env parameters to pass values to ejb's, we use config files as
>well. 
>
>For datasources and app servers in general, I hope you do not mean that
>configuring a datasource on a j2ee appserver is to difficult and should
>prevent Hermes from using them? 
>
>Even Tomcat supports connectionpools and transactions. Configuring them
>is easy, just as easy as it is in Hermes. 
>
>Ronald
>
>btw, can you confirm that the rawconnection is only needed to do
>database things outside of a transaction?
>
>  
>
>>-----Oorspronkelijk bericht-----
>>Van: Patrick Yee [mailto:kc...@ce...]
>>Verzonden: dinsdag 22 juli 2003 17:43
>>Aan: ebx...@li...
>>Onderwerp: Re: [ebxmlms-develop] channels, classes, jndi etc.
>>
>>
>>One of the concerns for using more J2EE services (we are 
>>suffering this in
>>another product we are doing now..) is configuration. We can 
>>assume that the
>>J2EE services provided by different app servers can be 
>>accessed without
>>modifying any code. But the configuration way of different 
>>app servers would
>>be different, even when JMX is used. There is no a standard way to
>>configure. This makes the configuration work complicated, and 
>>eventually
>>leads to difficult deployment.
>>
>>Any experience to share in this direction?
>>
>>-Patrick
>>
>>----- Original Message ----- 
>>From: "Ronald van Kuijk" <rv...@ab...>
>>To: <ebx...@li...>
>>Sent: Monday, July 14, 2003 05:55 AM
>>Subject: Re: [ebxmlms-develop] channels, classes, jndi etc.
>>
>>
>>    
>>
>>>While I was working on a small example of looking up connectors for
>>>channels (shouldn't we standardize on a name for these?) 
>>>      
>>>
>>together with
>>    
>>
>>>their configuration, it really started to look like I was 
>>>      
>>>
>>implementing
>>    
>>
>>>sessionbeans. I started from
>>>
>>>      
>>>
>>http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources
>>-howto.html#Adding%20Custom%20Resource%20Factories
>>    
>>
>>>and then had to add some other functionality. Eventually 
>>>      
>>>
>>the list was
>>    
>>
>>>- Looking-up components by their JNDI name
>>>- writing some config mechanism these components could use 
>>>      
>>>
>>(deployment
>>    
>>
>>>descriptors)
>>>- having it work with transactions
>>>- limiting the amount of simultaneous use (to prevent the
>>>application/backend to become overloaded)
>>>- .....
>>>
>>>At that moment I stopped, took a good night sleep and came 
>>>      
>>>
>>up with the
>>    
>>
>>>following.
>>>
>>>I think that Hermes should support two different approaches:
>>>- Lightweight, just running on a servlet engine
>>>- Running on a j2ee server (more complex in some parts, simpeler in
>>>      
>>>
>>others)
>>    
>>
>>>The reason I bring this up again, becomes clear by the 
>>>      
>>>
>>following table
>>    
>>
>>>which contains current and future functionality:
>>>
>>>Feature                     Hermes              Tomcat *1      Jetty
>>>Plus *2     j2ee
>>>ConnectionPool, with jndi   No, Proprietary     standard    
>>>      
>>>
>>   standard
>>    
>>
>>>         standard
>>>Transactions                Proprietary         standard *3 
>>>      
>>>
>>   standard
>>    
>>
>>>*3       standard *3
>>>authent. / author.          Proprietary         jaas           jaas
>>>         jaas
>>>Monitoring (jmx?)           No                  yes *4      
>>>      
>>>
>>   yes *5
>>    
>>
>>>         yes
>>>                            (curr. proprietary)
>>>Clustering                  No                  No (t yet *6)  No
>>>         standard
>>>JavaMail                    Yes,(other config)  yes            yes
>>>        yes
>>>JCA *7                      n/a                 No             No
>>>         Yes
>>>
>>>*1 : http://jakarta.apache.org/tomcat/
>>>*2 : http://jetty.mortbay.com/jetty/plus/
>>>*3 : JTA
>>>*4 : Tomcat 4.1 and newer
>>>*5: http://jetty.mortbay.com/jetty/jmx/index.html
>>>*6: http://www.onjava.com/pub/a/onjava/2002/07/17/tomcluster.html
>>>*7: Java Connector Architecture, for furture integration with SAP,
>>>Siebel, JDEdwards, PeopleSoft, Oracle, DBs, CICS, IMS, MQSeries
>>>
>>>With this table, I do not, not at all, want to shed a 
>>>      
>>>
>>negative light on
>>    
>>
>>>Hermes. The opposite, I'd like it to be what it currently 
>>>      
>>>
>>is, a great
>>    
>>
>>>and stable ebXML MSH. All the other functionality, like 
>>>      
>>>
>>connectionpools,
>>    
>>
>>>transaction managers etc, which do work without a problem, should be
>>>build by those people that have that as their core 
>>>      
>>>
>>(opensource-) business.
>>    
>>
>>>Whatever the difference will be between the 'lightweight' and 'j2ee'
>>>versions, providing the hooks to choose either path is 
>>>      
>>>
>>needed the most.
>>    
>>
>>>The step from using the build-in jta,jdbc, etc functionality of a
>>>servlet engine to using a j2ee-server is small.
>>>
>>>Any comment?
>>>
>>>Highest Regards
>>>
>>>Ronald
>>>
>>>Ronald van Kuijk wrote:
>>>
>>>      
>>>
>>>>While developing the small example with JNDI, some 
>>>>        
>>>>
>>questions came to
>>    
>>
>>>>mind. What I was doing looked alot like implementing what 
>>>>        
>>>>
>>can be done
>>    
>>
>>>>with session-beans in a j2ee server.
>>>>
>>>>Without thinking of ejb's, the questions this raises for me are:
>>>>
>>>>   * How dynamic should new classes (file/url/jms/....) be loaded.
>>>>         o  Should they be deployed expanded e.g. in a expanded
>>>>           deployed msh.war directory?
>>>>         o Is a restart acceptible?
>>>>   * Where and how should they be pre-configured (url, username,
>>>>     password, certificate etc).
>>>>   * Does each AppContext has it's own set of maximum of 
>>>>        
>>>>
>>3 'channel
>>    
>>
>>>>     connectors'  (message, error, notify) or should the be shared
>>>>     between AppContexts?
>>>>   * Where is the dynamic configuration persisted (if at all?) in
>>>>     relation to the AppContext (JNDI?, Database?)
>>>>   * Should there be a limit in maximum connections to 
>>>>        
>>>>
>>the receiving
>>    
>>
>>>>     application?    * etc...
>>>>
>>>>please comment..
>>>>
>>>>Regards,
>>>>
>>>>Ronald
>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This SF.Net email sponsored by: Parasoft
>>>>Error proof Web apps, automate testing & more.
>>>>Download & eval WebKing and get a free book.
>>>>www.parasoft.com/bulletproofapps1
>>>>_______________________________________________
>>>>ebxmlms-develop mailing list
>>>>ebx...@li...
>>>>https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>>>>        
>>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email sponsored by: Parasoft
>>>Error proof Web apps, automate testing & more.
>>>Download & eval WebKing and get a free book.
>>>www.parasoft.com/bulletproofapps1
>>>_______________________________________________
>>>ebxmlms-develop mailing list
>>>ebx...@li...
>>>https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>>>
>>>      
>>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: VM Ware
>>With VMware you can run multiple operating systems on a 
>>single machine.
>>WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual 
>>machines at the
>>same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
>>_______________________________________________
>>ebxmlms-develop mailing list
>>ebx...@li...
>>https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>>
>>    
>>

Re: [ebxmlms-develop] KeyInfo in outgoing messages

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
arrr yes... agreed. Peter, do you think it is possible for you to do
this?<br>
BTW, how is the result of digital signature interoperability between
Hermes and Tibco, with you adhoc quick fix?<br>
Regards, -Patrick<br>
<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] KeyInfo in outgoing messages</title>
  <p><font size="2">Adding a parameter to sign() doesn't handle signed
acks sent by Hermes, so I think the hook would be better.</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&nbsp; 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: Wednesday, 23 July 2003 1:31 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] KeyInfo in outgoing
messages</font>
  </p>
  <br>
  <p><font size="2">Agreed. Two approaches:</font>
  <br>
  <font size="2">1. add an optional parameter at ebxmlMessage.sign() to
control whether to add KeyInfo or not.</font>
  <br>
  <font size="2">2. write a hook to do digital signature</font>
  </p>
  <p><font size="2">Comment?</font>
  </p>
  <p><font size="2">Regards, -Patrick</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>

RE: [ebxmlms-develop] channels, classes, jndi etc.

[Ronald v. K. <rv...@ab...>]

For using ejb's etc I can understand that a little, we ourselves do not
use the env parameters to pass values to ejb's, we use config files as
well. 

For datasources and app servers in general, I hope you do not mean that
configuring a datasource on a j2ee appserver is to difficult and should
prevent Hermes from using them? 

Even Tomcat supports connectionpools and transactions. Configuring them
is easy, just as easy as it is in Hermes. 

Ronald

btw, can you confirm that the rawconnection is only needed to do
database things outside of a transaction?

> -----Oorspronkelijk bericht-----
> Van: Patrick Yee [mailto:kc...@ce...]
> Verzonden: dinsdag 22 juli 2003 17:43
> Aan: ebx...@li...
> Onderwerp: Re: [ebxmlms-develop] channels, classes, jndi etc.
> 
> 
> One of the concerns for using more J2EE services (we are 
> suffering this in
> another product we are doing now..) is configuration. We can 
> assume that the
> J2EE services provided by different app servers can be 
> accessed without
> modifying any code. But the configuration way of different 
> app servers would
> be different, even when JMX is used. There is no a standard way to
> configure. This makes the configuration work complicated, and 
> eventually
> leads to difficult deployment.
> 
> Any experience to share in this direction?
> 
> -Patrick
> 
> ----- Original Message ----- 
> From: "Ronald van Kuijk" <rv...@ab...>
> To: <ebx...@li...>
> Sent: Monday, July 14, 2003 05:55 AM
> Subject: Re: [ebxmlms-develop] channels, classes, jndi etc.
> 
> 
> > While I was working on a small example of looking up connectors for
> > channels (shouldn't we standardize on a name for these?) 
> together with
> > their configuration, it really started to look like I was 
> implementing
> > sessionbeans. I started from
> >
> http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources
> -howto.html#Adding%20Custom%20Resource%20Factories
> > and then had to add some other functionality. Eventually 
> the list was
> >
> > - Looking-up components by their JNDI name
> > - writing some config mechanism these components could use 
> (deployment
> > descriptors)
> > - having it work with transactions
> > - limiting the amount of simultaneous use (to prevent the
> > application/backend to become overloaded)
> > - .....
> >
> > At that moment I stopped, took a good night sleep and came 
> up with the
> > following.
> >
> > I think that Hermes should support two different approaches:
> > - Lightweight, just running on a servlet engine
> > - Running on a j2ee server (more complex in some parts, simpeler in
> others)
> >
> > The reason I bring this up again, becomes clear by the 
> following table
> > which contains current and future functionality:
> >
> > Feature                     Hermes              Tomcat *1      Jetty
> > Plus *2     j2ee
> > ConnectionPool, with jndi   No, Proprietary     standard    
>    standard
> >          standard
> > Transactions                Proprietary         standard *3 
>    standard
> > *3       standard *3
> > authent. / author.          Proprietary         jaas           jaas
> >          jaas
> > Monitoring (jmx?)           No                  yes *4      
>    yes *5
> >          yes
> >                             (curr. proprietary)
> > Clustering                  No                  No (t yet *6)  No
> >          standard
> > JavaMail                    Yes,(other config)  yes            yes
> >         yes
> > JCA *7                      n/a                 No             No
> >          Yes
> >
> > *1 : http://jakarta.apache.org/tomcat/
> > *2 : http://jetty.mortbay.com/jetty/plus/
> > *3 : JTA
> > *4 : Tomcat 4.1 and newer
> > *5: http://jetty.mortbay.com/jetty/jmx/index.html
> > *6: http://www.onjava.com/pub/a/onjava/2002/07/17/tomcluster.html
> > *7: Java Connector Architecture, for furture integration with SAP,
> > Siebel, JDEdwards, PeopleSoft, Oracle, DBs, CICS, IMS, MQSeries
> >
> > With this table, I do not, not at all, want to shed a 
> negative light on
> > Hermes. The opposite, I'd like it to be what it currently 
> is, a great
> > and stable ebXML MSH. All the other functionality, like 
> connectionpools,
> > transaction managers etc, which do work without a problem, should be
> > build by those people that have that as their core 
> (opensource-) business.
> >
> > Whatever the difference will be between the 'lightweight' and 'j2ee'
> > versions, providing the hooks to choose either path is 
> needed the most.
> > The step from using the build-in jta,jdbc, etc functionality of a
> > servlet engine to using a j2ee-server is small.
> >
> > Any comment?
> >
> > Highest Regards
> >
> > Ronald
> >
> > Ronald van Kuijk wrote:
> >
> > > While developing the small example with JNDI, some 
> questions came to
> > > mind. What I was doing looked alot like implementing what 
> can be done
> > > with session-beans in a j2ee server.
> > >
> > > Without thinking of ejb's, the questions this raises for me are:
> > >
> > >    * How dynamic should new classes (file/url/jms/....) be loaded.
> > >          o  Should they be deployed expanded e.g. in a expanded
> > >            deployed msh.war directory?
> > >          o Is a restart acceptible?
> > >    * Where and how should they be pre-configured (url, username,
> > >      password, certificate etc).
> > >    * Does each AppContext has it's own set of maximum of 
> 3 'channel
> > >      connectors'  (message, error, notify) or should the be shared
> > >      between AppContexts?
> > >    * Where is the dynamic configuration persisted (if at all?) in
> > >      relation to the AppContext (JNDI?, Database?)
> > >    * Should there be a limit in maximum connections to 
> the receiving
> > >      application?    * etc...
> > >
> > > please comment..
> > >
> > > Regards,
> > >
> > > Ronald
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email sponsored by: Parasoft
> > > Error proof Web apps, automate testing & more.
> > > Download & eval WebKing and get a free book.
> > > www.parasoft.com/bulletproofapps1
> > > _______________________________________________
> > > ebxmlms-develop mailing list
> > > ebx...@li...
> > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> >
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Parasoft
> > Error proof Web apps, automate testing & more.
> > Download & eval WebKing and get a free book.
> > www.parasoft.com/bulletproofapps1
> > _______________________________________________
> > ebxmlms-develop mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> >
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: VM Ware
> With VMware you can run multiple operating systems on a 
> single machine.
> WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual 
> machines at the
> same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
> 

Re: [ebxmlms-develop] channels, classes, jndi etc.

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

One of the concerns for using more J2EE services (we are suffering this in
another product we are doing now..) is configuration. We can assume that the
J2EE services provided by different app servers can be accessed without
modifying any code. But the configuration way of different app servers would
be different, even when JMX is used. There is no a standard way to
configure. This makes the configuration work complicated, and eventually
leads to difficult deployment.

Any experience to share in this direction?

-Patrick

----- Original Message ----- 
From: "Ronald van Kuijk" <rv...@ab...>
To: <ebx...@li...>
Sent: Monday, July 14, 2003 05:55 AM
Subject: Re: [ebxmlms-develop] channels, classes, jndi etc.


> While I was working on a small example of looking up connectors for
> channels (shouldn't we standardize on a name for these?) together with
> their configuration, it really started to look like I was implementing
> sessionbeans. I started from
>
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html#Adding%20Custom%20Resource%20Factories
> and then had to add some other functionality. Eventually the list was
>
> - Looking-up components by their JNDI name
> - writing some config mechanism these components could use (deployment
> descriptors)
> - having it work with transactions
> - limiting the amount of simultaneous use (to prevent the
> application/backend to become overloaded)
> - .....
>
> At that moment I stopped, took a good night sleep and came up with the
> following.
>
> I think that Hermes should support two different approaches:
> - Lightweight, just running on a servlet engine
> - Running on a j2ee server (more complex in some parts, simpeler in
others)
>
> The reason I bring this up again, becomes clear by the following table
> which contains current and future functionality:
>
> Feature                     Hermes              Tomcat *1      Jetty
> Plus *2     j2ee
> ConnectionPool, with jndi   No, Proprietary     standard       standard
>          standard
> Transactions                Proprietary         standard *3    standard
> *3       standard *3
> authent. / author.          Proprietary         jaas           jaas
>          jaas
> Monitoring (jmx?)           No                  yes *4         yes *5
>          yes
>                             (curr. proprietary)
> Clustering                  No                  No (t yet *6)  No
>          standard
> JavaMail                    Yes,(other config)  yes            yes
>         yes
> JCA *7                      n/a                 No             No
>          Yes
>
> *1 : http://jakarta.apache.org/tomcat/
> *2 : http://jetty.mortbay.com/jetty/plus/
> *3 : JTA
> *4 : Tomcat 4.1 and newer
> *5: http://jetty.mortbay.com/jetty/jmx/index.html
> *6: http://www.onjava.com/pub/a/onjava/2002/07/17/tomcluster.html
> *7: Java Connector Architecture, for furture integration with SAP,
> Siebel, JDEdwards, PeopleSoft, Oracle, DBs, CICS, IMS, MQSeries
>
> With this table, I do not, not at all, want to shed a negative light on
> Hermes. The opposite, I'd like it to be what it currently is, a great
> and stable ebXML MSH. All the other functionality, like connectionpools,
> transaction managers etc, which do work without a problem, should be
> build by those people that have that as their core (opensource-) business.
>
> Whatever the difference will be between the 'lightweight' and 'j2ee'
> versions, providing the hooks to choose either path is needed the most.
> The step from using the build-in jta,jdbc, etc functionality of a
> servlet engine to using a j2ee-server is small.
>
> Any comment?
>
> Highest Regards
>
> Ronald
>
> Ronald van Kuijk wrote:
>
> > While developing the small example with JNDI, some questions came to
> > mind. What I was doing looked alot like implementing what can be done
> > with session-beans in a j2ee server.
> >
> > Without thinking of ejb's, the questions this raises for me are:
> >
> >    * How dynamic should new classes (file/url/jms/....) be loaded.
> >          o  Should they be deployed expanded e.g. in a expanded
> >            deployed msh.war directory?
> >          o Is a restart acceptible?
> >    * Where and how should they be pre-configured (url, username,
> >      password, certificate etc).
> >    * Does each AppContext has it's own set of maximum of 3 'channel
> >      connectors'  (message, error, notify) or should the be shared
> >      between AppContexts?
> >    * Where is the dynamic configuration persisted (if at all?) in
> >      relation to the AppContext (JNDI?, Database?)
> >    * Should there be a limit in maximum connections to the receiving
> >      application?    * etc...
> >
> > please comment..
> >
> > Regards,
> >
> > Ronald
> >
> >
> >
> > -------------------------------------------------------
> > This SF.Net email sponsored by: Parasoft
> > Error proof Web apps, automate testing & more.
> > Download & eval WebKing and get a free book.
> > www.parasoft.com/bulletproofapps1
> > _______________________________________________
> > ebxmlms-develop mailing list
> > ebx...@li...
> > https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps1
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop
>

Re: [ebxmlms-develop] KeyInfo in outgoing messages

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

KeyInfo in outgoing messagesAgreed. Two approaches:
1. add an optional parameter at ebxmlMessage.sign() to control whether =
to add KeyInfo or not.
2. write a hook to do digital signature

Comment?

Regards, -Patrick

  ----- Original Message -----=20
  From: Mayne, Peter=20
  To: 'ebx...@li...'=20
  Sent: Tuesday, July 22, 2003 09:25 AM
  Subject: [ebxmlms-develop] KeyInfo in outgoing messages


  It turns out that Tibco BusinessConnect can't cope with messages =
(including normal messages and sync ack messages) that have KeyInfo data =
in them.

  Can we consider an option that allows for not including KeyInfo data =
in messages? Currently I have to remember to delete those code sections =
whenever I update the code.

  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.

Re: [ebxmlms-develop] Digital signature interoperability

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Now, the repository is saving the original bytes. :-)<br>
-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>RE: [ebxmlms-develop] Digital signature interoperability</title>
  <p><font size="2">Another problem: when the message is serialised
(using JAXM) into a repository, we then can't in the future go back and
verify a message. The repository woud have to have the original bytes,
rather than a JAXM copy.</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&nbsp; 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>

RE: [ebxmlms-develop] LDAPToURLresolverImpl.java

[Ronald v. K. <rv...@ab...>]

Should it be that people who want to compile the application use the
classes provided by their appserver/servlet engine? Just to be on the
safe side?
 
Ronald

-----Oorspronkelijk bericht-----
Van: Patrick Yee [mailto:kc...@ce...]
Verzonden: dinsdag 15 juli 2003 12:12
Aan: ebx...@li...
Onderwerp: Re: [ebxmlms-develop] LDAPToURLresolverImpl.java




One anomaly is including servlet.jar in the distribution. I have to keep
remembering to delete it. Given that it's a fairly safe assumption that
we already have a servlet.jar (or equivalent), does it need to be in the
distribution?


We need it when compile. But I agree that we can exclude it when making
war file.

-Patrick
------------------------------------------------------- This SF.Net
email sponsored by: Parasoft Error proof Web apps, automate testing &
more. Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
_______________________________________________ ebxmlms-develop mailing
list ebx...@li...
https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop

Re: [ebxmlms-develop] Digital signature interoperability

[Ng C. Y. <cy...@cs...>]

Hi,

> c14n-20010315 will reorder the attributes and NS declarations to lex. order
> prior to digest generation. This rules out order problems...

         I know. But the point is: does xmlsec produce the same thing (i.e., 
exactly the same bytes) as that of other implementation in terms of 
*intermediate* "transformed" and "canonicalized" output? Currently, we are 
trying to log the intermediate transformed and canonicalized output from 
xmlsec. This should be deterministic and compute the same digest value even 
we use other library such as jce.

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
----------------------------------------------------------------------------

Re: [ebxmlms-develop] LDAPToURLresolverImpl.java

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
<blockquote type="cite"
 cite="mid...@s-...">
  <p><font size="2">One anomaly is including servlet.jar in the
distribution. I have to keep remembering to delete it. Given that it's
a fairly safe assumption that we already have a servlet.jar (or
equivalent), does it need to be in the distribution?</font></p>
</blockquote>
<br>
We need it when compile. But I agree that we can exclude it when making
war file.<br>
<br>
-Patrick<br>
</body>
</html>

Re: [ebxmlms-develop] LDAPToURLresolverImpl.java

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

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
1.3 support is solely for compatibility to Weblogic and Websphere.&nbsp; I
am not sure about the JDK support of the latest versions of the above
servers, anybody got some idea? -Patrick<br>
<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] LDAPToURLresolverImpl.java</title>
  <p><font size="2">Another option is to drop 1.3 support.</font>
  </p>
  <p><font size="2">One anomaly is including servlet.jar in the
distribution. I have to keep remembering to delete it. Given that it's
a fairly safe assumption that we already have a servlet.jar (or
equivalent), does it need to be in the distribution?</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&nbsp; F: 61 2 62689777</font>
  </p>
  <p><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, 15 July 2003 2:09 PM</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]
LDAPToURLresolverImpl.java</font>
  </p>
  <br>
  <p><font size="2">Agreed with Peter. I think this case is similar to
JSSE. Although those classes can be found in JDK1.4, we include
jsse.jar in lib directory to make Hermes to be compiled under JDK 1.3.</font></p>
  <p><font size="2">So another option now is to include the JNDI class
library (downloadable from java.sun.com) to lib directory and make the
LDAPToURLresolverImpl.java to hk.hku.cecid.phoenix.message.handler
package.</font></p>
  <p><font size="2">Regards, -Patrick</font>
  </p>
  <br>
  <br>
  <br>
  <p><font size="2">Ronald van Kuijk wrote:</font>
  </p>
  <p><font size="2">JNDI is part of the 1.4 JDK. It's not standard for
1.3, although several servlet engines (Tomcat, Jetty) have versions
that also contain the jndi libraries, so you could use 1.3 with those
versions as wel</font></p>
  <p><font size="2">Ronald</font>
  <br>
  <font size="2">-----Oorspronkelijk bericht-----</font>
  <br>
  <font size="2">Van: Mayne, Peter [<a
 href="mailto:Pet...@ap...">mailto:Pet...@ap...</a>]</font>
  <br>
  <font size="2">Verzonden: maandag 14 juli 2003 2:12</font>
  <br>
  <font size="2">Aan: '<a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a>'</font>
  <br>
  <font size="2">Onderwerp: RE: [ebxmlms-develop]
LDAPToURLresolverImpl.java</font>
  </p>
  <br>
  <p><font size="2">Is JNDI part of standard Java? Could I compile it
without an LDAP implementation? </font>
  <br>
  <font size="2">If not, it would probably be better as a contrib
package? </font>
  <br>
  <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&nbsp; F: 61 2 62689777 </font>
  <br>
  <font size="2">&gt; -----Original Message----- </font>
  <br>
  <font size="2">&gt; From: Ronald van Kuijk [<a
 href="mailto:rv...@ab...">mailto:rv...@ab...</a>] </font>
  <br>
  <font size="2">&gt; Sent: Monday, 14 July 2003 6:30 AM </font>
  <br>
  <font size="2">&gt; To: ebxmlms </font>
  <br>
  <font size="2">&gt; Subject: [ebxmlms-develop]
LDAPToURLresolverImpl.java </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; Hi all, </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; Im writing a LDAPToURLresolverImpl class that can
get the URL </font>
  <br>
  <font size="2">&gt; to send a </font>
  <br>
  <font size="2">&gt; message to from an ldap server. Should I put this
class in the </font>
  <br>
  <font size="2">&gt; hk.hku.cecid.phoenix.message.handler package or
is it more </font>
  <br>
  <font size="2">&gt; something for </font>
  <br>
  <font size="2">&gt; in the transport package? Or should it even be in
my own package </font>
  <br>
  <font size="2">&gt; (net.vankuijk.message.handler/transport) and put
it in a </font>
  <br>
  <font size="2">&gt; contrib part of </font>
  <br>
  <font size="2">&gt; Hermes? </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; Ronald </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">&gt;
------------------------------------------------------- </font>
  <br>
  <font size="2">&gt; This SF.Net email sponsored by: Parasoft </font>
  <br>
  <font size="2">&gt; Error proof Web apps, automate testing &amp;
more. </font>
  <br>
  <font size="2">&gt; Download &amp; eval WebKing and get a free book. </font>
  <br>
  <font size="2">&gt; <a class="moz-txt-link-abbreviated" href="http://www.parasoft.com/bulletproofapps1">www.parasoft.com/bulletproofapps1</a> </font>
  <br>
  <font size="2">&gt; _______________________________________________ </font>
  <br>
  <font size="2">&gt; ebxmlms-develop mailing list </font>
  <br>
  <font size="2">&gt; <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> </font>
  <br>
  <font size="2">&gt; <a
 href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop"
 target="_blank">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a>
  </font>
  <br>
  <font size="2">&gt; </font>
  <br>
  <font size="2">The information contained in this email and any
attachments to it:</font>
  </p>
  <p><font size="2">(a) may be confidential and if you are not the
intended recipient, any interference with, </font>
  <br>
  <font size="2">use, disclosure or copying of this material is
unauthorised and prohibited; and</font>
  </p>
  <p><font size="2">(b) may contain personal information of the
recipient and/or the sender as defined </font>
  <br>
  <font size="2">under the Privacy Act 1988 (Cth). Consent is hereby
given by the recipient(s) to </font>
  <br>
  <font size="2">collect, hold and use such information and any
personal information contained in a </font>
  <br>
  <font size="2">response to this email, for any reasonable purpose in
the ordinary course of </font>
  <br>
  <font size="2">Spherion's </font>
  <br>
  <font size="2">business, including forwarding this email internally
or disclosing it to a third party. All </font>
  <br>
  <font size="2">personal information collected by Spherion will be
handled in accordance with </font>
  <br>
  <font size="2">Spherion's Privacy Policy. If you have received this
email in error, please notify the </font>
  <br>
  <font size="2">sender and delete it.</font>
  </p>
  <p><font size="2">(c) you agree not to employ or arrange employment
for any candidate(s) supplied in </font>
  <br>
  <font size="2">this email and any attachments without first entering
into a contractual agreement with </font>
  <br>
  <font size="2">Spherion. You further agree not to divulge any
information contained in this document </font>
  <br>
  <font size="2">to any person(s) or entities without the express
permission of Spherion.</font>
  </p>
  <br>
  <p><font size="2">&nbsp;&nbsp;&nbsp; </font>
  <br>
  <font size="2">-------------------------------------------------------
This SF.Net email sponsored by: Parasoft Error proof Web apps, automate
testing &amp; more. Download &amp; eval WebKing and get a free book.
<a class="moz-txt-link-abbreviated" href="http://www.parasoft.com/bulletproofapps1">www.parasoft.com/bulletproofapps1</a>
_______________________________________________ ebxmlms-develop mailing
list <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a> <a
 href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop"
 target="_blank">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a></font></p>
</blockquote>
</body>
</html>