Menu
▾
▴
ebxmlms-general — General discussions
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(20) |
Nov
(11) |
Dec
(27) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(11) |
Feb
(8) |
Mar
(17) |
Apr
(11) |
May
(9) |
Jun
(30) |
Jul
(18) |
Aug
|
Sep
(4) |
Oct
(34) |
Nov
(83) |
Dec
(28) |
| 2004 |
Jan
(4) |
Feb
|
Mar
(13) |
Apr
(20) |
May
(4) |
Jun
(26) |
Jul
(5) |
Aug
(2) |
Sep
(3) |
Oct
(7) |
Nov
(10) |
Dec
(24) |
| 2005 |
Jan
(7) |
Feb
(44) |
Mar
(9) |
Apr
(16) |
May
(9) |
Jun
(64) |
Jul
(48) |
Aug
(36) |
Sep
(27) |
Oct
(24) |
Nov
(20) |
Dec
(11) |
| 2006 |
Jan
(12) |
Feb
(13) |
Mar
(7) |
Apr
|
May
(16) |
Jun
(5) |
Jul
(2) |
Aug
(7) |
Sep
(19) |
Oct
(5) |
Nov
(9) |
Dec
(13) |
| 2007 |
Jan
(21) |
Feb
(12) |
Mar
(6) |
Apr
|
May
(2) |
Jun
(14) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
(5) |
May
(2) |
Jun
(1) |
Jul
(6) |
Aug
|
Sep
(9) |
Oct
(3) |
Nov
(25) |
Dec
(32) |
| 2009 |
Jan
(11) |
Feb
(12) |
Mar
(18) |
Apr
(19) |
May
(31) |
Jun
(23) |
Jul
(35) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
|
Dec
(8) |
| 2010 |
Jan
(3) |
Feb
(3) |
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Patrick Y. <kc...@ce...> - 2003-11-17 16:20:18
|
Mark,
We suspect of 2 possible causes:
1. there may be a mismatch of mail.jar and activation.jar. Are you using =
your own version of these jar files?=20
2. are you using SMTP authentication while your mail servers doesn't =
support?
Please check. Thanks.
Regards, -Patrick
----- Original Message -----=20
From: MTM Zenhorst=20
To: ebx...@li...=20
Sent: Monday, November 17, 2003 8:19 PM
Subject: Re: [ebxmlms-general] error 10102 Cannot Compose Mail Message
Hello,=20
I changed the from party ID but now I get another error that leaves me =
wondering.=20
parameters:=20
from partyId: mailto:de...@19....20=20
type: Mail=20
to partyId: mailto:ma...@19....20=20
type: MAIL=20
the errors given in the msh logfile are:=20
thread: sending message to ma...@19....20 through =
192.168.xxx.20=20
error: 10103 Cannot send mail message=20
exception: javax.mail.NoSuchProviderException=20
message: smtp=20
exception: =
hk.hku.cecid.phoenix.message.transport.TransportException=20
message: 10103 Cannot send mail message=20
We also tried with company mail addresses and hotmail mail addresses =
but they gave the same errors.=20
The log file of the mail server does not show the msh is trying to =
send the mail it is only polling in te pool for new messages.=20
do you have any idea as for what is going wrong?=20
=20
Patrick Yee wrote:=20
Mark,Sorry, under the current limitation of Hermes, when you send =
out message using SMTP protocol, the From Party ID of the message should =
be a valid email address also.Regards, -Patrick =20
----- Original Message -----
From: MTM Zenhorst
To: ebx...@li...
Sent: Friday, November 14, 2003 10:36 PM
Subject: [ebxmlms-general] error 10102 Cannot Compose Mail Message
Hello,=20
We are trying to install a alocal working ebXML setup but we have=20
encountered a problem. We hope you are able to help us.=20
When we send a message from a msh_client to the MSH server the =
error=20
occurs.=20
The message is sent with the following information.=20
from partyId: http://192.168.xxx.20:8080/msh=20
type: HTTP=20
to partyId: mailto:ma...@19....20=20
type: MAIL=20
the message is sent and it arrives at the MSH server. At that =
point I=20
think the actual error occurs.=20
The log file shows:=20
sending message to ma...@19....20 through 192.168.xxx.20=20
then it tells me a 10102 error Cannot Compose Mail Message occurs. =
the given exception is:=20
javax.mail.internet.AddressException=20
message: Nested Group=20
after trying to resend 2 times the client receives an error =
message:=20
errorCode=3D"Delivery Failure" severity=3D"Error"=20
description=3D"Communication error".=20
which is logical offcourse :)=20
Can you tell me if the email address format is not supported or if =
we=20
are doing something wrong?=20
Greetz,=20
Mark Zenhorst=20
=20
=20
-------------------------------------------------------=20
This SF.Net email sponsored by: ApacheCon 2003,=20
16-19 November in Las Vegas. Learn firsthand the latest=20
developments in Apache, PHP, Perl, XML, Java, MySQL,=20
WebDAV, and more! http://www.apachecon.com/=20
_______________________________________________=20
ebxmlms-general mailing list=20
ebx...@li...=20
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
|
|
From: Patrick Y. <kc...@ce...> - 2003-11-17 16:07:52
|
Christophe, But this seems only showing the traffic from outgoing message. What has = TCPMon captured in the incoming message? And can you please send to us = the msh.log file? Regards, -Patrick ----- Original Message -----=20 From: Larchier Christophe=20 To: ebx...@li...=20 Sent: Monday, November 17, 2003 11:04 PM Subject: RE: [ebxmlms-general] Digital signature Patrick, Finaly, I succeed to use TCPMon in listener mode. Here is the http message : OST / HTTP/1.1 Content-Type: multipart/related; type=3D"text/xml"; = boundary=3D"----=3D_Part_29_17303670.1069076816312"; charset=3D"utf-8"; = start=3D"<soappart>" SOAPAction: ebXML Content-Length: 4463 User-Agent: Java/1.4.1_03 Host: localhost Accept: text/html, image/gif, image/jpeg, *; q=3D.2, */*; q=3D.2 Connection: keep-alive ------=3D_Part_29_17303670.1069076816312 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.org/1999/xlink" = xsi:schemaLocation=3D"http://schemas.xmlsoap.org/soap/envelope/ = http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soap= -env:Header = 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>http://localhost:8080/= msh</eb:PartyId></eb:From><eb:To><eb:PartyId>http://localhost:8282</eb:Pa= rtyId></eb:To><eb:CPAId>CPA_2002</eb:CPAId><eb:ConversationId>Item_No_128= </eb:ConversationId><eb:Service>http://www.cecid.hku.hk/ebxml/service</eb= :Service><eb:Action>Order</eb:Action><eb:MessageData><eb:MessageId>200311= 17-134652218-CPA_2002.http://www.cecid.hku.hk/ebxml/service.Order.6@172.1= 6.161.154</eb:MessageId><eb:Timestamp>2003-11-17T13:46:52Z</eb:Timestamp>= </eb:MessageData></eb:MessageHeader><ds:Signature = xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod = Algorithm=3D"http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:Canoni= calizationMethod> <ds:SignatureMethod = Algorithm=3D"http://www.w3.org/2000/09/xmldsig#dsa-sha1"></ds:SignatureMe= thod> <ds:Reference URI=3D""> <ds:Transforms> <ds:Transform = Algorithm=3D"http://www.w3.org/2000/09/xmldsig#enveloped-signature"></ds:= Transform> <ds:Transform = Algorithm=3D"http://www.w3.org/TR/1999/REC-xpath-19991116"> = <ds:XPath>not(ancestor-or-self::node()[@soap-env:actor=3D"urn:oasis:names= :tc:ebxml-msg:actor:nextMSH"] | = ancestor-or-self::node()[@soap-env:actor=3D"http://schemas.xmlsoap.org/so= ap/actor/next"])</ds:XPath> </ds:Transform> <ds:Transform = Algorithm=3D"http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:Transf= orm> </ds:Transforms> <ds:DigestMethod = Algorithm=3D"http://www.w3.org/2000/09/xmldsig#sha1"></ds:DigestMethod> <ds:DigestValue>FnX6dxx6xVfzEUKWeplzmlf6sms=3D</ds:DigestValue> </ds:Reference> <ds:Reference URI=3D"cid:Payload-0"> <ds:DigestMethod = Algorithm=3D"http://www.w3.org/2000/09/xmldsig#sha1"></ds:DigestMethod> <ds:DigestValue>rXe6R+MQUXLN+9rnsG9JA30sElE=3D</ds:DigestValue> </ds:Reference> </ds:SignedInfo> = <ds:SignatureValue>kg9+FDNhq4qADjPOd7v1YXGo0vZrv7lPASvW71c3UvagAyaHV3V4Zg= =3D=3D</ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate> = MIIDJTCCAuICBD+x8fAwCwYHKoZIzjgEAwUAMHgxCzAJBgNVBAYTAkZSMRUwEwYDVQQIEwxIY= XV0 = ZS1TYXZvaWUxGDAWBgNVBAcTD0FubmVjeSBsZSBWaWV1eDETMBEGA1UEChMKU29wcmFHcm91c= DEO = MAwGA1UECxMFQXh3YXkxEzARBgNVBAMTCkNocmlzdG9waGUwHhcNMDMxMTEyMDg0MDE2WhcNM= DQw = MjEwMDg0MDE2WjB4MQswCQYDVQQGEwJGUjEVMBMGA1UECBMMSGF1dGUtU2F2b2llMRgwFgYDV= QQH = Ew9Bbm5lY3kgbGUgVmlldXgxEzARBgNVBAoTClNvcHJhR3JvdXAxDjAMBgNVBAsTBUF4d2F5M= RMw = EQYDVQQDEwpDaHJpc3RvcGhlMIIBtzCCASwGByqGSM44BAEwggEfAoGBAP1/U4EddRIpUt9Kn= C7s = 5Of2EbdSPO9EAMMeP4C2USZpRV1AIlH7WT2NWPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClp= J+f = 6AR7ECLCT7up1/63xhv4O1fnxqimFQ8E+4P208UewwI1VBNaFpEy9nXzrith1yrv8iIDGZ3RS= AHH = AhUAl2BQjxUjC8yykrmCouuEC/BYHPUCgYEA9+GghdabPd7LvKtcNrhXuXmUr7v6OuqC+VdMC= z0H = gmdRWVeOutRZT+ZxBxCBgLRJFnEj6EwoFhO3zwkyjMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C= /oh = NWLx+2J6ASQ7zKTxvqhRkImog9/hWuWfBpKLZl6Ae1UlZAFMO/7PSSoDgYQAAoGACgp0fZI2/= fLj = FAswnTiG4y3optT510AKXXqiqOX46zbT1VTsLmpPXUjR68SW6J0GllTLlPwGNVC6Fxylu9Md7= /z2 = LZ6krAHQEsS39jnQqY1G+mSTHl6B+gkxpLPjm3kW/49k/4kjFSbcypnmdzruqs/tn5rV4CQgV= Z8/ = ZeE+qj0wCwYHKoZIzjgEAwUAAzAAMC0CFQCByj7heG8HJjn+OUfYaPOAVhR7RQIUVNJVbo+W4= NwP RPGXWo56VMCUe4g=3D </ds:X509Certificate> </ds:X509Data> </ds:KeyInfo> </ds:Signature></soap-env:Header><soap-env:Body = 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:Manifest = xmlns:eb=3D"http://www.oasis-open.org/committees/ebxml-msg/schema/msg-hea= der-2_0.xsd" eb:version=3D"2.0"><eb:Reference eb:id=3D"Payload-0" = xlink:type=3D"simple" = xlink:href=3D"cid:Payload-0"/></eb:Manifest></soap-env:Body></soap-env:En= velope> ------=3D_Part_29_17303670.1069076816312 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-Id: <Payload-0> <po/> ------=3D_Part_29_17303670.1069076816312-- For me, it seems to be good. Do you see something anormal? Christophe -----Message d'origine----- De : ebx...@li... = [mailto:ebx...@li...]De la part de = Patrick Yee Envoy=E9 : samedi 15 novembre 2003 15:19 =C0 : ebx...@li... Objet : Re: [ebxmlms-general] Digital signature Christophe, So you have send out the message twice using Monitor, once without = using digital signature, once with digital signature, right? Are you = using exactly the same parameters in Monitor, with only the digital = signature check box in the latter case? If the answer is yes, we have still no clue about what's happening = in your case. To further investigate, you can try to grab a very useful = tool called TCPMon from Apache AXIS project. This tool should be = installed between your Monitor and the MSH server, and it can help you = to capture all the HTTP level traffic between Monitor and MSH server, = and then forward the captured traffic out as a proxy.=20 It will be useful to capture the text/plain message to see the = cause. Regards, -Patrick ----- Original Message -----=20 From: Larchier Christophe=20 To: ebx...@li...=20 Sent: Friday, November 14, 2003 3:31 PM Subject: RE: [ebxmlms-general] Digital signature It's a loopback test. Note that the loopback test without digital signature works fine. Christophe -----Message d'origine----- De : ebx...@li... = [mailto:ebx...@li...]De la part de = Patrick Yee Envoy=E9 : jeudi 13 novembre 2003 11:32 =C0 : ebx...@li... Objet : Re: [ebxmlms-general] Digital signature Larchier, Where did you send the message to? It seems that the target end = sent back a message that is not comprehensible by Hermes. Regards, -Patrick Larchier Christophe wrote: Hi all,=20 With the MSH monitor, when I send a message with digital = signature, I get the following message in the Tomcat console :=20 javax.xml.soap.SOAPException: Invalid Content-Type:text/plain=20 at = com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) = at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20 at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142)=20 at java.security.AccessController.doPrivileged(Native = Method)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115)=20 at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20 at = hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)=20 javax.xml.soap.SOAPException: Unable to internalize message=20 at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) = at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142)=20 at java.security.AccessController.doPrivileged(Native = Method)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115)=20 at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20 at = hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)=20 Caused by: javax.xml.soap.SOAPException: Invalid = Content-Type:text/plain=20 at = com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) = at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20 ... 7 more=20 java.security.PrivilegedActionException: = javax.xml.soap.SOAPException: Unable to internalize message=20 at java.security.AccessController.doPrivileged(Native = Method)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115)=20 at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20 at = hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)=20 Caused by: javax.xml.soap.SOAPException: Unable to internalize = message=20 at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) = at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142)=20 ... 4 more=20 After few minutes, I receive an error message : "Delivery = failure".=20 Thanks for your help.=20 ______________________________________=20 Christophe Larchier=20 Axway.=20 a Sopra Group company.=20 3, rue de Pr=E9 Faucon=20 PAE - Les Glaisins - BP238=20 F-74942 Annecy-le-Vieux Cedex=20 ( +33 (0)4 50 33 31 55=20 ______________________________________=20 ------------------------------------------------------- This = SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. = Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, = MySQL, WebDAV, and more! http://www.apachecon.com/ = _______________________________________________ ebxmlms-general mailing = list ebx...@li... = https://lists.sourceforge.net/lists/listinfo/ebxmlms-general |
|
From: Larchier C. <cla...@ax...> - 2003-11-17 15:54:42
|
Patrick, =20 Finaly, I succeed to use TCPMon in listener mode. Here is the http message : =20 OST / HTTP/1.1 =20 Content-Type: multipart/related; type=3D"text/xml"; = boundary=3D"----=3D_Part_29_17303670.1069076816312"; charset=3D"utf-8"; = start=3D"<soappart>" =20 SOAPAction: ebXML =20 Content-Length: 4463 =20 User-Agent: Java/1.4.1_03 =20 Host: localhost =20 Accept: text/html, image/gif, image/jpeg, *; q=3D.2, */*; q=3D.2 =20 Connection: keep-alive =20 =20 =20 ------=3D_Part_29_17303670.1069076816312 =20 Content-Type: text/xml =20 Content-Transfer-Encoding: binary =20 Content-Id: <soappart> =20 =20 =20 <?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.org/1999/xlink" xsi:schemaLocation=3D" = http://schemas.xmlsoap.org/soap/envelope/ = <http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd> = http://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soap= -env:Header xsi:schemaLocation=3D" = 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= > = 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-header-2_0.xsd"= eb:version=3D"2.0" = soap-env:mustUnderstand=3D"1"><eb:From><eb:PartyId>http://localhost:8080/= msh</eb:PartyId></eb:From><eb:To><eb:PartyId>http://localhost:8282</eb:Pa= rtyId></eb:To><eb:CPAId>CPA_2002</eb:CPAId><eb:ConversationId>Item_No_128= </eb:ConversationId><eb:Service>http://www.cecid.hku.hk/ebxml/service</eb= :Service><eb:Action>Order</eb:Action><eb:MessageData><eb:MessageId>200311= 17-134652218-CPA_2002.http://www.cecid.hku.hk/ebxml/service.Order.6@172.1= 6.161.154</eb:MessageId><eb:Timestamp>2003-11-17T13:46:52Z</eb:Timestamp>= </eb:MessageData></eb:MessageHeader><ds:Signature xmlns:ds=3D" = http://www.w3.org/2000/09/xmldsig#"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm=3D" = <http://www.w3.org/TR/2001/REC-xml-c14n-20010315> = http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:CanonicalizationMet= hod> <ds:SignatureMethod Algorithm=3D" = <http://www.w3.org/2000/09/xmldsig#dsa-sha1> = http://www.w3.org/2000/09/xmldsig#dsa-sha1"></ds:SignatureMethod> <ds:Reference URI=3D""> <ds:Transforms> <ds:Transform Algorithm=3D" = <http://www.w3.org/2000/09/xmldsig#enveloped-signature> = http://www.w3.org/2000/09/xmldsig#enveloped-signature"></ds:Transform> <ds:Transform Algorithm=3D" = http://www.w3.org/TR/1999/REC-xpath-19991116"> <ds:XPath>not(ancestor-or-self::node()[@soap-env:actor=3D"urn:oasis:names= :tc:ebxml-msg:actor:nextMSH"] | = ancestor-or-self::node()[@soap-env:actor=3D" = <http://schemas.xmlsoap.org/soap/actor/next> = http://schemas.xmlsoap.org/soap/actor/next"])</ds:XPath> </ds:Transform> <ds:Transform Algorithm=3D" = <http://www.w3.org/TR/2001/REC-xml-c14n-20010315> = http://www.w3.org/TR/2001/REC-xml-c14n-20010315"></ds:Transform> </ds:Transforms> <ds:DigestMethod Algorithm=3D" <http://www.w3.org/2000/09/xmldsig#sha1> = http://www.w3.org/2000/09/xmldsig#sha1"></ds:DigestMethod> <ds:DigestValue>FnX6dxx6xVfzEUKWeplzmlf6sms=3D</ds:DigestValue> </ds:Reference> <ds:Reference URI=3D"cid:Payload-0"> <ds:DigestMethod Algorithm=3D" <http://www.w3.org/2000/09/xmldsig#sha1> = http://www.w3.org/2000/09/xmldsig#sha1"></ds:DigestMethod> <ds:DigestValue>rXe6R+MQUXLN+9rnsG9JA30sElE=3D</ds:DigestValue> </ds:Reference> </ds:SignedInfo> <ds:SignatureValue>kg9+FDNhq4qADjPOd7v1YXGo0vZrv7lPASvW71c3UvagAyaHV3V4Zg= =3D=3D</ds:SignatureValue> <ds:KeyInfo> <ds:X509Data> <ds:X509Certificate> MIIDJTCCAuICBD+x8fAwCwYHKoZIzjgEAwUAMHgxCzAJBgNVBAYTAkZSMRUwEwYDVQQIEwxIY= XV0 ZS1TYXZvaWUxGDAWBgNVBAcTD0FubmVjeSBsZSBWaWV1eDETMBEGA1UEChMKU29wcmFHcm91c= DEO MAwGA1UECxMFQXh3YXkxEzARBgNVBAMTCkNocmlzdG9waGUwHhcNMDMxMTEyMDg0MDE2WhcNM= DQw MjEwMDg0MDE2WjB4MQswCQYDVQQGEwJGUjEVMBMGA1UECBMMSGF1dGUtU2F2b2llMRgwFgYDV= QQH Ew9Bbm5lY3kgbGUgVmlldXgxEzARBgNVBAoTClNvcHJhR3JvdXAxDjAMBgNVBAsTBUF4d2F5M= RMw EQYDVQQDEwpDaHJpc3RvcGhlMIIBtzCCASwGByqGSM44BAEwggEfAoGBAP1/U4EddRIpUt9Kn= C7s 5Of2EbdSPO9EAMMeP4C2USZpRV1AIlH7WT2NWPq/xfW6MPbLm1Vs14E7gB00b/JmYLdrmVClp= J+f 6AR7ECLCT7up1/63xhv4O1fnxqimFQ8E+4P208UewwI1VBNaFpEy9nXzrith1yrv8iIDGZ3RS= AHH AhUAl2BQjxUjC8yykrmCouuEC/BYHPUCgYEA9+GghdabPd7LvKtcNrhXuXmUr7v6OuqC+VdMC= z0H gmdRWVeOutRZT+ZxBxCBgLRJFnEj6EwoFhO3zwkyjMim4TwWeotUfI0o4KOuHiuzpnWRbqN/C= /oh NWLx+2J6ASQ7zKTxvqhRkImog9/hWuWfBpKLZl6Ae1UlZAFMO/7PSSoDgYQAAoGACgp0fZI2/= fLj FAswnTiG4y3optT510AKXXqiqOX46zbT1VTsLmpPXUjR68SW6J0GllTLlPwGNVC6Fxylu9Md7= /z2 LZ6krAHQEsS39jnQqY1G+mSTHl6B+gkxpLPjm3kW/49k/4kjFSbcypnmdzruqs/tn5rV4CQgV= Z8/ ZeE+qj0wCwYHKoZIzjgEAwUAAzAAMC0CFQCByj7heG8HJjn+OUfYaPOAVhR7RQIUVNJVbo+W4= NwP RPGXWo56VMCUe4g=3D </ds:X509Certificate> </ds:X509Data> </ds:KeyInfo> </ds:Signature></soap-env:Header><soap-env:Body xsi:schemaLocation=3D" = 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= > = 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-header-2_0.xsd"= eb:version=3D"2.0"><eb:Reference eb:id=3D"Payload-0" = xlink:type=3D"simple" = xlink:href=3D"cid:Payload-0"/></eb:Manifest></soap-env:Body></soap-env:En= velope> =20 ------=3D_Part_29_17303670.1069076816312 =20 Content-Type: application/octet-stream =20 Content-Transfer-Encoding: binary =20 Content-Id: <Payload-0> =20 =20 =20 <po/> =20 ------=3D_Part_29_17303670.1069076816312-- =20 =20 =20 =20 For me, it seems to be good. Do you see something anormal? =20 Christophe =20 -----Message d'origine----- De : ebx...@li... = [mailto:ebx...@li...]De la part de = Patrick Yee Envoy=E9 : samedi 15 novembre 2003 15:19 =C0 : ebx...@li... Objet : Re: [ebxmlms-general] Digital signature Christophe, =20 So you have send out the message twice using Monitor, once without using = digital signature, once with digital signature, right? Are you using = exactly the same parameters in Monitor, with only the digital signature = check box in the latter case? =20 If the answer is yes, we have still no clue about what's happening in = your case. To further investigate, you can try to grab a very useful = tool called TCPMon from Apache AXIS project. This tool should be = installed between your Monitor and the MSH server, and it can help you = to capture all the HTTP level traffic between Monitor and MSH server, = and then forward the captured traffic out as a proxy.=20 =20 It will be useful to capture the text/plain message to see the cause. =20 Regards, -Patrick =20 ----- Original Message -----=20 From: Larchier <mailto:cla...@ax...> Christophe=20 To: ebx...@li...=20 Sent: Friday, November 14, 2003 3:31 PM Subject: RE: [ebxmlms-general] Digital signature It's a loopback test. Note that the loopback test without digital signature works fine. =20 Christophe -----Message d'origine----- De : ebx...@li... = [mailto:ebx...@li...]De la part de = Patrick Yee Envoy=E9 : jeudi 13 novembre 2003 11:32 =C0 : ebx...@li... Objet : Re: [ebxmlms-general] Digital signature Larchier, Where did you send the message to? It seems that the target end sent = back a message that is not comprehensible by Hermes. Regards, -Patrick Larchier Christophe wrote: Hi all,=20 With the MSH monitor, when I send a message with digital signature, I = get the following message in the Tomcat console :=20 javax.xml.soap.SOAPException: Invalid Content-Type:text/plain=20 at = com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) = at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20 at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142)=20 at java.security.AccessController.doPrivileged(Native Method)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115)=20 at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20 at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown = Source)=20 javax.xml.soap.SOAPException: Unable to internalize message=20 at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) = at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142)=20 at java.security.AccessController.doPrivileged(Native Method)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115)=20 at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20 at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown = Source)=20 Caused by: javax.xml.soap.SOAPException: Invalid Content-Type:text/plain = at = com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) = at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20 ... 7 more=20 java.security.PrivilegedActionException: javax.xml.soap.SOAPException: = Unable to internalize message=20 at java.security.AccessController.doPrivileged(Native Method)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon= nection.java:115)=20 at = hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20 at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown = Source)=20 Caused by: javax.xml.soap.SOAPException: Unable to internalize message=20 at = com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) = at = com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF= actoryImpl.java:32)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon= nection.java:333)=20 at = com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.= run(HttpSOAPConnection.java:142)=20 ... 4 more=20 After few minutes, I receive an error message : "Delivery failure".=20 Thanks for your help.=20 ______________________________________=20 Christophe Larchier=20 Axway.=20 a Sopra Group company.=20 3, rue de Pr=E9 Faucon=20 PAE - Les Glaisins - BP238=20 F-74942 Annecy-le-Vieux Cedex=20 * +33 (0)4 50 33 31 55=20 ______________________________________=20 ------------------------------------------------------- This SF.Net = email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn = firsthand the latest developments in Apache, PHP, Perl, XML, Java, = MySQL, WebDAV, and more! http://www.apachecon.com/ = _______________________________________________ ebxmlms-general mailing = list ebx...@li... = https://lists.sourceforge.net/lists/listinfo/ebxmlms-general=20 |
|
From: MTM Z. <zen...@fe...> - 2003-11-17 12:20:49
|
Hello, I changed the from party ID but now I get another error that leaves me wondering. parameters: from partyId: mailto:de...@19....20 type: Mail to partyId: mailto:ma...@19....20 type: MAIL the errors given in the msh logfile are: thread: sending message to ma...@19....20 through 192.168.xxx.20 error: 10103 Cannot send mail message exception: javax.mail.NoSuchProviderException message: smtp exception: hk.hku.cecid.phoenix.message.transport.TransportException message: 10103 Cannot send mail message We also tried with company mail addresses and hotmail mail addresses but they gave the same errors. The log file of the mail server does not show the msh is trying to send the mail it is only polling in te pool for new messages. do you have any idea as for what is going wrong? Patrick Yee wrote: > Mark,Sorry, under the current limitation of Hermes, when you send out > message using SMTP protocol, the From Party ID of the message should > be a valid email address also.Regards, -Patrick > > ----- Original Message ----- > From: MTM Zenhorst > To: ebx...@li... > Sent: Friday, November 14, 2003 10:36 PM > Subject: [ebxmlms-general] error 10102 Cannot Compose Mail > Message > Hello, > > We are trying to install a alocal working ebXML setup but we > have > encountered a problem. We hope you are able to help us. > > When we send a message from a msh_client to the MSH server > the error > occurs. > The message is sent with the following information. > from partyId: http://192.168.xxx.20:8080/msh > type: HTTP > to partyId: mailto:ma...@19....20 > type: MAIL > > the message is sent and it arrives at the MSH server. At > that point I > think the actual error occurs. > > The log file shows: > sending message to ma...@19....20 through > 192.168.xxx.20 > then it tells me a 10102 error Cannot Compose Mail Message > occurs. > the given exception is: > javax.mail.internet.AddressException > message: Nested Group > > after trying to resend 2 times the client receives an error > message: > errorCode="Delivery Failure" severity="Error" > description="Communication error". > > which is logical offcourse :) > > Can you tell me if the email address format is not supported > or if we > are doing something wrong? > > Greetz, > > Mark Zenhorst > > > > ------------------------------------------------------- > This SF.Net email sponsored by: ApacheCon 2003, > 16-19 November in Las Vegas. Learn firsthand the latest > developments in Apache, PHP, Perl, XML, Java, MySQL, > WebDAV, and more! http://www.apachecon.com/ > _______________________________________________ > ebxmlms-general mailing list > ebx...@li... > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general > |
|
From: Larchier C. <cla...@ax...> - 2003-11-17 10:15:07
|
Patrick,
=20
The answer is yes for your 2 first questions.
=20
I have uncommented the following lines in msh.properties.xml (and =
restarted Tomcat) :
<Proxy>
<Host>localhost</Host>
<Port>8282</Port>
</Proxy>
But it seems changing nothing.
In the msh.log trace I always have :
2003-11-17 10:00:49,687 INFO [Thread-18]: Sending message to =
http://localhost:8080/msh
And with TCPMon I get nothing on 8282 port.
=20
Is there something else to do?
=20
Christophe
-----Message d'origine-----
De : ebx...@li... =
[mailto:ebx...@li...]De la part de =
Patrick Yee
Envoy=E9 : samedi 15 novembre 2003 15:19
=C0 : ebx...@li...
Objet : Re: [ebxmlms-general] Digital signature
Christophe,
=20
So you have send out the message twice using Monitor, once without using =
digital signature, once with digital signature, right? Are you using =
exactly the same parameters in Monitor, with only the digital signature =
check box in the latter case?
=20
If the answer is yes, we have still no clue about what's happening in =
your case. To further investigate, you can try to grab a very useful =
tool called TCPMon from Apache AXIS project. This tool should be =
installed between your Monitor and the MSH server, and it can help you =
to capture all the HTTP level traffic between Monitor and MSH server, =
and then forward the captured traffic out as a proxy.=20
=20
It will be useful to capture the text/plain message to see the cause.
=20
Regards, -Patrick
=20
----- Original Message -----=20
From: Larchier <mailto:cla...@ax...> Christophe=20
To: ebx...@li...=20
Sent: Friday, November 14, 2003 3:31 PM
Subject: RE: [ebxmlms-general] Digital signature
It's a loopback test.
Note that the loopback test without digital signature works fine.
=20
Christophe
-----Message d'origine-----
De : ebx...@li... =
[mailto:ebx...@li...]De la part de =
Patrick Yee
Envoy=E9 : jeudi 13 novembre 2003 11:32
=C0 : ebx...@li...
Objet : Re: [ebxmlms-general] Digital signature
Larchier,
Where did you send the message to? It seems that the target end sent =
back a message that is not comprehensible by Hermes.
Regards, -Patrick
Larchier Christophe wrote:
Hi all,=20
With the MSH monitor, when I send a message with digital signature, I =
get the following message in the Tomcat console :=20
javax.xml.soap.SOAPException: Invalid Content-Type:text/plain=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
javax.xml.soap.SOAPException: Unable to internalize message=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) =
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
Caused by: javax.xml.soap.SOAPException: Invalid Content-Type:text/plain =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20
... 7 more=20
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: =
Unable to internalize message=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
Caused by: javax.xml.soap.SOAPException: Unable to internalize message=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) =
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
... 4 more=20
After few minutes, I receive an error message : "Delivery failure".=20
Thanks for your help.=20
______________________________________=20
Christophe Larchier=20
Axway.=20
a Sopra Group company.=20
3, rue de Pr=E9 Faucon=20
PAE - Les Glaisins - BP238=20
F-74942 Annecy-le-Vieux Cedex=20
* +33 (0)4 50 33 31 55=20
______________________________________=20
------------------------------------------------------- This SF.Net =
email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn =
firsthand the latest developments in Apache, PHP, Perl, XML, Java, =
MySQL, WebDAV, and more! http://www.apachecon.com/ =
_______________________________________________ ebxmlms-general mailing =
list ebx...@li... =
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general=20
|
|
From: Ronald v. K. <rv...@ab...> - 2003-11-16 23:03:04
|
-----Oorspronkelijk bericht----- Van: Patrick Yee [mailto:kc...@ce...] Verzonden: zaterdag 15 november 2003 15:35 Aan: ebx...@li... Onderwerp: Re: [ebxmlms-general] idea : use ebXML to bridge the gap, through JMS Christophe, Thank you for your cool idea. That makes me excited too. To further the discusison, I have the following questions: 1. What is the difference of your proposed ebXML post office and a ebXML MSH with a pair of JMS queues, one for accepting message to be sent out, and one for the messages to be delivered back to the client? [Ronald van Kuijk] Not much I think, other than that it could be a (defacto?) standard to connect JMS servers of different origin 2. In an ebXML post office, how can different applications to get their own messages back? I mean, how the post office partition the messages for different clients? [Ronald van Kuijk] probably a lot like is done now in hermes.. after sending out a message by putting it in a jms queue, you register a listener on the incomming queue with a filter. This could be a filter which looks for a 'RefToMessageId' identical to the MessageId used when sending out the message (jms has a messageid). Or a more complex one where ebxml message header fields (or service, action, conversationid) are mapped to extended jms header properties. 3. How about encryption? If the post office should examine the messages before to send it out, does that imply we have to sacrifice end to end security? [Ronald van Kuijk] Hmm.. depends on who creates the envelope. If the client that puts the message in a queue generates the envelope, it could not be fully encrypted, at least not the relevant fields. otoh, these could also be put in jms header fields that can be used by the postoffice without looking into the envelope. just my 0.018 Ronald Thanks. Regards, -Patrick ----- Original Message ----- From: Christophe Hartwig-Peillon <mailto:chr...@re...> To: ebx...@li... <mailto:ebx...@li...> Sent: Monday, November 03, 2003 4:59 PM Subject: Re: [ebxmlms-general] idea : use ebXML to bridge the gap, through JMS Hi all, I've been thinking more about it this week end... Here is a new approach to the problem: There is no specification in J2EE concerning messages that should get out of the system. JMS only concerns sending messages reliably to a queue. Even JMS bridges simply allow sending messages to a queue and forwarding to an external queue (JSM to Tibco bridge for instance)... There is no way to take JSM messages out ! What we need is a JMS postoffice ! That's why the match between JMS and ebXML is not easy : ebXML is a distribution (in the sense of mail distribution) protocol. What would be cool is to think in terms of an ebXML postoffice. When you want to send snail mail, you post your letter in a mailbox, except this mailbox is then emptied by the postman, and the mail is dispatched. Internal mail (in a company) does not go through a postoffice, you put the letter in you recepient's mailbox : that's JMS... ebXML actually determines the distribution : to whom should the messages be delivered, should a receipt be expected, should the message be signed, should the message use the HTTP or SMTP path (remember the AirMail stickers on letters ?), should a return address be used for replying, etc... I like this approach because : - everybody now understands the difference between JMS and ebXML goals - the need for ebXML is obvious - the lack of an existing standard is obvious too - the mismatch of JAXM and these goals is obvious (because JAXM does not try to play this postoffice role, does not have postoffice semantics) - the fact that JMS and ebXML are related is clear : JMS is for posting the letter, ebXML is sending it in the right place. ebXML is receiving the mail from the postoffice, JSM is for opening and reading the letter... - CPAs are used to tell the postoffice what it should do, how the message can reach its recepient, etc... Do you like it this way ? I like the idea of a JSR... Because ebXML is now different than JMS (but related to it!), is not about reliable messaging, but about inter-system reliable routing and sending of messages... This is a functional area not yet covered by other Java specifications, so there should be some place for it... Note that there are JSRs related to CPPs/CPAs already... I'm eager to hear your opinion ! Bye Chris --------------------------------------------------------------------- Christophe HARTWIG - Interface Technologies cha...@re... <mailto:cha...@re...> 17, avenue Andre Roussin http://www.reservit.com <http://www.reservit.com> ZAC de Saumaty-Seon Tel : + 33 4 91 03 64 90 13016 MARSEILLE - FRANCE Fax : + 33 4 91 03 64 92 --------------------------------------------------------------------- ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ <http://sourceforge.net/donate/> _______________________________________________ ebxmlms-general mailing list ebx...@li... <mailto:ebx...@li...> https://lists.sourceforge.net/lists/listinfo/ebxmlms-general <https://lists.sourceforge.net/lists/listinfo/ebxmlms-general> |
|
From: Patrick Y. <kc...@ce...> - 2003-11-15 14:35:03
|
Christophe, Thank you for your cool idea. That makes me excited too. To further the = discusison, I have the following questions: 1. What is the difference of your proposed ebXML post office and a ebXML = MSH with a pair of JMS queues, one for accepting message to be sent out, = and one for the messages to be delivered back to the client? 2. In an ebXML post office, how can different applications to get their = own messages back? I mean, how the post office partition the messages = for different clients? 3. How about encryption? If the post office should examine the messages = before to send it out, does that imply we have to sacrifice end to end = security? Thanks. Regards, -Patrick ----- Original Message -----=20 From: Christophe Hartwig-Peillon=20 To: ebx...@li...=20 Sent: Monday, November 03, 2003 4:59 PM Subject: Re: [ebxmlms-general] idea : use ebXML to bridge the gap, = through JMS Hi all, I've been thinking more about it this week end... Here is a new = approach=20 to the problem: There is no specification in J2EE concerning messages that should get=20 out of the system. JMS only concerns sending messages reliably to a queue. Even JMS = bridges=20 simply allow sending messages to a queue and forwarding to an external = queue (JSM to Tibco bridge for instance)... There is no way to take = JSM=20 messages out ! What we need is a JMS postoffice ! That's why the match between JMS = and=20 ebXML is not easy : ebXML is a distribution (in the sense of mail=20 distribution) protocol. What would be cool is to think in terms of an ebXML postoffice. When = you=20 want to send snail mail, you post your letter in a mailbox, except = this=20 mailbox is then emptied by the postman, and the mail is dispatched. Internal mail (in a company) does not go through a postoffice, you put = the letter in you recepient's mailbox : that's JMS... ebXML actually determines the distribution : to whom should the = messages=20 be delivered, should a receipt be expected, should the message be=20 signed, should the message use the HTTP or SMTP path (remember the=20 AirMail stickers on letters ?), should a return address be used for=20 replying, etc... I like this approach because : - everybody now understands the difference between JMS and ebXML goals - the need for ebXML is obvious - the lack of an existing standard is obvious too - the mismatch of JAXM and these goals is obvious (because JAXM does = not=20 try to play this postoffice role, does not have postoffice semantics) - the fact that JMS and ebXML are related is clear : JMS is for = posting=20 the letter, ebXML is sending it in the right place. ebXML is receiving = the mail from the postoffice, JSM is for opening and reading the = letter... - CPAs are used to tell the postoffice what it should do, how the=20 message can reach its recepient, etc... Do you like it this way ? I like the idea of a JSR... Because ebXML is now different than JMS = (but=20 related to it!), is not about reliable messaging, but about = inter-system=20 reliable routing and sending of messages... This is a functional area=20 not yet covered by other Java specifications, so there should be some=20 place for it... Note that there are JSRs related to CPPs/CPAs = already... I'm eager to hear your opinion ! Bye Chris --------------------------------------------------------------------- Christophe HARTWIG - Interface Technologies cha...@re... 17, avenue Andre Roussin http://www.reservit.com ZAC de Saumaty-Seon Tel : + 33 4 91 03 64 90 13016 MARSEILLE - FRANCE Fax : + 33 4 91 03 64 92 ---------------------------------------------------------------------=20 ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ ebxmlms-general mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-general |
|
From: Patrick Y. <kc...@ce...> - 2003-11-15 14:22:47
|
Mark, Sorry, under the current limitation of Hermes, when you send out message = using SMTP protocol, the From Party ID of the message should be a valid = email address also. Regards, -Patrick ----- Original Message -----=20 From: MTM Zenhorst=20 To: ebx...@li...=20 Sent: Friday, November 14, 2003 10:36 PM Subject: [ebxmlms-general] error 10102 Cannot Compose Mail Message Hello, We are trying to install a alocal working ebXML setup but we have encountered a problem. We hope you are able to help us. When we send a message from a msh_client to the MSH server the error occurs. The message is sent with the following information. from partyId: http://192.168.xxx.20:8080/msh type: HTTP to partyId: mailto:ma...@19....20 type: MAIL the message is sent and it arrives at the MSH server. At that point I think the actual error occurs. The log file shows: sending message to ma...@19....20 through 192.168.xxx.20 then it tells me a 10102 error Cannot Compose Mail Message occurs. the given exception is: javax.mail.internet.AddressException message: Nested Group after trying to resend 2 times the client receives an error message: errorCode=3D"Delivery Failure" severity=3D"Error" description=3D"Communication error". which is logical offcourse :) Can you tell me if the email address format is not supported or if we are doing something wrong? Greetz, Mark Zenhorst ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ ebxmlms-general mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-general |
|
From: Patrick Y. <kc...@ce...> - 2003-11-15 14:18:48
|
Christophe,
So you have send out the message twice using Monitor, once without using =
digital signature, once with digital signature, right? Are you using =
exactly the same parameters in Monitor, with only the digital signature =
check box in the latter case?
If the answer is yes, we have still no clue about what's happening in =
your case. To further investigate, you can try to grab a very useful =
tool called TCPMon from Apache AXIS project. This tool should be =
installed between your Monitor and the MSH server, and it can help you =
to capture all the HTTP level traffic between Monitor and MSH server, =
and then forward the captured traffic out as a proxy.=20
It will be useful to capture the text/plain message to see the cause.
Regards, -Patrick
----- Original Message -----=20
From: Larchier Christophe=20
To: ebx...@li...=20
Sent: Friday, November 14, 2003 3:31 PM
Subject: RE: [ebxmlms-general] Digital signature
It's a loopback test.
Note that the loopback test without digital signature works fine.
Christophe
-----Message d'origine-----
De : ebx...@li... =
[mailto:ebx...@li...]De la part de =
Patrick Yee
Envoy=E9 : jeudi 13 novembre 2003 11:32
=C0 : ebx...@li...
Objet : Re: [ebxmlms-general] Digital signature
Larchier,
Where did you send the message to? It seems that the target end sent =
back a message that is not comprehensible by Hermes.
Regards, -Patrick
Larchier Christophe wrote:
Hi all,=20
With the MSH monitor, when I send a message with digital =
signature, I get the following message in the Tomcat console :=20
javax.xml.soap.SOAPException: Invalid Content-Type:text/plain=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
at java.security.AccessController.doPrivileged(Native =
Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at =
hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)=20
javax.xml.soap.SOAPException: Unable to internalize message=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) =
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
at java.security.AccessController.doPrivileged(Native =
Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at =
hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)=20
Caused by: javax.xml.soap.SOAPException: Invalid =
Content-Type:text/plain=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20
... 7 more=20
java.security.PrivilegedActionException: =
javax.xml.soap.SOAPException: Unable to internalize message=20
at java.security.AccessController.doPrivileged(Native =
Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at =
hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)=20
Caused by: javax.xml.soap.SOAPException: Unable to internalize =
message=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) =
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
... 4 more=20
After few minutes, I receive an error message : "Delivery =
failure".=20
Thanks for your help.=20
______________________________________=20
Christophe Larchier=20
Axway.=20
a Sopra Group company.=20
3, rue de Pr=E9 Faucon=20
PAE - Les Glaisins - BP238=20
F-74942 Annecy-le-Vieux Cedex=20
( +33 (0)4 50 33 31 55=20
______________________________________=20
------------------------------------------------------- This SF.Net =
email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn =
firsthand the latest developments in Apache, PHP, Perl, XML, Java, =
MySQL, WebDAV, and more! http://www.apachecon.com/ =
_______________________________________________ ebxmlms-general mailing =
list ebx...@li... =
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general |
|
From: Patrick Y. <kc...@ce...> - 2003-11-15 14:08:53
|
Ajit, If you look at the sample code in Hermes client, you can see the constructor of a Request object has a parameter called toMshUrl. When the client sends out the message though this Request object, MSH will then in turn send that message out using that toMshUrl as the endpoint. And you are right, writing a custom URL resolver can be another way to "tell" MSH about the end point. You can write a custom URL resolver and specify it inside msh.properties.xml. Normally, your custom URL resolver should be capable to resolve a URL by an ebXML message (e.g. using it's toPartyID, or using it's service/action pair, etc.) In operation, when MSH gets a message to send out, it will pass the message to your custom URL resolver, and then your resolver should return a URL, and then MSH will use that endpoint to send the message out. Hope this helps. Regards, -Patrick ----- Original Message ----- From: "Tripathi, Ajit (GXS)" <Aji...@gx...> To: <ebx...@li...> Sent: Thursday, November 13, 2003 6:48 PM Subject: RE: [ebxmlms-general] ebXML sample client question > Patrick, > > Got it! Question is ... what in the MSH resolves a (service, action) to > a (protocol, URL)? > > If I understand it right, the service is a part of business process in > this context. An interface... > > However, in the end, based on the action and the service, doesn't the > MSH have to figure out what endpoint to relay the message to? > > If yes, do I need to write a custom URL resolver to do that and plug it > in using the config file? > > regards, > Ajit > > > -----Original Message----- > From: Patrick Yee [mailto:kc...@ce...] > Sent: Thursday, November 13, 2003 4:00 PM > To: ebx...@li... > Subject: Re: [ebxmlms-general] ebXML sample client question > > > > Ajit, > > No, the service field is not of that purpose. Let's put it this way, 2 > companies do business over ebXML. They develop their own applications at > each side. They are said to be offering a "service" to their counterparts. > Each application at one side may handle one or more types of business > request. So we said the "service" includes one or more types of "action". > > In ebXML messaging service, the service and action are defined as above. > When the business documents are delivered through ebMS, that "service" and > "action" are marked in the ebMS message headers, the purpose is let MSH be > able to route the received messages to the correct application. Of course, > the application should beforehand notify the MSH that which "service" and > "action" are supported by this application too. > > Hope this helps. > > Regards, -Patrick > > > |
|
From: MTM Z. <zen...@fe...> - 2003-11-14 14:36:50
|
Hello, We are trying to install a alocal working ebXML setup but we have encountered a problem. We hope you are able to help us. When we send a message from a msh_client to the MSH server the error occurs. The message is sent with the following information. from partyId: http://192.168.xxx.20:8080/msh type: HTTP to partyId: mailto:ma...@19....20 type: MAIL the message is sent and it arrives at the MSH server. At that point I think the actual error occurs. The log file shows: sending message to ma...@19....20 through 192.168.xxx.20 then it tells me a 10102 error Cannot Compose Mail Message occurs. the given exception is: javax.mail.internet.AddressException message: Nested Group after trying to resend 2 times the client receives an error message: errorCode="Delivery Failure" severity="Error" description="Communication error". which is logical offcourse :) Can you tell me if the email address format is not supported or if we are doing something wrong? Greetz, Mark Zenhorst |
|
From: Larchier C. <cla...@ax...> - 2003-11-14 07:32:11
|
It's a loopback test.
Note that the loopback test without digital signature works fine.
=20
Christophe
-----Message d'origine-----
De : ebx...@li... =
[mailto:ebx...@li...]De la part de =
Patrick Yee
Envoy=E9 : jeudi 13 novembre 2003 11:32
=C0 : ebx...@li...
Objet : Re: [ebxmlms-general] Digital signature
Larchier,
Where did you send the message to? It seems that the target end sent =
back a message that is not comprehensible by Hermes.
Regards, -Patrick
Larchier Christophe wrote:
Hi all,=20
With the MSH monitor, when I send a message with digital signature, I =
get the following message in the Tomcat console :=20
javax.xml.soap.SOAPException: Invalid Content-Type:text/plain=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
javax.xml.soap.SOAPException: Unable to internalize message=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) =
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
Caused by: javax.xml.soap.SOAPException: Invalid Content-Type:text/plain =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159) =
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)=20
... 7 more=20
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: =
Unable to internalize message=20
at java.security.AccessController.doPrivileged(Native Method)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)=20
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)=20
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)=20
Caused by: javax.xml.soap.SOAPException: Unable to internalize message=20
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135) =
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)=20
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)=20
... 4 more=20
After few minutes, I receive an error message : "Delivery failure".=20
Thanks for your help.=20
______________________________________=20
Christophe Larchier=20
Axway.=20
a Sopra Group company.=20
3, rue de Pr=E9 Faucon=20
PAE - Les Glaisins - BP238=20
F-74942 Annecy-le-Vieux Cedex=20
* +33 (0)4 50 33 31 55=20
______________________________________=20
------------------------------------------------------- This SF.Net =
email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn =
firsthand the latest developments in Apache, PHP, Perl, XML, Java, =
MySQL, WebDAV, and more! http://www.apachecon.com/ =
_______________________________________________ ebxmlms-general mailing =
list ebx...@li... =
https://lists.sourceforge.net/lists/listinfo/ebxmlms-general=20
|
|
From: Tripathi, A. (GXS) <Aji...@gx...> - 2003-11-13 10:52:46
|
Patrick,
Got it! Question is ... what in the MSH resolves a (service, action) to
a (protocol, URL)?
If I understand it right, the service is a part of business process in
this context. An interface...
However, in the end, based on the action and the service, doesn't the
MSH have to figure out what endpoint to relay the message to?
If yes, do I need to write a custom URL resolver to do that and plug it
in using the config file?
regards,
Ajit
-----Original Message-----
From: Patrick Yee [mailto:kc...@ce...]
Sent: Thursday, November 13, 2003 4:00 PM
To: ebx...@li...
Subject: Re: [ebxmlms-general] ebXML sample client question
Ajit,
No, the service field is not of that purpose. Let's put it this way, 2
companies do business over ebXML. They develop their own applications at
each side. They are said to be offering a "service" to their counterparts.
Each application at one side may handle one or more types of business
request. So we said the "service" includes one or more types of "action".
In ebXML messaging service, the service and action are defined as above.
When the business documents are delivered through ebMS, that "service" and
"action" are marked in the ebMS message headers, the purpose is let MSH be
able to route the received messages to the correct application. Of course,
the application should beforehand notify the MSH that which "service" and
"action" are supported by this application too.
Hope this helps.
Regards, -Patrick
|
|
From: Patrick Y. <kc...@ce...> - 2003-11-13 10:31:57
|
<!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"> Larchier,<br> <br> Where did you send the message to? It seems that the target end sent back a message that is not comprehensible by Hermes.<br> <br> Regards, -Patrick<br> <br> <br> <br> <br> Larchier Christophe wrote:<br> <blockquote type="cite" cite="mid...@we..."> <meta content="text/html; " http-equiv="Content-Type"> <meta content="MS Exchange Server version 6.0.6487.1" name="Generator"> <title>Digital signature</title> <!-- Converted from text/rtf format --> <p><font face="Arial" size="2">Hi all,</font> </p> <p><font face="Arial" size="2">With the MSH monitor, when I send a message with digital signature, I get the following message in the Tomcat console :</font> </p> <p><font face="Arial" size="2">javax.xml.soap.SOAPException: Invalid Content-Type:text/plain</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:32)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:333)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:142)</font> <br> <font face="Arial" size="2"> at java.security.AccessController.doPrivileged(Native Method)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:115)</font> <br> <font face="Arial" size="2"> at hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)</font> <br> <font face="Arial" size="2"> at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)</font> <br> <font face="Arial" size="2">javax.xml.soap.SOAPException: Unable to internalize message</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:32)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:333)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:142)</font> <br> <font face="Arial" size="2"> at java.security.AccessController.doPrivileged(Native Method)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:115)</font> <br> <font face="Arial" size="2"> at hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)</font> <br> <font face="Arial" size="2"> at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)</font> <br> <font face="Arial" size="2">Caused by: javax.xml.soap.SOAPException: Invalid Content-Type:text/plain</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)</font> <br> <font face="Arial" size="2"> ... 7 more</font> <br> <font face="Arial" size="2">java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Unable to internalize message</font> <br> <font face="Arial" size="2"> at java.security.AccessController.doPrivileged(Native Method)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:115)</font> <br> <font face="Arial" size="2"> at hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)</font> <br> <font face="Arial" size="2"> at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown Source)</font> <br> <font face="Arial" size="2">Caused by: javax.xml.soap.SOAPException: Unable to internalize message</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:32)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:333)</font> <br> <font face="Arial" size="2"> at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:142)</font> <br> <font face="Arial" size="2"> ... 4 more</font> </p> <p><font face="Arial" size="2">After few minutes, I receive an error message : "Delivery failure".</font> </p> <p><font face="Arial" size="2">Thanks for your help.</font> </p> <br> <br> <p><b><font face="Arial" size="2" color="#000080">______________________________________</font></b> </p> <p><b><font face="Times New Roman" size="2">Christophe Larchier </font></b> <br> <b><font face="Century Schoolbook" size="6" color="#808080">Axwa</font><font face="Century Schoolbook" size="6" color="#ff0000">y.</font></b> <br> <b><i><font face="Arial" size="1">a</font> <font face="Arial" size="1">Sopra</font> <font face="Arial" size="1">Group company.</font></i></b> </p> <p><font face="Times New Roman" size="2">3, rue de Pré Faucon</font> <br> <font face="Times New Roman" size="2">PAE - Les Glaisins - BP238</font> <br> <font face="Times New Roman" size="2">F-74942 Annecy-le-Vieux Cedex</font> <br> <font face="Wingdings" size="2">(</font><font face="Times New Roman" size="2"> +33 (0)4 50 33 31 55</font> <br> <b><font face="Arial" size="2" color="#000080">______________________________________</font></b> </p> <br> <br> </blockquote> <br> </body> </html> |
|
From: Patrick Y. <kc...@ce...> - 2003-11-13 10:30:50
|
<!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">
Ajit,<br>
<br>
No, the service field is not of that purpose. Let's put it this way, 2
companies do business over ebXML. They develop their own applications
at each side. They are said to be offering a "service" to their
counterparts. Each application at one side may handle one or more types
of business request. So we said the "service" includes one or more
types of "action".<br>
<br>
In ebXML messaging service, the service and action are defined as
above. When the business documents are delivered through ebMS, that
"service" and "action" are marked in the ebMS message headers, the
purpose is let MSH be able to route the received messages to the
correct application. Of course, the application should beforehand
notify the MSH that which "service" and "action" are supported by this
application too.<br>
<br>
Hope this helps.<br>
<br>
Regards, -Patrick<br>
<br>
<br>
Tripathi, Ajit (GXS) wrote:<br>
<blockquote type="cite"
cite="mid...@ba...">
<meta content="text/html; " http-equiv="Content-Type">
<title></title>
<meta name="GENERATOR" content="MSHTML 6.00.2800.1226">
<style></style>
<div><span class="203322712-10112003"><font size="2" color="#0000ff"
face="Arial">Patrick,</font></span></div>
<div><span class="203322712-10112003"></span> </div>
<div><span class="203322712-10112003"> <font size="2"
color="#0000ff" face="Arial">Doesn't the msh relay ebXML messages to
the receiving applications described by the service field? Then how do
receiving applications use it (as in the case study on the hermes
website)?</font></span></div>
<div><span class="203322712-10112003"></span> </div>
<div><span class="203322712-10112003"><font size="2" color="#0000ff"
face="Arial">regards,</font></span></div>
<div><span class="203322712-10112003"><font size="2" color="#0000ff"
face="Arial">Ajit</font></span></div>
<blockquote style="margin-right: 0px;" dir="ltr">
<div align="left" dir="ltr" class="OutlookMessageHeader"><font
size="2" face="Tahoma">-----Original Message-----<br>
<b>From:</b> Patrick Yee [<a class="moz-txt-link-freetext" href="mailto:kc...@ce...">mailto:kc...@ce...</a>]<br>
<b>Sent:</b> Saturday, November 08, 2003 8:14 AM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a><br>
<b>Subject:</b> Re: [ebxmlms-general] ebXML sample client question<br>
<br>
</font></div>
<div><font size="2" face="Arial">No. That service is only a field
in ebXML Messaging Service. It is not used as endpoint for forwarding,
instead, it only use as a header for identifying the receiving
applications.</font></div>
<div> </div>
<div><font size="2" face="Arial">The toMshUrl is the one you need
to set to make your messages being forwarded to other hosts.</font></div>
<div> </div>
<div><font size="2" face="Arial">Regards, -patrick</font></div>
<div> </div>
<div> </div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;"
dir="ltr">
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;">-----
Original Message ----- </div>
<div
style="background: rgb(228, 228, 228) none repeat scroll 0%; -moz-background-clip: initial; -moz-background-origin: initial; -moz-background-inline-policy: initial; font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>From:</b>
<a href="mailto:Aji...@gx..."
title="Aji...@gx...">Tripathi, Ajit (GXS)</a> </div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>To:</b>
<a href="mailto:%27e...@li...%27"
title="ebx...@li...">'ebx...@li...'</a>
</div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Sent:</b>
Friday, November 07, 2003 1:04 PM</div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Subject:</b>
[ebxmlms-general] ebXML sample client question</div>
<div><br>
</div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003">Hi,</span></font></font></font></div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"></span></font></font></font> </div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"> If I put the following in my loopback
client...</span></font></font></font></div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"></span></font></font></font> </div>
<div><font color="#0000ff"><font size="+0"><font face="Arial"><font
size="2"><span class="984065504-07112003"> </span> <span
class="984065504-07112003"> </span>String cpaID = "CPA_2002";<br>
String conversationID = "Item_No_128";<br>
String service = "</font></font></font><a
href="http://localhost:8080/loopback"><font size="2" face="Arial">http://localhost:8080/loopback</font></a><font
face="Arial"><font size="2">";<br>
String action = "Order";<br>
<span class="984065504-07112003"> </span></font></font></font></div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"> Shouldn't the msh forward the message to
"<a href="http://localhost:8080/loopback"><font size="2" face="Arial">http://localhost:8080/loopback</font></a><font
face="Arial"><font size="2">"? It doesn't seem to.</font></font></span></font></font></font></div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"></span></font></font></font> </div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"> How do I make the msh forward the ebXML
message to another JAXM servlet?</span></font></font></font></div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"></span></font></font></font> </div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"><font face="Arial"><font size="2">regards,</font></font></span></font></font></font></div>
<div><font color="#0000ff"><font face="Arial"><font size="2"><span
class="984065504-07112003"><font face="Arial"><font size="2">Ajit</font></font></span></font></font></font></div>
<font color="#0000ff"><font face="Arial"><font size="2"><font
face="Arial"><font size="2">
<div><br>
</div>
</font></font></font></font></font></blockquote>
</blockquote>
</blockquote>
<br>
</body>
</html>
|
|
From: Patrick Y. <kc...@ce...> - 2003-11-13 10:13:01
|
Not in the current version. As Bob said, we will undergo a big change in Hermes architecture so as to adapt to multiple protocols. Personally I like this idea and will start this discussion in the development team. Regards, -Patrick > > Any change of making an interface an changing some things to the > MessageServiceHandler.java so it could be easy to give others the > option to use the connectionpools that come with the appserver/servlet > engine? |
|
From: Larchier C. <cla...@ax...> - 2003-11-12 09:30:07
|
Hi all,
With the MSH monitor, when I send a message with digital signature, I =
get the following message in the Tomcat console :
javax.xml.soap.SOAPException: Invalid Content-Type:text/plain
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.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)
javax.xml.soap.SOAPException: Unable to internalize message
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135)
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)
at java.security.AccessController.doPrivileged(Native Method)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)
Caused by: javax.xml.soap.SOAPException: Invalid Content-Type:text/plain
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.verify(MessageImpl.java:159)
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:91)
... 7 more
java.security.PrivilegedActionException: javax.xml.soap.SOAPException: =
Unable to internalize message
at java.security.AccessController.doPrivileged(Native Method)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPCon=
nection.java:115)
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown Source)
at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown =
Source)
Caused by: javax.xml.soap.SOAPException: Unable to internalize message
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:135)
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(MessageF=
actoryImpl.java:32)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPCon=
nection.java:333)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.=
run(HttpSOAPConnection.java:142)
... 4 more
After few minutes, I receive an error message : "Delivery failure".
Thanks for your help.
______________________________________
Christophe Larchier=20
Axway.
a Sopra Group company.
3, rue de Pr=E9 Faucon
PAE - Les Glaisins - BP238
F-74942 Annecy-le-Vieux Cedex
* +33 (0)4 50 33 31 55
______________________________________
|
|
From: Tripathi, A. (GXS) <Aji...@gx...> - 2003-11-10 12:25:02
|
Patrick,
Doesn't the msh relay ebXML messages to the receiving applications
described by the service field? Then how do receiving applications use it
(as in the case study on the hermes website)?
regards,
Ajit
-----Original Message-----
From: Patrick Yee [mailto:kc...@ce...]
Sent: Saturday, November 08, 2003 8:14 AM
To: ebx...@li...
Subject: Re: [ebxmlms-general] ebXML sample client question
No. That service is only a field in ebXML Messaging Service. It is not used
as endpoint for forwarding, instead, it only use as a header for identifying
the receiving applications.
The toMshUrl is the one you need to set to make your messages being
forwarded to other hosts.
Regards, -patrick
----- Original Message -----
From: Tripathi, <mailto:Aji...@gx...> Ajit (GXS)
To: 'ebx...@li...'
<mailto:'ebx...@li...'>
Sent: Friday, November 07, 2003 1:04 PM
Subject: [ebxmlms-general] ebXML sample client question
Hi,
If I put the following in my loopback client...
String cpaID = "CPA_2002";
String conversationID = "Item_No_128";
String service = " <http://localhost:8080/loopback>
http://localhost:8080/loopback";
String action = "Order";
Shouldn't the msh forward the message to "
<http://localhost:8080/loopback> http://localhost:8080/loopback"? It doesn't
seem to.
How do I make the msh forward the ebXML message to another JAXM servlet?
regards,
Ajit
|
|
From: Ronald v. K. <rv...@ab...> - 2003-11-08 19:57:22
|
Yes Patrick, I do. The current mail and activation libraries from sun (even the ones that came with the jaxm summerpack 2002) work fine. We had the problem in Bea Weblogic and solved that by overriding the implementation that comes with bea by the ones that are in the jaxm summer pack 2002 (bea finally solved it in 6.1sp5 and it took them 3 serivicepacks to do it right). I never had the problem in JBoss with it's implementation of mail and activation. Shoud 'we' join the two lines into one by not using the default libraries that can do that for us because the other systems are not able to process valid responses?? Technically I would not like that, businesswise we probably should. I think i'd choose the ad-hoc solution and not writing our own mime-header parsing routines. Ronald Patrick Yee wrote: > Ronald, > > Are you referring to the mime header "content-type"? We met that > sometimes before when we are doing interop test with other vendors. > What we try to do is to manually make that splitted header into one > line using some tricks in Javamail. But that's kind-of ad-hoc.. So, we > plan to bypass Javamail to outputting multipart messages.. what do you > think? > > Regards, -Patrick > > > ----- Original Message ----- > *From:* Ronald van Kuijk <mailto:rv...@ab...> > *To:* 'ebx...@li...' > <mailto:%27e...@li...%27> > *Sent:* Saturday, November 08, 2003 12:03 AM > *Subject:* RE: [ebxmlms-general] interesting hermes error > > Do you get this message in hermes on receiving 'echo'? > > This is caused by the servelet not detecting a multipart-mime > header. Either because it's not there or because the format is > wrong. There has been problems with the mail/activation libraries > in Bea where they wew unable to detect a boundary that spanned > multiple lines. (spanning is done by having the second line begin > with a whitespace character, which bea failed to detect). An plain > html or a simple xml (including a echo of an ebxml > envelop!!) response also does not have the boundary set, and > therefor leads to the same error > > Ronald > > -----Oorspronkelijk bericht----- > *Van:* Tripathi, Ajit (GXS) [mailto:Aji...@gx...] > *Verzonden:* vrijdag 7 november 2003 16:38 > *Aan:* 'ebx...@li...' > *Onderwerp:* [ebxmlms-general] interesting hermes error > > Hi, > > I am using hermes to send a message from hermes to a JAXM > servlet. If I return the same ebXML message in reponse, this > is what I am getting. > > regards, > Ajit > > javax.mail.MessagingException: Missing start boundary > at > javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284) > at > javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172) > > at > com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1 > 18) > at > com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess > ageFactoryImpl.java:32) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA > PConnection.java:333) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP > ost.run(HttpSOAPConnection.java:142) > at java.security.AccessController.doPrivileged(Native > Method) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA > PConnection.java:115) > at > hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j > ava:231) > at > hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1 > 38) > javax.xml.soap.SOAPException: Unable to internalize message > at > com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1 > 35) > at > com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess > ageFactoryImpl.java:32) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA > PConnection.java:333) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP > ost.run(HttpSOAPConnection.java:142) > at java.security.AccessController.doPrivileged(Native > Method) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA > PConnection.java:115) > at > hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j > ava:231) > at > hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1 > 38) > Caused by: javax.mail.MessagingException: Missing start boundary > at > javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284) > at > javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172) > > at > com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1 > 18) > |
|
From: Ronald v. K. <rv...@ab...> - 2003-11-08 19:46:41
|
Thanks for the response Patrick Yee wrote: >>btw. Can somebody explain why there is a normal and a raw connection? >> >> > >A normal connection is pooled. A raw is not. For a pooled one, we have put >effort to make sure it works. > This part I found out from the code ;-), but thanks anyway for explaining >(In some cases, we find DB server cutting idle >connections, so the idle pooled db connection object is not usable after a >while). To check the validity of the pooled connection, we do a simple >select on one of a table. > > This can be done with the other connectionpools to (e.g. tomcat, jboss, weblogic), sometimes even in the driver (mysql) >But when Hermes starts up in the first time, it may create the tables. So >before the tables are created, we cannot use the pooled connections (all >pooled ones are "considered" as invalid as it cannot do the select on the >table). In that case, we use raw connection. > > Ok, so it is not because you want to have the guarantee that even if the connectionpool is fully used you could still use a raw connection? Any change of making an interface an changing some things to the MessageServiceHandler.java so it could be easy to give others the option to use the connectionpools that come with the appserver/servlet engine? Ronald > >Hope it is clear. > >Regards, -Patrick > > >------------------------------------------------------- >This SF.Net email sponsored by: ApacheCon 2003, >16-19 November in Las Vegas. Learn firsthand the latest >developments in Apache, PHP, Perl, XML, Java, MySQL, >WebDAV, and more! http://www.apachecon.com/ >_______________________________________________ >ebxmlms-general mailing list >ebx...@li... >https://lists.sourceforge.net/lists/listinfo/ebxmlms-general > > |
|
From: Ronald v. K. <rv...@ab...> - 2003-11-08 19:35:50
|
Ajit, This is just the soap part. What is needed to explain the 'missing start boundary' is the http header... it should look something like: POST /servlet/ebXMLhandler HTTP/1.1 Host: www.example2.com SOAPAction: "ebXML" Content-type: multipart/related; boundary="----=_Part_2_24749215.1068222593281"; type="text/xml"; start="<ebx...@ex...>" This example is taken from the ebxml specs where I changed the boundary to match your message (as it should) The start part may be omitted (afaik) I haven't found a way yet to dump these headers from Java, other than a partial list via a a getMimeHeaders on the SOAPMessage object. You could try to implement this on the echoing jaxm servlet or use ethereal as mentioned earlier. Ronald ''Tripathi, Ajit (GXS) wrote: > Ron, > > Here is the echo message that caused the problem (between echo lines)! > > ----------echo------------------------- > > ------=_Part_2_24749215.1068222593281 > Content-Type: text/xml > Content-Id: <soappart> > > <?xml version="1.0" encoding="UTF-8"?> > <soap-env:Envelope > xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xm > lns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:xlink="http://www.w3.o > rg/1999/xlink" > xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ htt > p://www.oasis-open.org/committees/ebxml-msg/schema/envelope.xsd"><soap-env:Heade > r > 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="fromPartyId">Sample</eb:PartyId></eb:From><eb:To><eb:P > artyId > eb:type="toPartyId">Sampola</eb:PartyId></eb:To><eb:CPAId>CPA_2003</eb:CP > AId><eb:ConversationId>Item_No_128</eb:ConversationId><eb:Service>http://localho > st:9090/loopback</eb:Service><eb:Action>Order</eb:Action><eb:MessageData><eb:Mes > sageId>20031107-162721578-CPA_2003.http://localhost:9090/loopback.Order.1@10.24. > 200.237</eb:MessageId><eb:Timestamp>2003-11-07T16:27:21Z</eb:Timestamp></eb:Mess > ageData></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"><eb:Manifest > <http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd%22%3E%3Ceb:Manifest> > xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.x > sd" eb:version="2.0"><eb:Reference eb:id="contentId" > xlink:type="simple" xlink:h > ref="cid:contentId"><eb:Description > xml:lang="en-US">description</eb:Description > ></eb:Reference></eb:Manifest></soap-env:Body></soap-env:Envelope> > ------=_Part_2_24749215.1068222593281 > Content-Type: text/xml > Content-Transfer-Encoding: binary > Content-Id: <contentId> > > <po/> > > ------=_Part_2_24749215.1068222593281-- > > ----------echo------------------------- > > regards, > Ajit > > -----Original Message----- > *From:* Ronald van Kuijk [mailto:rv...@ab...] > *Sent:* Friday, November 07, 2003 9:33 PM > *To:* 'ebx...@li...' > *Subject:* RE: [ebxmlms-general] interesting hermes error > > Do you get this message in hermes on receiving 'echo'? > > This is caused by the servelet not detecting a multipart-mime > header. Either because it's not there or because the format is > wrong. There has been problems with the mail/activation libraries > in Bea where they wew unable to detect a boundary that spanned > multiple lines. (spanning is done by having the second line begin > with a whitespace character, which bea failed to detect). An plain > html or a simple xml (including a echo of an ebxml > envelop!!) response also does not have the boundary set, and > therefor leads to the same error > > Ronald > > -----Oorspronkelijk bericht----- > *Van:* Tripathi, Ajit (GXS) [mailto:Aji...@gx...] > *Verzonden:* vrijdag 7 november 2003 16:38 > *Aan:* 'ebx...@li...' > *Onderwerp:* [ebxmlms-general] interesting hermes error > > Hi, > > I am using hermes to send a message from hermes to a JAXM > servlet. If I return the same ebXML message in reponse, this > is what I am getting. > > regards, > Ajit > > javax.mail.MessagingException: Missing start boundary > at > javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284) > at > javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172) > > at > com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1 > 18) > at > com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess > ageFactoryImpl.java:32) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA > PConnection.java:333) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP > ost.run(HttpSOAPConnection.java:142) > at java.security.AccessController.doPrivileged(Native > Method) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA > PConnection.java:115) > at > hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j > ava:231) > at > hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1 > 38) > javax.xml.soap.SOAPException: Unable to internalize message > at > com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1 > 35) > at > com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess > ageFactoryImpl.java:32) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA > PConnection.java:333) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP > ost.run(HttpSOAPConnection.java:142) > at java.security.AccessController.doPrivileged(Native > Method) > at > com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA > PConnection.java:115) > at > hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j > ava:231) > at > hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1 > 38) > Caused by: javax.mail.MessagingException: Missing start boundary > at > javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284) > at > javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172) > > at > com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1 > 18) > |
|
From: Patrick Y. <kc...@ce...> - 2003-11-08 02:51:34
|
Ronald,
Are you referring to the mime header "content-type"? We met that =
sometimes before when we are doing interop test with other vendors. What =
we try to do is to manually make that splitted header into one line =
using some tricks in Javamail. But that's kind-of ad-hoc.. So, we plan =
to bypass Javamail to outputting multipart messages.. what do you think?
Regards, -Patrick
----- Original Message -----=20
From: Ronald van Kuijk=20
To: 'ebx...@li...'=20
Sent: Saturday, November 08, 2003 12:03 AM
Subject: RE: [ebxmlms-general] interesting hermes error
Do you get this message in hermes on receiving 'echo'?
This is caused by the servelet not detecting a multipart-mime header. =
Either because it's not there or because the format is wrong. There has =
been problems with the mail/activation libraries in Bea where they wew =
unable to detect a boundary that spanned multiple lines. (spanning is =
done by having the second line begin with a whitespace character, which =
bea failed to detect). An plain html or a simple xml (including a echo =
of an ebxml envelop!!) response also does not have the boundary set, and =
therefor leads to the same error=20
Ronald
-----Oorspronkelijk bericht-----
Van: Tripathi, Ajit (GXS) [mailto:Aji...@gx...]
Verzonden: vrijdag 7 november 2003 16:38
Aan: 'ebx...@li...'
Onderwerp: [ebxmlms-general] interesting hermes error
Hi,
I am using hermes to send a message from hermes to a JAXM =
servlet. If I return the same ebXML message in reponse, this is what I =
am getting.
regards,
Ajit
javax.mail.MessagingException: Missing start boundary
at =
javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
at =
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18)
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
at java.security.AccessController.doPrivileged(Native =
Method)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
at =
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
javax.xml.soap.SOAPException: Unable to internalize message
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
at =
com.sun.xml.messaging.saaj.soap.MessageFactoryImpl.createMessage(Mess
ageFactoryImpl.java:32)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:333)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:142)
at java.security.AccessController.doPrivileged(Native =
Method)
at =
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:115)
at =
hk.hku.cecid.phoenix.message.transport.HttpServlet.send(HttpServlet.j
ava:231)
at =
hk.hku.cecid.phoenix.message.handler.HttpSender.run(HttpSender.java:1
38)
Caused by: javax.mail.MessagingException: Missing start boundary
at =
javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:284)
at =
javax.mail.internet.MimeMultipart.getBodyPart(MimeMultipart.java:172)
at =
com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
18) |
|
From: Patrick Y. <kc...@ce...> - 2003-11-08 02:44:20
|
No. That service is only a field in ebXML Messaging Service. It is not =
used as endpoint for forwarding, instead, it only use as a header for =
identifying the receiving applications.
The toMshUrl is the one you need to set to make your messages being =
forwarded to other hosts.
Regards, -patrick
----- Original Message -----=20
From: Tripathi, Ajit (GXS)=20
To: 'ebx...@li...'=20
Sent: Friday, November 07, 2003 1:04 PM
Subject: [ebxmlms-general] ebXML sample client question
Hi,
If I put the following in my loopback client...
String cpaID =3D "CPA_2002";
String conversationID =3D "Item_No_128";
String service =3D "http://localhost:8080/loopback";
String action =3D "Order";
=20
Shouldn't the msh forward the message to =
"http://localhost:8080/loopback"? It doesn't seem to.
How do I make the msh forward the ebXML message to another JAXM =
servlet?
regards,
Ajit
|
|
From: Patrick Y. <kc...@ce...> - 2003-11-08 02:30:49
|
You are right. As Bob said, we are trying to solve this problem in 1.0. -patrick Failover is also not possible (i think) since the message sending = threads (for retries etc) are created on a restart of the server, so if = one crashes you have to restart the other to have it pick up the = messages. |
|
From: Patrick Y. <kc...@ce...> - 2003-11-08 02:30:09
|
> btw. Can somebody explain why there is a normal and a raw connection? A normal connection is pooled. A raw is not. For a pooled one, we have put effort to make sure it works. (In some cases, we find DB server cutting idle connections, so the idle pooled db connection object is not usable after a while). To check the validity of the pooled connection, we do a simple select on one of a table. But when Hermes starts up in the first time, it may create the tables. So before the tables are created, we cannot use the pooled connections (all pooled ones are "considered" as invalid as it cannot do the select on the table). In that case, we use raw connection. Hope it is clear. Regards, -Patrick |
266 messages has been excluded from this view by a project administrator.
