Menu
▾
▴
ebxmlms-develop — Development discussions
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
|
Dec
(21) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(22) |
Feb
(41) |
Mar
(100) |
Apr
(113) |
May
(70) |
Jun
(89) |
Jul
(79) |
Aug
(17) |
Sep
(16) |
Oct
(9) |
Nov
(7) |
Dec
(22) |
| 2004 |
Jan
(42) |
Feb
(2) |
Mar
(20) |
Apr
(35) |
May
(18) |
Jun
(14) |
Jul
(12) |
Aug
(3) |
Sep
(5) |
Oct
(3) |
Nov
|
Dec
(1) |
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(3) |
Jun
(9) |
Jul
(18) |
Aug
(10) |
Sep
(12) |
Oct
(4) |
Nov
(4) |
Dec
(9) |
| 2006 |
Jan
(10) |
Feb
(2) |
Mar
(3) |
Apr
(3) |
May
(4) |
Jun
(9) |
Jul
(1) |
Aug
(1) |
Sep
(10) |
Oct
(29) |
Nov
(27) |
Dec
(14) |
| 2007 |
Jan
(9) |
Feb
(23) |
Mar
(3) |
Apr
(9) |
May
(21) |
Jun
(24) |
Jul
(21) |
Aug
(22) |
Sep
(11) |
Oct
(5) |
Nov
(3) |
Dec
(4) |
| 2008 |
Jan
(2) |
Feb
(5) |
Mar
(3) |
Apr
(22) |
May
(18) |
Jun
(14) |
Jul
(27) |
Aug
(20) |
Sep
(16) |
Oct
(17) |
Nov
(26) |
Dec
(48) |
| 2009 |
Jan
(37) |
Feb
(14) |
Mar
(39) |
Apr
(66) |
May
(140) |
Jun
(127) |
Jul
(78) |
Aug
(26) |
Sep
(24) |
Oct
(34) |
Nov
(10) |
Dec
(20) |
| 2010 |
Jan
(6) |
Feb
(7) |
Mar
(51) |
Apr
(49) |
May
(71) |
Jun
(57) |
Jul
(42) |
Aug
(53) |
Sep
(21) |
Oct
(4) |
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
(2) |
May
(3) |
Jun
|
Jul
(2) |
Aug
(5) |
Sep
(1) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2012 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2014 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
(4) |
Jun
(2) |
Jul
(4) |
Aug
(2) |
Sep
(1) |
Oct
|
Nov
(2) |
Dec
(6) |
| 2015 |
Jan
(1) |
Feb
(4) |
Mar
(11) |
Apr
(15) |
May
(12) |
Jun
(13) |
Jul
(7) |
Aug
(7) |
Sep
(5) |
Oct
(3) |
Nov
(5) |
Dec
(15) |
| 2016 |
Jan
(8) |
Feb
(1) |
Mar
(3) |
Apr
(1) |
May
(4) |
Jun
(2) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
(6) |
Jul
(15) |
Aug
|
Sep
(1) |
Oct
(3) |
Nov
(3) |
Dec
(7) |
| 2018 |
Jan
(6) |
Feb
(8) |
Mar
(12) |
Apr
(6) |
May
(5) |
Jun
(3) |
Jul
(4) |
Aug
(6) |
Sep
(1) |
Oct
(2) |
Nov
|
Dec
(2) |
| 2019 |
Jan
(5) |
Feb
(5) |
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2021 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2022 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(9) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(29) |
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Tripathi, A. (GXS) <Aji...@gx...> - 2003-11-07 09:51:54
|
Bob, Patrick, I traced hermes a little bit more. This is what I am getting in the messages ... does it make sense? I think type and value of partyID elements are interchanged!!!!! Please confirm. <eb:From><eb:PartyId eb:type="Sample">fromPartyId</eb:PartyId></eb:From><eb:To><eb:PartyId eb:type="Sampola">toPartyId</eb:PartyId></eb:To> regards, Ajit --------------- The spec: It is further recommended that these 783 values be taken from the EDIRA (ISO 6523), EDIFACT ISO 9735 or ANSI ASC X12 I05 registries. 784 If the PartyId type attribute is not present, the content of the PartyId element MUST be a URI 785 [RFC2396], otherwise the Receiving MSH SHOULD report an error (see section 4.1.5) with errorCode 786 3.1.1 From and To Elements 762 The REQUIRED From element identifies the Party that originated the message. The REQUIRED To 763 element identifies the Party that is the intended recipient of the message. Both To and From can contain 764 logical identifiers, such as a DUNS number, or identifiers that also imply a physical location such as an 765 eMail address. 766 The From and the To elements each contains: 767 * PartyId elements - occurs one or more times 768 * Role element - occurs zero or one times. 769 If either the From or To elements contains multiple PartyId elements, all members of the list MUST 770 identify the same organization. Unless a single type value refers to multiple identification systems, the 771 value of any given type attribute MUST be unique within the list of PartyId elements contained within 772 either the From or To element. 773 Note: This mechanism is particularly useful when transport of a message between the parties may involve multiple 774 intermediaries. More generally, the From Party should provide identification in all domains it knows in support of 775 intermediaries and destinations that may give preference to particular identification systems. 776 The From and To elements contain zero or one Role child element that, if present, SHALL immediately 777 follow the last PartyId child element. 778 3.1.1.1 PartyId Element 779 The PartyId element has a single attribute, type and the content is a string value. The type attribute 780 indicates the domain of names to which the string in the content of the PartyId element belongs. The 781 value of the type attribute MUST be mutually agreed and understood by each of the Parties. It is 782 RECOMMENDED that the value of the type attribute be a URI. It is further recommended that these 783 values be taken from the EDIRA (ISO 6523), EDIFACT ISO 9735 or ANSI ASC X12 I05 registries. 784 If the PartyId type attribute is not present, the content of the PartyId element MUST be a URI 785 [RFC2396], otherwise the Receiving MSH SHOULD report an error (see section 4.1.5) with errorCode 786 set to Inconsistent and severity set to Error. It is strongly RECOMMENDED that the content of the 787 PartyId element be a URI. 788 3.1.1.2 Role Element 789 The Role element identifies the authorized role (fromAuthorizedRole or toAuthorizedRole) |
|
From: Ganga S. <gan...@ya...> - 2003-11-03 23:11:35
|
I wanted to file few issues/bugs in Hermes, which I see during interop testing of Hermes with non-Hermes ebXML server. I don't see any bugs under bug tracker, so I am not sure I should enter bug here or just send email on this. Please let me know. thx ganga __________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/ |
|
From: <ol...@ge...> - 2003-10-29 17:54:23
|
Hi all, Sorry for the crossposting, but I don't know exactly where to post this=20 message. I developped a small application wich use ebxmlss as a reliable=20 messaging system. I send (SMTP) messages with list of recipients to a=20 server and the server routes the message to all recipients (with full=20 ebxmlms). During our developpment, I saw that (apparently) ehbxmlms does'nt verify=20 that acknowledge signature and original sended message signature, as=20 explained in ebxml.org "Message Service Specification 2.0" 6.3.2.5 lines=20 1560 to 1563. The only way to do this was to modify the sources My questions are : 1=B0) Am I wrong, and does ebxmlms has the right behavior (I spent time i= n=20 sources without seeing it) 2=B0) I need to install the application many times, Am I compatible with=20 the ebxmlms licence (sorry, but I'm not sure and don't want to be outlaw). In fact, this part of the application should be available as open source=20 code, but for now we are concentrated on the first release and the=20 sources are not fully documented. We plan to publish it before the end=20 of the this year. Regards, Olivier Moises |
|
From: Bob K. <py...@ce...> - 2003-10-21 07:45:04
|
------=3D_BOUNDARY_01 Content-Type: text/xml; charset=3D"UTF-8" Content-Id: <soappart> Content-Transfer-Encoding: binary <?xml version=3D"1.0" encoding=3D"UTF-8"?> <soap-env:Envelope xmlns:soap-env=3D"http://schemas.xmlsoap.org/soap/enve= lope/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xmlns:xlin= k=3D"http://www.w3.org/1999/xlink" xsi:schemaLocation=3D"http://schemas.x= mlsoap.org/soap/envelope/ http://www.oasis-open.org/committees/ebxml-msg/= schema/envelope.xsd"><soap-env:Header xsi:schemaLocation=3D"http://www.oa= sis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oa= sis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:MessageH= eader xmlns:eb=3D"http://www.oasis-open.org/committees/ebxml-msg/schema/m= sg-header-2_0.xsd" soap-env:mustUnderstand=3D"1" soap-env:actor=3D"" eb:v= ersion=3D"2.0"><eb:From><eb:PartyId eb:type=3D"ebIOT">CECID</eb:PartyId><= eb:Role>Buyer</eb:Role></eb:From><eb:To><eb:PartyId eb:type=3D"ebIOT">SUN= </eb:PartyId><eb:Role>Seller</eb:Role></eb:To><eb:CPAId>ebIOT-CPAT1.CECID= =2ESUN</eb:CPAId><eb:ConversationId>20030924143425343</eb:ConversationId>= <eb:Service eb:type=3D"anyURI">urn:ebIOT-TestService:order</eb:Service><e= b:Action>Order</eb:Action><eb:MessageData><eb:MessageId>20030924-06342701= 5-ebIOT-CPAT1.CECID.SUN.urn:ebIOT-TestService:order.Order.1@147.8.177.35<= /eb:MessageId><eb:Timestamp>2003-09-24T06:34:27Z</eb:Timestamp></eb:Messa= geData></eb:MessageHeader><dsig:Signature xmlns:dsig=3D"http://www.w3.org= /2000/09/xmldsig#"> <dsig:SignedInfo> <dsig:CanonicalizationMethod Algorithm=3D"http://www.w3.org/TR/2001/REC-x= ml-c14n-20010315"/> <dsig:SignatureMethod Algorithm=3D"http://www.w3.org/2000/09/xmldsig#rsa-= sha1"/> <dsig:Reference URI=3D""> <dsig:Transforms> <dsig:Transform Algorithm=3D"http://www.w3.org/2000/09/xmldsig#enveloped-= signature"/> <dsig:Transform Algorithm=3D"http://www.w3.org/TR/1999/REC-xpath-19991116= "> <dsig:XPath>not(ancestor-or-self::node()[@soap-env:actor=3D"urn:oasis:nam= es:tc:ebxml-msg:actor:nextMSH"] | ancestor-or-self::node()[@soap-env:acto= r=3D"http://schemas.xmlsoap.org/soap/actor/next"])</dsig:XPath> </dsig:Transform> <dsig:Transform Algorithm=3D"http://www.w3.org/TR/2001/REC-xml-c14n-20010= 315"/> </dsig:Transforms> <dsig:DigestMethod Algorithm=3D"http://www.w3.org/2000/09/xmldsig#sha1"/>= <dsig:DigestValue>NLzZ5KNIf1iTW8Fdkn0or/0wDJc=3D</dsig:DigestValue> </dsig:Reference> <dsig:Reference URI=3D"cid:0"> <dsig:DigestMethod Algorithm=3D"http://www.w3.org/2000/09/xmldsig#sha1"/>= <dsig:DigestValue>c+YUJufy39UnOTp/GeMKPmr5a0o=3D</dsig:DigestValue> </dsig:Reference> </dsig:SignedInfo> <dsig:SignatureValue> IuRNgCiyZH4/eifWi5sRehpjkZDfJUcyJTwiIF7NQslO29fMfDkZNRaHgHwStiSV1DTWOZbJb= C8E 6jcidx2L1AONUg1fjIHFd/IZ1JGuGentQpdVEfv5VhCEh/IUWYmBTMrky9qAPJ/hCorAv9kPJ= Y3A vnlKQm2rXH9OqklLJfI=3D </dsig:SignatureValue> <dsig:KeyInfo> <dsig:X509Data> <dsig:X509Certificate> MIICnjCCAgegAwIBAgIBAzANBgkqhkiG9w0BAQQFADB+MQswCQYDVQQGEwJISzESMBAGA1UEC= BMJ SG9uZyBLb25nMRIwEAYDVQQHEwlIb25nIEtvbmcxDjAMBgNVBAoTBUNFQ0lEMSQwIgYDVQQLE= xtU aGUgVW5pdmVyc2l0eSBvZiBIb25nIEtvbmcxETAPBgNVBAMTCENFQ0lEIENBMB4XDTAzMDkxO= TAz NDkxMVoXDTEzMDkxNjAzNDkxMVowgYkxCzAJBgNVBAYTAkhLMRIwEAYDVQQIEwlIb25nIEtvb= mcx EjAQBgNVBAcTCUhvbmcgS29uZzEOMAwGA1UEChMFQ0VDSUQxJDAiBgNVBAsTG1RoZSBVbml2Z= XJz aXR5IG9mIEhvbmcgS29uZzEcMBoGA1UEAxMTQ0VDSUQgWE1MIFNpZ25hdHVyZTCBnzANBgkqh= kiG 9w0BAQEFAAOBjQAwgYkCgYEAqPRszoyHH79W5rW3ZoIGomu21IAL5RYmxO86NJy+7oNlxQNt7= FlL lzs7R97NkTMbqcUWSUiPYR0OlsRQqf54YypKpLK8+eE4qHwG8Rhr4JnCw9XB5wNS8/aPPpW2m= kZz tJiPfUKekYi+IL9EuVsn3aA2+OvbeVYfToJ9BHBIptsCAwEAAaMgMB4wDAYDVR0TAQH/BAIwA= DAO BgNVHQ8BAf8EBAMCBsAwDQYJKoZIhvcNAQEEBQADgYEAsUgBEdnF5jZEidjslVEyXEbe58Kip= DAs /Gf4LWawieLuSWj9haqIj+VR3PdqUI8YpmW2XiM0xNf0Fy0K2oaAZKVOwtRSUlefxdj9YL1Pp= Hxk AZj6OgPo0AeTqdsmmUi9FgZclrmB0PrbLFN1fWDBElD0bzMv4hSOflatSdr5cTQ=3D </dsig:X509Certificate> </dsig:X509Data> <dsig:X509Data> <dsig:X509Certificate> MIIClTCCAf6gAwIBAgIBADANBgkqhkiG9w0BAQQFADB+MQswCQYDVQQGEwJISzESMBAGA1UEC= BMJ SG9uZyBLb25nMRIwEAYDVQQHEwlIb25nIEtvbmcxDjAMBgNVBAoTBUNFQ0lEMSQwIgYDVQQLE= xtU aGUgVW5pdmVyc2l0eSBvZiBIb25nIEtvbmcxETAPBgNVBAMTCENFQ0lEIENBMB4XDTAzMDkxO= TAz NDkwMloXDTEzMDkxNjAzNDkwMlowfjELMAkGA1UEBhMCSEsxEjAQBgNVBAgTCUhvbmcgS29uZ= zES MBAGA1UEBxMJSG9uZyBLb25nMQ4wDAYDVQQKEwVDRUNJRDEkMCIGA1UECxMbVGhlIFVuaXZlc= nNp dHkgb2YgSG9uZyBLb25nMREwDwYDVQQDEwhDRUNJRCBDQTCBnzANBgkqhkiG9w0BAQEFAAOBj= QAw gYkCgYEAtKg/Yh0mzTUAzmc9cbQilC2cToaIQiOp09DeGqhDjor8W0W6nzkTmbKHosPq0kGKL= 76J beM0TpKDkTzWYFW/d/p3Ru+b3AMo2DbJO5ETo5cMDrN7AaeQ/LWhzBgunAbpoN/bLI/npmCcD= p+1 np2SiOZGZRIMk/2QvkDSzCwP5b8CAwEAAaMjMCEwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BA= f8E BAMCAgQwDQYJKoZIhvcNAQEEBQADgYEAqXayWWHz8o9LIhX5kzQYrrm2JmSGTXoFG7Uy/+TtF= dNx ymXwrLDpENT9uxQd1SHvrYUshzc295HWMruHOBIufguDZVxdyY+Le49F/TMhW7w8UhANf170D= Tsd rd2tfBLaCJbYTTocoKhq1cYbCOeL8S96NfGZT23UDAgNPcKCWJ4=3D </dsig:X509Certificate> </dsig:X509Data> </dsig:KeyInfo> </dsig:Signature></soap-env:Header><soap-env:Body xsi:schemaLocation=3D"h= ttp://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd h= ttp://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/s= chema/msg-header-2_0.xsd" eb:version=3D"2.0"><eb:Reference eb:id=3D"0" xl= ink:type=3D"simple" xlink:href=3D"cid:0"><eb:Description xml:lang=3D"en-U= S">No description</eb:Description></eb:Reference></eb:Manifest></soap-env= :Body></soap-env:Envelope> ------=3D_BOUNDARY_01 Content-Type: application/octet-stream Content-Id: <0> Content-Transfer-Encoding: binary <?xml version=3D"1.0" encoding=3D"Shift_JIS"?> <!-- Test Payload --> <TestRoot> <TestElement> <Test1 test=3D"1"/> <Test2 test=3D"2"/> <Test3 test=3D"3"> <TestChild child=3D"child3"/> </Test3> <Test4 test=3D"4"/> </TestElement> </TestRoot> ------=3D_BOUNDARY_01-- |
|
From: Bob K. <py...@ce...> - 2003-10-15 04:32:27
|
See the answer inline. Note that in fact we are current designing the new version of Hermes, which will also consider the problem you raise. Regards, Bob Koon Luoh Ren-Shan wrote: >Hi, > > I have the following questions: > > 1. Is it possible to send a message using the "Request" object > without register a new MessageListener? > No. MessageListener should be needed. > > 2. Is it safe to run Hermes in a clustered environment? > (e.g. several web servers with one DB) > > No too. I believe there will be error if running on such situation. > 3. Is there any method/command to purge unused objects > in the object store? > No. > > Thanks. > >Luoh Ren-Shan >lu...@ii... > > > > > > >------------------------------------------------------- >This SF.net email is sponsored by: SF.net Giveback Program. >SourceForge.net hosts over 70,000 Open Source Projects. >See the people who have HELPED US provide better services: >Click here: http://sourceforge.net/supporters.php >_______________________________________________ >ebxmlms-develop mailing list >ebx...@li... >https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop > > > |
|
From: Luoh Ren-S. <lu...@ii...> - 2003-10-15 04:01:51
|
Hi,
I have the following questions:
1. Is it possible to send a message using the "Request" object
without register a new MessageListener?
2. Is it safe to run Hermes in a clustered environment?
(e.g. several web servers with one DB)
3. Is there any method/command to purge unused objects
in the object store?
Thanks.
Luoh Ren-Shan
lu...@ii...
|
|
From: Bob K. <py...@ce...> - 2003-10-02 04:06:04
|
------=3D_BOUNDARY_01 Content-Type: text/xml; charset=3D"UTF-8" Content-Id: <soappart> Content-Transfer-Encoding: binary <?xml version=3D"1.0" encoding=3D"UTF-8"?> <soap-env:Envelope xmlns:soap-env=3D"http://schemas.xmlsoap.org/soap/enve= lope/" xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" xmlns:xlin= k=3D"http://www.w3.org/1999/xlink" xsi:schemaLocation=3D"http://schemas.x= mlsoap.org/soap/envelope/ http://www.oasis-open.org/committees/ebxml-msg/= schema/envelope.xsd"><soap-env:Header xsi:schemaLocation=3D"http://www.oa= sis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd http://www.oa= sis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"><eb:MessageH= eader xmlns:eb=3D"http://www.oasis-open.org/committees/ebxml-msg/schema/m= sg-header-2_0.xsd" soap-env:mustUnderstand=3D"1" soap-env:actor=3D"" eb:v= ersion=3D"2.0"><eb:From><eb:PartyId eb:type=3D"ebIOT">CECID</eb:PartyId><= eb:Role>Buyer</eb:Role></eb:From><eb:To><eb:PartyId eb:type=3D"ebIOT">SUN= </eb:PartyId><eb:Role>Seller</eb:Role></eb:To><eb:CPAId>ebIOT-CPAT1.CECID= =2ESUN</eb:CPAId><eb:ConversationId>20030924143425343</eb:ConversationId>= <eb:Service eb:type=3D"anyURI">urn:ebIOT-TestService:order</eb:Service><e= b:Action>Order</eb:Action><eb:MessageData><eb:MessageId>20030924-06342701= 5-ebIOT-CPAT1.CECID.SUN.urn:ebIOT-TestService:order.Order.1@147.8.177.35<= /eb:MessageId><eb:Timestamp>2003-09-24T06:34:27Z</eb:Timestamp></eb:Messa= geData></eb:MessageHeader><dsig:Signature xmlns:dsig=3D"http://www.w3.org= /2000/09/xmldsig#"> <dsig:SignedInfo> <dsig:CanonicalizationMethod Algorithm=3D"http://www.w3.org/TR/2001/REC-x= ml-c14n-20010315"/> <dsig:SignatureMethod Algorithm=3D"http://www.w3.org/2000/09/xmldsig#rsa-= sha1"/> <dsig:Reference URI=3D""> <dsig:Transforms> <dsig:Transform Algorithm=3D"http://www.w3.org/2000/09/xmldsig#enveloped-= signature"/> <dsig:Transform Algorithm=3D"http://www.w3.org/TR/1999/REC-xpath-19991116= "> <dsig:XPath>not(ancestor-or-self::node()[@soap-env:actor=3D"urn:oasis:nam= es:tc:ebxml-msg:actor:nextMSH"] | ancestor-or-self::node()[@soap-env:acto= r=3D"http://schemas.xmlsoap.org/soap/actor/next"])</dsig:XPath> </dsig:Transform> <dsig:Transform Algorithm=3D"http://www.w3.org/TR/2001/REC-xml-c14n-20010= 315"/> </dsig:Transforms> <dsig:DigestMethod Algorithm=3D"http://www.w3.org/2000/09/xmldsig#sha1"/>= <dsig:DigestValue>NLzZ5KNIf1iTW8Fdkn0or/0wDJc=3D</dsig:DigestValue> </dsig:Reference> <dsig:Reference URI=3D"cid:0"> <dsig:DigestMethod Algorithm=3D"http://www.w3.org/2000/09/xmldsig#sha1"/>= <dsig:DigestValue>c+YUJufy39UnOTp/GeMKPmr5a0o=3D</dsig:DigestValue> </dsig:Reference> </dsig:SignedInfo> <dsig:SignatureValue> IuRNgCiyZH4/eifWi5sRehpjkZDfJUcyJTwiIF7NQslO29fMfDkZNRaHgHwStiSV1DTWOZbJb= C8E 6jcidx2L1AONUg1fjIHFd/IZ1JGuGentQpdVEfv5VhCEh/IUWYmBTMrky9qAPJ/hCorAv9kPJ= Y3A vnlKQm2rXH9OqklLJfI=3D </dsig:SignatureValue> <dsig:KeyInfo> <dsig:X509Data> <dsig:X509Certificate> MIICnjCCAgegAwIBAgIBAzANBgkqhkiG9w0BAQQFADB+MQswCQYDVQQGEwJISzESMBAGA1UEC= BMJ SG9uZyBLb25nMRIwEAYDVQQHEwlIb25nIEtvbmcxDjAMBgNVBAoTBUNFQ0lEMSQwIgYDVQQLE= xtU aGUgVW5pdmVyc2l0eSBvZiBIb25nIEtvbmcxETAPBgNVBAMTCENFQ0lEIENBMB4XDTAzMDkxO= TAz NDkxMVoXDTEzMDkxNjAzNDkxMVowgYkxCzAJBgNVBAYTAkhLMRIwEAYDVQQIEwlIb25nIEtvb= mcx EjAQBgNVBAcTCUhvbmcgS29uZzEOMAwGA1UEChMFQ0VDSUQxJDAiBgNVBAsTG1RoZSBVbml2Z= XJz aXR5IG9mIEhvbmcgS29uZzEcMBoGA1UEAxMTQ0VDSUQgWE1MIFNpZ25hdHVyZTCBnzANBgkqh= kiG 9w0BAQEFAAOBjQAwgYkCgYEAqPRszoyHH79W5rW3ZoIGomu21IAL5RYmxO86NJy+7oNlxQNt7= FlL lzs7R97NkTMbqcUWSUiPYR0OlsRQqf54YypKpLK8+eE4qHwG8Rhr4JnCw9XB5wNS8/aPPpW2m= kZz tJiPfUKekYi+IL9EuVsn3aA2+OvbeVYfToJ9BHBIptsCAwEAAaMgMB4wDAYDVR0TAQH/BAIwA= DAO BgNVHQ8BAf8EBAMCBsAwDQYJKoZIhvcNAQEEBQADgYEAsUgBEdnF5jZEidjslVEyXEbe58Kip= DAs /Gf4LWawieLuSWj9haqIj+VR3PdqUI8YpmW2XiM0xNf0Fy0K2oaAZKVOwtRSUlefxdj9YL1Pp= Hxk AZj6OgPo0AeTqdsmmUi9FgZclrmB0PrbLFN1fWDBElD0bzMv4hSOflatSdr5cTQ=3D </dsig:X509Certificate> </dsig:X509Data> <dsig:X509Data> <dsig:X509Certificate> MIIClTCCAf6gAwIBAgIBADANBgkqhkiG9w0BAQQFADB+MQswCQYDVQQGEwJISzESMBAGA1UEC= BMJ SG9uZyBLb25nMRIwEAYDVQQHEwlIb25nIEtvbmcxDjAMBgNVBAoTBUNFQ0lEMSQwIgYDVQQLE= xtU aGUgVW5pdmVyc2l0eSBvZiBIb25nIEtvbmcxETAPBgNVBAMTCENFQ0lEIENBMB4XDTAzMDkxO= TAz NDkwMloXDTEzMDkxNjAzNDkwMlowfjELMAkGA1UEBhMCSEsxEjAQBgNVBAgTCUhvbmcgS29uZ= zES MBAGA1UEBxMJSG9uZyBLb25nMQ4wDAYDVQQKEwVDRUNJRDEkMCIGA1UECxMbVGhlIFVuaXZlc= nNp dHkgb2YgSG9uZyBLb25nMREwDwYDVQQDEwhDRUNJRCBDQTCBnzANBgkqhkiG9w0BAQEFAAOBj= QAw gYkCgYEAtKg/Yh0mzTUAzmc9cbQilC2cToaIQiOp09DeGqhDjor8W0W6nzkTmbKHosPq0kGKL= 76J beM0TpKDkTzWYFW/d/p3Ru+b3AMo2DbJO5ETo5cMDrN7AaeQ/LWhzBgunAbpoN/bLI/npmCcD= p+1 np2SiOZGZRIMk/2QvkDSzCwP5b8CAwEAAaMjMCEwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BA= f8E BAMCAgQwDQYJKoZIhvcNAQEEBQADgYEAqXayWWHz8o9LIhX5kzQYrrm2JmSGTXoFG7Uy/+TtF= dNx ymXwrLDpENT9uxQd1SHvrYUshzc295HWMruHOBIufguDZVxdyY+Le49F/TMhW7w8UhANf170D= Tsd rd2tfBLaCJbYTTocoKhq1cYbCOeL8S96NfGZT23UDAgNPcKCWJ4=3D </dsig:X509Certificate> </dsig:X509Data> </dsig:KeyInfo> </dsig:Signature></soap-env:Header><soap-env:Body xsi:schemaLocation=3D"h= ttp://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd h= ttp://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/s= chema/msg-header-2_0.xsd" eb:version=3D"2.0"><eb:Reference eb:id=3D"0" xl= ink:type=3D"simple" xlink:href=3D"cid:0"><eb:Description xml:lang=3D"en-U= S">No description</eb:Description></eb:Reference></eb:Manifest></soap-env= :Body></soap-env:Envelope> ------=3D_BOUNDARY_01 Content-Type: application/octet-stream Content-Id: <0> Content-Transfer-Encoding: binary <?xml version=3D"1.0" encoding=3D"Shift_JIS"?> <!-- Test Payload --> <TestRoot> <TestElement> <Test1 test=3D"1"/> <Test2 test=3D"2"/> <Test3 test=3D"3"> <TestChild child=3D"child3"/> </Test3> <Test4 test=3D"4"/> </TestElement> </TestRoot> ------=3D_BOUNDARY_01-- |
|
From: Bob K. <py...@ce...> - 2003-10-02 02:39:57
|
I am investigating the problem. From the code, it seems that it is due to the problem on reading element assuming "ds" namespace in Signature constructor, and I need more time test it and fix it. Regards, Bob Koon Mayne, Peter wrote: > I'm getting a signed message delivered to my Hermes. Hermes is > accepting the message and passing it through to my listener servlet, > which does > > EbxmlMessage msg = new EbxmlMessage(headers, req.getInputStream()); > > to recreate the message. However, at this point I'm getting the exception > > hk.hku.cecid.phoenix.message.packaging.validation.SOAPValidationException: > Client: <ds:SignedInfo> is not found in <ds:Signature>! > > at > hk.hku.cecid.phoenix.message.packaging.Signature.<init>(Unknown Source) > at > hk.hku.cecid.phoenix.message.packaging.PKISignatureImpl.<init>(Unknown > Source) > at > hk.hku.cecid.phoenix.message.packaging.Signature.newInstance(Unknown > Source) > at > hk.hku.cecid.phoenix.message.packaging.HeaderContainer.<init>(Unknown > Source) > at > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage.<init>(Unknown > Source) > at > hk.hku.cecid.phoenix.message.packaging.EbxmlMessage.<init>(Unknown > Source) > at com.spherion.ap.in.Listener.doPost(Listener.java:284) > > The signature part of the message is: > > <dsig:Signature> > <dsig:SignedInfo> > <dsig:CanonicalizationMethod > Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></dsig:CanonicalizationMethod> > > <dsig:SignatureMethod > Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></dsig:SignatureMethod> > > <dsig:Reference URI=""> > <dsig:Transforms> > <dsig:Transform > Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></dsig:Transform> > > <dsig:Transform Algorithm="http://www.w3.org/TR/1999/REC-xpath-19991116"> > <dsig:XPath>not > (ancestor-or-self::node()[@SOAP-ENV:actor="urn:oasis:names:tc:ebxml-msg:service:nextMSH"] > | > ancestor-or-self::node()[@SOAP-ENV:actor="http://schemas.xmlsoap.org/soap/actor/next"])</dsig:XPath> > > </dsig:Transform> > <dsig:Transform > Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></dsig:Transform> > > </dsig:Transforms> > <dsig:DigestMethod > Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod> > <dsig:DigestValue>HygUBl6Mc++fHlZw7MrDnCMBXQg=</dsig:DigestValue> > </dsig:Reference> > <dsig:Reference > URI="cid:26819613.1064899362588.BusinessConnect@172.26.83.100"> > <dsig:DigestMethod > Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod> > <dsig:DigestValue>vABkj3oXJQW4KRGjezGuf5M25TQ=</dsig:DigestValue> > </dsig:Reference> > </dsig:SignedInfo> > <dsig:SignatureValue> > AivNERJ/IY+rahJH/nOiTZkhkNUI0WHVj/up7bEf4dPVPaPzZ42Ah19SH7ZpaWUAvuwZXCgMVQro > > V+huco+Yb9demjNRaQPdIuLObitQ0Gc0xGEPPu/QCRCoILDtyBKsMfYaEooniRjTEKxgH6/y8vh7 > > gqRf63oo1ShA38Eir7Q= > </dsig:SignatureValue> > </dsig:Signature> > > Note the "dsig:" namespace, rather than "ds:". I'm sure this was fixed > at one stage, but I can't remember if it was fixed generally in > Hermes, or I had to fix something in my own copy. > > How come this gets through the MSH, but it falls over when my listener > client attempts to rebuild the message? What do I have to do to make > it work? > > (Unsigned messages work perfectly, of course.) > > Thanks. > > PJDM > -- > Peter Mayne > Technology Consultant > Spherion Technology Solutions > Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 > T: 61 2 62689727 F: 61 2 62689777 > >The information contained in this email and any attachments to it: > >(a) may be confidential and if you are not the intended recipient, any interference with, >use, disclosure or copying of this material is unauthorised and prohibited; and > >(b) may contain personal information of the recipient and/or the sender as defined >under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to >collect, hold and use such information and any personal information contained in a >response to this email, for any reasonable purpose in the ordinary course of >Spherion's >business, including forwarding this email internally or disclosing it to a third party. All >personal information collected by Spherion will be handled in accordance with >Spherion's Privacy Policy. If you have received this email in error, please notify the >sender and delete it. > >(c) you agree not to employ or arrange employment for any candidate(s) supplied in >this email and any attachments without first entering into a contractual agreement with >Spherion. You further agree not to divulge any information contained in this document >to any person(s) or entities without the express permission of Spherion. > > > > |
|
From: Erik Y. <eri...@fe...> - 2003-09-16 09:00:37
|
10:30:15,185 INFO [STDOUT] Before sending: = http://212.75.69.148:4444/invoke/wm.ip.ebxml.MSH/receive 10:30:15,195 INFO [STDOUT] ------=3D_Part_3_31757016.1063701015185 Content-Type: text/xml Content-Transfer-Encoding: binary Content-Id: <soappart> <?xml version=3D"1.0" encoding=3D"UTF-8"?> <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.o rg/1999/xlink" = xsi:schemaLocation=3D"http://schemas.xmlsoap.org/soap/envelope/ = http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soap= -env:Heade r = xsi:schemaLocation=3D"http://www.oasis-open.org/committees/ebxml-msg/sche= ma/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-hea= der-2_0.xsd" eb:version=3D"2.0" soap-env:mustUnderstand=3D"1"><eb: From><eb:PartyId = eb:type=3D"DUNS">123456</eb:PartyId></eb:From><eb:To><eb:PartyId = eb:type=3D"DUNS">11-111-1111</eb:PartyId></eb:To><eb:CPAId>1234567890</eb= :CPAId><e b:ConversationId>erik_och_bea</eb:ConversationId><eb:Service>urn:com.ferr= ologic.os.ebxml.order</eb:Service><eb:Action>OrderResponse</eb:Action><eb= :MessageData>< eb:MessageId>20030916-082743146-1234567890.urn:com.ferrologic.os.ebxml.or= der.OrderResponse.1@212.75.69.157</eb:MessageId><eb:Timestamp>2003-09-16T= 08:27:43Z</eb: Timestamp></eb:MessageData></eb:MessageHeader></soap-env:Header><soap-env= :Body = xsi:schemaLocation=3D"http://www.oasis-open.org/committees/ebxml-msg/sche= ma/msg-hea der-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/sche ma/msg-header-2_0.xsd" eb:version=3D"2.0"><eb:Reference = eb:id=3D"contentId" xlink:type=3D"simple" = xlink:href=3D"cid:contentId"><eb:Description xml:lang=3D"en-US">descript ion</eb:Description></eb:Reference></eb:Manifest></soap-env:Body></soap-e= nv:Envelope> ------=3D_Part_3_31757016.1063701015185 Content-Type: text/xml Content-Transfer-Encoding: binary Content-Id: <contentId> <po/> ------=3D_Part_3_31757016.1063701015185-- 10:30:15,936 ERROR [STDERR] java.lang.NullPointerException 10:30:15,946 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:161) 10:30:15,956 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91) 10:30:15,956 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32) 10:30:15,966 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333) 10:30:15,976 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142) 10:30:15,986 ERROR [STDERR] at = java.security.AccessController.doPrivileged(Native Method) 10:30:15,986 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115) 10:30:15,996 ERROR [STDERR] at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source) 10:30:16,006 ERROR [STDERR] at = hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source) 10:30:16,006 ERROR [STDERR] javax.xml.soap.SOAPException: Unable to = internalize message 10:30:16,016 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) 10:30:16,026 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32) 10:30:16,026 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333) 10:30:16,036 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142) 10:30:16,046 ERROR [STDERR] at = java.security.AccessController.doPrivileged(Native Method) 10:30:16,046 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115) 10:30:16,056 ERROR [STDERR] at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source) 10:30:16,066 ERROR [STDERR] at = hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source) 10:30:16,066 ERROR [STDERR] Caused by: java.lang.NullPointerException 10:30:16,076 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:161) 10:30:16,086 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91) 10:30:16,096 ERROR [STDERR] ... 7 more 10:30:16,096 ERROR [STDERR] java.security.PrivilegedActionException: = javax.xml.soap.SOAPException: Unable to internalize message 10:30:16,106 ERROR [STDERR] at = java.security.AccessController.doPrivileged(Native Method) 10:30:16,116 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115) 10:30:16,116 ERROR [STDERR] at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source) 10:30:16,126 ERROR [STDERR] at = hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source) 10:30:16,136 ERROR [STDERR] Caused by: javax.xml.soap.SOAPException: = Unable to internalize message 10:30:16,136 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) 10:30:16,146 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32) 10:30:16,156 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333) 10:30:16,156 ERROR [STDERR] at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142) 10:30:16,166 ERROR [STDERR] ... 4 more 10:30:16,176 ERROR [STDERR] Caused by: java.lang.NullPointerException 10:30:16,176 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:161) 10:30:16,186 ERROR [STDERR] at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91) 10:30:16,196 ERROR [STDERR] ... 7 more |
|
From: Bob K. <py...@ce...> - 2003-09-16 03:54:02
|
I think the case is that receiver may not know whether the ack is received successful. The logic on reliable messaging is that if the receiver receive a message with ackRequested, he MUST send back the ack. to the sender. Whether the ack. will successfully deliver to the sender is unknown, but if the sender doesn't get the ack, it will resend the message again. Therefore, we cannot store whether the ack is successfully received by the sender in receiver side. The STATE_RECEIVED_ACKNOWLEDGED is used for state on a sent message which an ack. is received. Luoh Ren-Shan wrote: >Hi, > >We are tracing the source code of Hermes 0931. Our question is: > >What is the simplest way for the receiving party to know that >is a received message being acked (when AckRequested exists)? > > >It seems that the received message always stays at STATE_RECEIVED (-7) >no matter the ack is sent successfully or not. >Should it change to STATE_RECEIVED_ACKNOWLEDGED(-6) if success? > >Regards, >Luoh Ren-Shan >lu...@ii... > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >ebxmlms-develop mailing list >ebx...@li... >https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop > > > |
|
From: Luoh Ren-S. <lu...@ii...> - 2003-09-16 03:11:22
|
Hi, We are tracing the source code of Hermes 0931. Our question is: What is the simplest way for the receiving party to know that is a received message being acked (when AckRequested exists)? It seems that the received message always stays at STATE_RECEIVED (-7) no matter the ack is sent successfully or not. Should it change to STATE_RECEIVED_ACKNOWLEDGED(-6) if success? Regards, Luoh Ren-Shan lu...@ii... |
|
From: Gait B. <gai...@ti...> - 2003-09-11 10:47:44
|
MeddelandeHi Erik, AFAICT, there is no problem with the message you attached, at least not = with the xmlns:eb. The NS declaration is in scope for all items in the = eb namespace, which all reside within the eb:MessageHeader. What is the problem you experience here, do you get an error rerported = anywhere? Or is it simply different from what you were expecting? ----- Original Message -----=20 From: Erik Ytterman=20 To: ebx...@li...=20 Sent: Wednesday, September 10, 2003 3:13 PM Subject: [ebxmlms-develop] Pong namespace problem. Dear All! It seems like there is a problem with the Pong reply from HERMES MSH = 0.9.2. I believe that this problem originates from a missing ebXML namespace = declaraction in the SOAP envelope (<soap-env:Envelope>). Instead, this declaration = seem to end=20 up in the ebXML message header (<eb:MessageHeader>). Has anyone experienced the same problems? Are these problems related = to the used SAAJ/JAXM implementation! Does anyone know exactly where in the code(!) these namespace = declarations take place e.g are added to the SOAP envelope (<soap-env:Envelope>) and the = ebXML=20 message header (<eb:MessageHeader>). I also attach the message sent back from HERMES MSH. Hope that you = will be able to help me! =20 Best Regards /Erik Ytterman =20 |
|
From: Bob K. <py...@ce...> - 2003-09-11 02:35:34
|
Dear Erik, I think it is okay for the declaration of the eb namespace inside the message header itself, but anyway if you want to follow the code, please have a look on hk.hku.cecid.phoenix.message.packaging.HeaderContainer, which contains the code on namespace declaration. See if it can help. Regards, Bob Koon Erik Ytterman wrote: > Dear All! > > It seems like there is a problem with the Pong reply from HERMES MSH > 0.9.2. > I believe that this problem originates from a missing ebXML namespace > declaraction > in the SOAP envelope (<soap-env:Envelope>). Instead, this declaration > seem to end > up in the ebXML message header (<eb:MessageHeader>). > > Has anyone experienced the same problems? Are these problems related > to the > used SAAJ/JAXM implementation! > > Does anyone know exactly where in the code(!) these namespace > declarations take > place e.g are added to the SOAP envelope (<soap-env:Envelope>) and the > ebXML > message header (<eb:MessageHeader>). > > I also attach the message sent back from HERMES MSH. Hope that you will be > able to help me! > > Best Regards > /Erik Ytterman > > > >------------------------------------------------------------------------ > ><?xml version="1.0" encoding="UTF-8"?> ><soap-env:Envelope >xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ >http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"> ><soap-env:Header >xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd >http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"> ><eb:MessageHeader xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" >eb:version="2.0" soap-env:mustUnderstand="1"> ><eb:From> ><eb:PartyId eb:type="DUNS">123456</eb:PartyId> ></eb:From> ><eb:To> ><eb:PartyId eb:type="DUNS">11-111-1111</eb:PartyId> ></eb:To> ><eb:CPAId>ebMS-Ping-CPAId</eb:CPAId> ><eb:ConversationId>ebMS-Ping-ConversationId</eb:ConversationId> ><eb:Service>urn:oasis:names:tc:ebxml-msg:service</eb:Service> ><eb:Action>Pong</eb:Action> ><eb:MessageData> ><eb:MessageId>20030909-154139986-ebMS-Ping-CPAId.urn:oasis:names:tc:ebxml-msg:service.Pong.14@212.75.69.157</eb:MessageId> ><eb:Timestamp>2003-09-09T15:41:39Z</eb:Timestamp> ><eb:RefToMessageId>a4mhd100uu3g5qsv00000018</eb:RefToMessageId> ></eb:MessageData> ></eb:MessageHeader> ></soap-env:Header> ><soap-env:Body xsi:schemaLocation="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd >http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"/> ></soap-env:Envelope> > > |
|
From: Bob K. <py...@ce...> - 2003-09-11 02:23:38
|
Dear Daniel, Maybe I can explain why there are recent changes on Http.java. The main=20 reason behind this is that we are on hurry on the development for the=20 ebxml asia Interoperability Test. The test will cover SSL Server=20 Authentication, SSL Client Authentication and XML Digital Signature.=20 Therefore, your guessing is right that I will commit more codes related=20 to Http.java. (In fact I will commit the code for client authentication=20 within few days, maybe today) Thanks for the suggestion for the pluggable design on Http, and I also=20 think that it is good idea, but as I said, we are on hurry on the=20 development for the interoperability test (a very tight schedule), so I=20 think I will consider this changes in Hermes 1.0 design. Regards, Bob Koon Daniel Bergh wrote: >Hi, > >I noticed some changes in hk.hku.cecid.phoenix.message.transport.Http >regarding server authentication... I recently had to change this file my= self >with a few hacks in order to make it suite my environment. > >There is a lot of configuration that can be done on an outbound connecti= on >and I guess this class is going to be a hot spot for changes in the futu= re. >So why don't make the hole lot pluggable? The plugin could take an >ebxml-message and return an HttpURLConnection (the actual sending of the >message still being done in Http.java). This way the user could control: > >* The implementation of the http-protocol (The rather strange hack for >forcing which implementation to use in the beginning of send wouldn't be >needed) >* The plugin could use different setting (hostname verifiers, proxy >configuration etc.) for different trading partners, which would be very >useful. >* Resolving partner uri:s to URLs could be deferred to this point (a >separate plugin for that wouldn't be needed) >* The user doesn't have to rely on system properties to configure outbou= nd >connections. (System properties are great for stand alone applications, = but >not for application servers!) > >It also would be nice if there was a way of passing configuration >information to plugins. One suggestion is to give the plugins a method t= hat >takes an 'Element' from the xml in the configuration file... > >If you like the id=E9a and need a hand with the implementation I'd be gl= ad to >help you... > >regards > >Daniel > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >ebxmlms-develop mailing list >ebx...@li... >https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop > > > =20 > |
|
From: Daniel B. <Dan...@os...> - 2003-09-10 14:37:59
|
Hi, I noticed some changes in hk.hku.cecid.phoenix.message.transport.Http regarding server authentication... I recently had to change this file = myself with a few hacks in order to make it suite my environment. There is a lot of configuration that can be done on an outbound = connection and I guess this class is going to be a hot spot for changes in the = future. So why don't make the hole lot pluggable? The plugin could take an ebxml-message and return an HttpURLConnection (the actual sending of = the message still being done in Http.java). This way the user could = control: * The implementation of the http-protocol (The rather strange hack for forcing which implementation to use in the beginning of send wouldn't = be needed) * The plugin could use different setting (hostname verifiers, proxy configuration etc.) for different trading partners, which would be very useful. * Resolving partner uri:s to URLs could be deferred to this point (a separate plugin for that wouldn't be needed) * The user doesn't have to rely on system properties to configure = outbound connections. (System properties are great for stand alone applications, = but not for application servers!) It also would be nice if there was a way of passing configuration information to plugins. One suggestion is to give the plugins a method = that takes an 'Element' from the xml in the configuration file... If you like the id=E9a and need a hand with the implementation I'd be = glad to help you... regards Daniel |
|
From: Ladislav U. <Lad...@we...> - 2003-09-04 15:47:56
|
Dear Dorris and Hermes developers,
the new release of Webswell Connect includes Hermes MSH.
Webswell Connect 1.1 Beta constitutes open source integration framework
based on ebXML standards. It contains:
* EbXML Registry/Repository server and client. It uses ebxmlrr
implementation.
* EbXML Message Service Handler. This component is based on Hermes
Message Service Handler ebxmlms
* EbMail
Webswell Connect 1.1 Beta enables easy interactive installation and
configuration of all its parts. The installation package includes
pre-configured components (Tomcat, database, ebXML Registry and
Repository Server and Client,ebMail, Message Service Handler etc.), it
requires only java runtime environment installed.
Webswell Connect is temporarily available for Linux platform only.
You can download it at:
http://sourceforge.net/project/showfiles.php?group_id=79859&release_id=157081
Regards Ladislav
www.webswell.com
|
|
From: Ladislav U. <Lad...@we...> - 2003-09-04 15:34:41
|
Hello Patrick and ebMail developers,
the new release of Webswell Connect includes ebMail.
Webswell Connect 1.1 Beta constitutes business integration framework
based on ebXML standards. It contains:
* EbXML Registry/Repository server and client. It uses ebxmlrr
implementation.
* EbXML Message Service Handler. This component is based on Hermes
Message Service Handler ebxmlms
* EbMail
Webswell Connect 1.1 Beta enables easy interactive installation and
configuration of all its parts. The installation package includes
pre-configured components (Tomcat, database, ebXML Registry and
Repository Server and Client,ebMail, Message Service Handler etc.), it
requires only java runtime environment installed.
Webswell Connect is temporarily available for Linux platform only.
You can download it at:
http://sourceforge.net/project/showfiles.php?group_id=79859&release_id=157081
Regards Ladislav
www.webswell.com
|
|
From: Erik Y. <eri...@fe...> - 2003-09-02 11:16:30
|
Dear All! I'm currently evaluating HERMES MSH, and I'm quite new some of the configuration parts of ebXML. I wonder if anyone has any HERMES client code that sends an ebXML Ping to a certain URL. If so, i would be realy happy to see it! BR /Erik Ytterman User ID: 853135 User Name: eytterman |
|
From: Erik Y. <eri...@fe...> - 2003-09-02 09:04:09
|
This is a test. |
|
From: Erik Y. <eri...@fe...> - 2003-09-02 08:57:16
|
This is a subscription test. |
|
From: Ng C. Y. <cy...@cs...> - 2003-08-27 02:00:19
|
Hi,
> Tomcat is up to 4.1.27. I'll find some time to give it a try.
> Why did you switch to Jetty?
I switch to Jetty as well for more than several months. I love it.
Its performance is much much better than Tomcat. Startup time < 1s in the
Pentium III 700 server. (Jetty runs in my mini-sub-laptop very fast as
well.) No need to patch those common/lib/*.jar as in Tomcat. Jetty seems to
support something like embedded web server mode, i.e., you can new a
org.xxxxx.jetty something in your code.
Regards,
CY
----------------------------------------------------------------------------
Ng Chi Yuen, CY. cy...@ce... http://www.cecid.hku.hk/
Technology Officer,
Centre for E-Commerce Infrastructure Development,
The University of Hong Kong
----------------------------------------------------------------------------
|
|
From: Patrick Y. <kc...@ce...> - 2003-08-26 07:40:26
|
<!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"> I did. However, it was quite a long time ago.. and I switched to Jetty. :-)<br> The last version I used is 4.0.6 full version. To use it, you may need to patch the xalan.jar in tomcat/common/lib.<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>Hermes in non-LE Tomcat</title> <p><font size="2">Has anyone tried using Hermes in a non LE version of Tomcat?</font> </p> <p><font size="2">The members of the Tomcat mailing list are rather disparaging about the LE version, and I'm doing other stuff that will run in the full version, and it seems strange to have two versions of Tomcat lying around.</font></p> <p><font size="2">Thanks.</font> </p> <p><font size="2">PJDM</font> <br> <font size="2">-- </font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p> <font size="3" color="BLUE"> <pre>The information contained in this email and any attachments to it: (a) may be confidential and if you are not the intended recipient, any interference with, use, disclosure or copying of this material is unauthorised and prohibited; and (b) may contain personal information of the recipient and/or the sender as defined under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to collect, hold and use such information and any personal information contained in a response to this email, for any reasonable purpose in the ordinary course of Spherion's business, including forwarding this email internally or disclosing it to a third party. All personal information collected by Spherion will be handled in accordance with Spherion's Privacy Policy. If you have received this email in error, please notify the sender and delete it. (c) you agree not to employ or arrange employment for any candidate(s) supplied in this email and any attachments without first entering into a contractual agreement with Spherion. You further agree not to divulge any information contained in this document to any person(s) or entities without the express permission of Spherion. </pre> </font></blockquote> </body> </html> |
|
From: Bob K. <py...@ce...> - 2003-08-15 08:12:08
|
Dear Daniel,
Thanks for the information. I have fixed the bug (probably using the
code you suggested, and with some additional updates on other parts) and
committed to the CVS on ebxmlms. If you like, you can check it out using
CVS to have a test on it.
Regards,
Bob Koon
Daniel Bergh wrote:
>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
>
|
|
From: Rao Y. <ra...@ya...> - 2003-08-15 00:36:48
|
Thanks to the help of people on this list, now the document sent from Hermes reaches JWSDP on the other box. I could see the document in the archive. Now when JWSDP is trying to dispatch the document to the appropriate handler , it is throwing a NullPointer Exception . Basically it is failing at the point where it is trying to retreive the "To" PartyId to dispatch to the corresponding URL. Any ideas ??? -Venkat --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software |
|
From: Rao Y. <ra...@ya...> - 2003-08-12 15:02:32
|
Thanks to Bob Koon and CY. Now the request is reaching our in-house MSH. I could see the document archived in toBeDispatched directory of JWSDP. But when trying to reconstruct the document for dispatching , it is throwing NullPointer Exceptions. It is unable to find out the To Party. I downloaded the source code of JAXM & SAAJ and i am trying to figure out the problem. -Venkat ebx...@li... wrote: Send ebxmlms-develop mailing list submissions to ebx...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop or, via email, send a message with subject or body 'help' to ebx...@li... You can reach the person managing the list at ebx...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of ebxmlms-develop digest..." Today's Topics: 1. Re: Re: Hermes interoperate with jwsdp 1.0.1 (Bob Koon) 2. Re: Re: Hermes interoperate with jwsdp 1.0.1 (Bob Koon) --__--__-- Message: 1 Date: Mon, 11 Aug 2003 10:28:53 +0800 From: Bob Koon To: ebx...@li... Subject: Re: [ebxmlms-develop] Re: Hermes interoperate with jwsdp 1.0.1 Reply-To: ebx...@li... --------------040404040908090703030703 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 > - > Free, easy-to-use web site design software --------------040404040908090703030703 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit 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 - Free, easy-to-use web site design software --------------040404040908090703030703-- --__--__-- Message: 2 Date: Mon, 11 Aug 2003 10:33:52 +0800 From: Bob Koon To: ebx...@li... Subject: Re: [ebxmlms-develop] Re: Hermes interoperate with jwsdp 1.0.1 Reply-To: ebx...@li... --------------080109070105000800060004 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 >> - >> Free, easy-to-use web site design software > > --------------080109070105000800060004 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit 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 - Free, easy-to-use web site design software --------------080109070105000800060004-- --__--__-- _______________________________________________ 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 |
1574 messages has been excluded from this view by a project administrator.
