Menu
▾
▴
Re: [ebxmlms-general] Malformed MessageServiceHandler URL
|
From: Frankie L. <ts...@ce...> - 2002-11-13 02:24:01
|
Dear Simon,
I tried to reproduce the case by internalizing the message using Sun's
implementation of EbXMLMessageImpl(), and it results in the following error:
Exception in thread "main" java.lang.NumberFormatException:
2002-11-01T07:29:07Z
at java.lang.Long.parseLong(Long.java:332)
at java.lang.Long.parseLong(Long.java:381)
at
com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageImpl.setMessageData(EbXM
LMessageImpl.java:269)
at
com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageImpl.setMessageHeader(Eb
XMLMessageImpl.java:181)
at
com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageImpl.fillInHeaders(EbXML
MessageImpl.java:140)
at
com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageImpl.<init>(EbXMLMessage
Impl.java:117)
at Test.main(Unknown Source)
The ebXML Specification 1.092 Section 3.1.6.2 says that the timestamp should
conform to the dateTime [XMLSchema] and MUST be expressed in UTC. However,
the timestamp created by Sun's implementation is:
<eb:Timestamp>1037152439234</eb:Timestamp>
It seems to me that it's a bug that it directly outputs the long value of
the java Date object. Therefore the message created by Hermes cannot be
internalized by Sun's implementation. After modifying the message to use the
timestamp above, the message can be internalized successfully.
Note, however, that there was also a bug in Hermes r0914 that timestamp is
not checked; therefore it can internalize the message created by Sun's
implementation without error =) This is corrected in Hermes r0920.
In addition, the namespaces have changed from ebMS 1.0 and 2.0; therefore
the messages sent by MSH conformant to 1.0 probably cannot be received
correctly by MSH conformant to ebMS 2.0. You may also be interested to know
the other differences in
http://lists.ebxml.org/archives/ebxml-dev/200205/msg00059.html.
Best regards,
--
Frankie Lam
Assistant Technology Officer
Center for E-Commerce Infrastructure Development (CECID)
Dept. of Computer Science and Information Systems
The University of Hong Kong
Tel: (852) 22415737
Fax: (852) 25474611
P.S. This message is cc'ed to the ebxmlms-general list.
----- Original Message -----
From: "simon carni" <sim...@ho...>
To: <ts...@ce...>
Sent: Wednesday, November 13, 2002 3:20 AM
Subject: Re: [ebxmlms-general] Malformed MessageServiceHandler URL
> Hi
> You haven't heard from me for a while. That's becouse i was smahing my had
> trying to find a couse to my problem and I think I've made some progress.
>
> If I construct an ebXML Message using Sun's implementaion of ebXML message
> and then send it with your MSH, then the Sun's jaxm provider gets the
> message and everything is done correctly. Here's the sample code:
> String cpaID = "CPA_2002";
> String conversationID = "Item_No_128";
> String service = "Purchase Order";
> String action = "Order";
>
>
> ApplicationContext ac = new ApplicationContext(
> cpaID, conversationID, service, action);
>
> String transportType = "HTTP";
> String toMshUrl = "http://localhost:8080/jaxm
> provider/receiver/ebxml";
>
>
> Request mshReq = new Request(
> ac, new URL(toMshUrl), null, transportType);
>
> /***********************************/
> /*** constructing a message using Sun's implementation ***/
> EbXMLMessageImpl ebxmlMsg= new EbXMLMessageImpl();
>
> ebxmlMsg.setSender(new Party("http://localhost:8080/msh"));
> ebxmlMsg.setReceiver(new
> Party("http://www.wombats.com/remote/sender"));
>
> Service service1 = new Service(service);
> ebxmlMsg.setRefToMessageId("200...@ex...");
> ebxmlMsg.setCPAId(cpaID);
> ebxmlMsg.setConversationId("20001209-133003-28572");
> ebxmlMsg.setService(service1);
> ebxmlMsg.setAction(action);
> Manifest manifest = new Manifest("manifest", "1.0");
> Reference ref = new Reference("pay01", "cid:pay01",
> "http://regrep.org/gci/purchaseorder");
>
> Schema schema = new Schema(
> "http://regrep.org/gci/purchaseorder.xsd",
> "1.0");
> ref.setSchema(schema);
>
> Description desc = new Description("en-us");
> desc.setText("PurchaseOrder for widgets");
> ref.setDescription(desc);
> manifest.addReference(ref);
> ebxmlMsg.setManifest(manifest);
>
> /********************************************************/
> /*** sending a message using your msh ***/
> /*** before that I have to create EbxmlMessage object ***/
> /*** (Sun's EbXMLMessageImpl extends SOAPMessage)**/
> hk.hku.cecid.phoenix.message.packaging.EbxmlMessage message = new
> hk.hku.cecid.phoenix.message.packaging.EbxmlMessage(ebxmlMsg);
>
> message.saveChanges();
> mshReq.send(message);
>
> That's it.
>
> So my guess is that Sun's message listener (or jaxm provider) doesn't
> recognize the messege creates with your implementation of ebXML Message.
> Or it might be a version thing, becouse Sun's implementation creates an
> ebXML message version 1.0. But I read somewhere that the compatibility
> shouldn't be a problem.
>
> Any ideas?
>
> Thank's
> Simon
>
>
>
>
>
>
>
>
> >From: "Frankie Lam" <ts...@ce...>
> >To: "simon carni" <sim...@ho...>
> >Subject: Re: [ebxmlms-general] Malformed MessageServiceHandler URL
> >Date: Fri, 8 Nov 2002 17:58:53 +0800
> >
> >Dear Simon,
> >
> >Thanks for the information. We suspect that there is some problem that
> >prevents Sun's implementation of JAXM provider to internalize the
> >ebxmlMessage generated by our MSH. Could you please attach the log files
of
> >Sun's JAXM provider here also? Thank you!
> >
> >Best regards,
> >
> >Frankie Lam
> >Assistant Technology Officer
> >Center for E-Commerce Infrastructure Development (CECID)
> >Dept. of Computer Science and Information Systems
> >The University of Hong Kong
> >Tel: (852) 22415737
> >Fax: (852) 25474611
> >
> >----- Original Message -----
> >From: "simon carni" <sim...@ho...>
> >To: <fr...@mi...>
> >Cc: <ebx...@li...>
> >Sent: Friday, November 08, 2002 5:07 PM
> >Subject: Re: [ebxmlms-general] Malformed MessageServiceHandler URL
> >
> >
> > > Hi,
> > >
> > > I will try to simplify
> > >
> > > I'm testing your MSH so i've set up the default conf. Then I run
> >RunMonitor.
> > > If I dont't change to MSH URL field averything works fine. But if
change
> >ut
> > > to the URL of client that uses another MSH or directly to another MSH
i
> >get
> > > mentioned exception. I'm using hermesMSH version 0.9.1.4. The other
MSH
> >is
> > > Sun's implementation jaxm provider Here's part of msh.log that might
be
> > > interesting to you:
> > >
> > > 2002-11-08 09:41:58,522 DEBUG [main]: Hermes (ebms2) MSH v.0.9.1.4
> >started.
> > > 2002-11-08 09:41:58,763 DEBUG [main]: Verifying the database tables
are
> > > properly installed...
> > > 2002-11-08 09:41:58,833 DEBUG [main]: Looks good.
> > > 2002-11-08 09:41:59,674 DEBUG [main]: Restart previous sending threads
> > > 2002-11-08 09:41:59,674 DEBUG [main]: Get delivery status of messages
> > > 2002-11-08 09:41:59,684 DEBUG [main]: Getting the sequence number of
> >sent
> > > messages
> > > 2002-11-08 09:41:59,684 DEBUG [main]: ConversationID: convid Max
> >Seq: -9999
> > > 2002-11-08 09:41:59,684 DEBUG [main]: ConversationID: Item_No_128 Max
> >Seq:
> > > -9999
> > > 2002-11-08 09:41:59,724 DEBUG [Thread-4]: Polling mail server: pop3,
> > > localhost, 110, INBOX, user
> > > 2002-11-08 09:43:33,088 DEBUG [HttpProcessor[8080][4]]: Received
request
> >for
> > > registering msh config
> > > 2002-11-08 09:43:33,088 DEBUG [HttpProcessor[8080][4]]: Update
MSHConfig
> > > 2002-11-08 09:43:33,098 DEBUG [main]: Diagnostic command: 5
> > > 2002-11-08 09:43:33,128 DEBUG [HttpProcessor[8080][3]]: Received
request
> >of
> > > enable ack.
> > > 2002-11-08 09:43:33,128 DEBUG [main]: Diagnostic command: 7
> > > 2002-11-08 09:43:33,148 DEBUG [HttpProcessor[8080][1]]: Received
request
> >of
> > > accept ack.
> > > 2002-11-08 09:43:49,532 DEBUG [HttpProcessor[8080][1]]: Received
request
> >for
> > > sending message
> > > 2002-11-08 09:43:50,153 DEBUG [HttpProcessor[8080][1]]: Final sequence
> > > number in store: -9999
> > > 2002-11-08 09:43:50,153 DEBUG [HttpProcessor[8080][1]]: Entering
> > > MessageServer.store
> > > 2002-11-08 09:43:50,163 DEBUG [HttpProcessor[8080][1]]:
> > > getRepositoryFileName return: R0000\aM24DNtzCG6xgLMPYpYI4g==
> > > 2002-11-08 09:43:50,163 DEBUG [HttpProcessor[8080][1]]: Insert into
> > > messagestore database
> > > 2002-11-08 09:43:50,243 DEBUG [Thread-6]: Send... try #1
> > > 2002-11-08 09:43:50,243 DEBUG [Thread-6]: Entering MessageServer.retry
> > > 2002-11-08 09:43:50,243 DEBUG [Thread-6]: Current: 0 specified: 1
> > > 2002-11-08 09:43:50,243 DEBUG [Thread-6]: Update state to become 1
> > > 2002-11-08 09:43:50,583 DEBUG [Thread-6]:
> > > hk.hku.cecid.phoenix.message.handler.HttpSender cannot send message
> > > successfully for 1 times:
> > > hk.hku.cecid.phoenix.message.transport.TransportException:
> > > java.security.PrivilegedActionException
<<javax.xml.soap.SOAPException:
> > > Unable to internalize message>>
> > > 2002-11-08 09:44:20,256 DEBUG [Thread-6]: Send... try #2
> > > 2002-11-08 09:44:20,256 DEBUG [Thread-6]: Entering MessageServer.retry
> > > 2002-11-08 09:44:20,256 DEBUG [Thread-6]: Current: 1 specified: 2
> > > 2002-11-08 09:44:20,256 DEBUG [Thread-6]: Update state to become 2
> > > 2002-11-08 09:44:20,276 DEBUG [Thread-6]:
> > > hk.hku.cecid.phoenix.message.handler.HttpSender cannot send message
> > > successfully for 2 times:
> > > hk.hku.cecid.phoenix.message.transport.TransportException:
> > > java.security.PrivilegedActionException
<<javax.xml.soap.SOAPException:
> > > Unable to internalize message>>
> > > 2002-11-08 09:44:20,436 DEBUG [Thread-6]: Final sequence number in
> >store:
> > > -9998
> > > 2002-11-08 09:44:20,436 DEBUG [Thread-6]: Entering MessageServer.store
> > > 2002-11-08 09:44:20,436 DEBUG [Thread-6]: getRepositoryFileName
return:
> > > R0000\KX-7va+2rpn5bw0pEMo-fQ==
> > > 2002-11-08 09:44:20,657 DEBUG [Thread-6]: Insert into reftomessage
> >database
> > > 2002-11-08 09:44:20,657 DEBUG [Thread-6]: Insert into messagestore
> >database
> > > 2002-11-08 09:44:20,687 DEBUG [Thread-6]: Entering MessageServer.retry
> > > 2002-11-08 09:44:20,687 DEBUG [Thread-6]: Current: 2 specified: -2
> > > 2002-11-08 09:44:20,687 DEBUG [Thread-6]: Update state to become -2
> > > 2002-11-08 09:44:33,195 DEBUG [HttpProcessor[8080][1]]: Key:
> > > R0000\KX-7va+2rpn5bw0pEMo-fQ==
> > > 2002-11-08 09:44:33,195 DEBUG [HttpProcessor[8080][1]]: File name:
> > > KX-7va+2rpn5bw0pEMo-fQ==
> > > 2002-11-08 09:44:33,205 DEBUG [HttpProcessor[8080][1]]: Normal return
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > >From: "Frankie Lam" <fr...@mi...>
> > > >To: "simon carni" <sim...@ho...>
> > > >CC: <ebx...@li...>
> > > >Subject: Re: [ebxmlms-general] Malformed MessageServiceHandler URL
> > > >Date: Fri, 8 Nov 2002 09:33:02 +0800
> > > >
> > > >Dear Simon,
> > > >
> > > >Can you attach your code here? And which version of MSH / Application
> > > >Server
> > > >are you using? Moreover, could you please tell us more about "the
other
> > > >msh"
> > > >that you are using?
> > > >
> > > >Best regards,
> > > >
> > > >Frankie Lam
> > > >Assistant Technology Officer
> > > >Center for E-Commerce Infrastructure Development (CECID)
> > > >Dept. of Computer Science and Information Systems
> > > >The University of Hong Kong
> > > >Tel: (852) 22415737
> > > >Fax: (852) 25474611
> > > >
> > > >----- Original Message -----
> > > >From: "simon carni" <sim...@ho...>
> > > >To: <kc...@ce...>; <ebx...@li...>
> > > >Sent: Friday, November 08, 2002 4:54 AM
> > > >Subject: Re: [ebxmlms-general] Malformed MessageServiceHandler URL
> > > >
> > > >
> > > > > thanks, I solved the problem but now I have a new one:
> > > > >
> > > > > While trying to send a message from your msh to other msh
> >(jaxm-provider
> > > > > from Sun) i get following exception:
> > > > >
> > > > > ******************************************
> > > > > javax.xml.soap.SOAPException: Invalid Content-Type:text/html
> > > > > 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(MessageFac
> >t
> > > >oryImpl.java:32)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConne
> >c
> > > >tion.java:333)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.ru
> >n
> > > >(HttpSOAPConnection.java:142)
> > > > > at java.security.AccessController.doPrivileged(Native Method)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConne
> >c
> > > >tion.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(MessageFac
> >t
> > > >oryImpl.java:32)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConne
> >c
> > > >tion.java:333)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.ru
> >n
> > > >(HttpSOAPConnection.java:142)
> > > > > at java.security.AccessController.doPrivileged(Native Method)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConne
> >c
> > > >tion.java:115)
> > > > > at hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown
> > > >Source)
> > > > > at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown
> >Source)
> > > > > java.security.PrivilegedActionException:
> >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(MessageFac
> >t
> > > >oryImpl.java:32)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConne
> >c
> > > >tion.java:333)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.ru
> >n
> > > >(HttpSOAPConnection.java:142)
> > > > > at java.security.AccessController.doPrivileged(Native Method)
> > > > > at
> > > > >
> > >
> >
>com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConne
> >c
> > > >tion.java:115)
> > > > > at hk.hku.cecid.phoenix.message.transport.HttpServlet.send(Unknown
> > > >Source)
> > > > > at hk.hku.cecid.phoenix.message.handler.HttpSender.run(Unknown
> >Source)
> > > > > *************************************************************
> > > > >
> > > > > I assume that happens on the "other side". I don't know if you are
> >the
> > > >right
> > > > > adress for this problem, but anyway. Any idea?
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > >From: "Patrick Yee" <kc...@ce...>
> > > > > >To: "EbXMLms List \(E-mail\)"
> ><ebx...@li...>
> > > > > >Subject: Re: [ebxmlms-general] Malformed MessageServiceHandler
URL
> > > > > >Date: Tue, 5 Nov 2002 09:28:53 +0800
> > > > > >
> > > > > >This time, it is the MSH Stub inside your client application who
is
> > > >finding
> > > > > >the msh.properties.xml. So, you should place the property file in
> >the
> > > > > >CLASSPATH or the working directory when/where you are invoking
the
> > > >client
> > > > > >application. This may be a separate copy of the property file
other
> > > >than
> > > > > >the
> > > > > >one in Tomcat. The one in Tomcat is for MSH server.
> > > > > >
> > > > > >Hope this helps.
> > > > > >
> > > > > >Regards, -Patrick
> > > > > >--
> > > > > >Patrick Yee
> > > > > >System Architect
> > > > > >Center for E-Commerce Infrastructure Development (CECID)
> > > > > >Dept. of Computer Science and Information Systems
> > > > > >The University of Hong Kong
> > > > > >Tel: (852) 22415674
> > > > > >Fax: (852) 25474611
> > > > > >
> > > > > > > Hi
> > > > > > >
> > > > > > > When I try to register my Application context (in a Servlet) I
> >get
> > > >the
> > > > > > > following exception Malformed MessageServiceHandler URL!. I
> >think
> > > >taht
> > > > > >the
> > > > > > > reason for this exc. is that msh.properties.xml file can't be
> >found.
> > > >So
> > > > > >I
> > > > > > > thinj the right question would be: where do I have to put
> > > > > >msh.properties.xml
> > > > > > > file if I'm running a MSH client as a Web App. I'm
> > > > > > > using Tomcat 4.0.4 and I've already tried to put it in :
> > > > > > > <TOMCAT_HOME>/classes
> > > > > > > <TOMCAT_HOME>/coomon/classes
> > > > > > > <TOMCAT_HOME>/bin
> > > > > > > myWebAppRoot/
> > > > > > > myWebAppRoot/WEB-INF
> > > > > > > myWebAppRoot/EWB-INF/classes
> > > > > > >
> > > > > > > None of thosed alternatives worked.
> > > > > > >
> > > > > > > Could you please help me.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Simon
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> >_________________________________________________________________
> > > > > > > Unlimited Internet access -- and 2 months free!?Try MSN.
> > > > > > > http://resourcecenter.msn.com/access/plans/2monthsfree.asp
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > -------------------------------------------------------
> > > > > > > This SF.net email is sponsored by: ApacheCon, November 18-21
in
> > > > > > > Las Vegas (supported by COMDEX), the only Apache event to be
> > > > > > > fully supported by the ASF. http://www.apachecon.com
> > > > > > > _______________________________________________
> > > > > > > ebxmlms-general mailing list
> > > > > > > ebx...@li...
> > > > > > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >-------------------------------------------------------
> > > > > >This SF.net email is sponsored by: ApacheCon, November 18-21 in
> > > > > >Las Vegas (supported by COMDEX), the only Apache event to be
> > > > > >fully supported by the ASF. http://www.apachecon.com
> > > > > >_______________________________________________
> > > > > >ebxmlms-general mailing list
> > > > > >ebx...@li...
> > > > > >https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> > > > >
> > > > >
> > > > > _________________________________________________________________
> > > > > The new MSN 8: advanced junk mail protection and 2 months FREE*
> > > > > http://join.msn.com/?page=features/junkmail
> > > > >
> > > > >
> > > > >
> > > > > -------------------------------------------------------
> > > > > This sf.net email is sponsored by: See the NEW Palm
> > > > > Tungsten T handheld. Power & Color in a compact size!
> > > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> > > > > _______________________________________________
> > > > > ebxmlms-general mailing list
> > > > > ebx...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> > > > >
> > > >
> > > >
> > > >
> > > >-------------------------------------------------------
> > > >This sf.net email is sponsored by: See the NEW Palm
> > > >Tungsten T handheld. Power & Color in a compact size!
> > > >http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> > > >_______________________________________________
> > > >ebxmlms-general mailing list
> > > >ebx...@li...
> > > >https://lists.sourceforge.net/lists/listinfo/ebxmlms-general
> > >
> > >
> > > _________________________________________________________________
> > > The new MSN 8: smart spam protection and 2 months FREE*
> > > http://join.msn.com/?page=features/junkmail
> > >
> > >
>
>
> _________________________________________________________________
> Add photos to your e-mail with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
>
|
