Menu
▾
▴
[ebxmlms-develop] Re: StatusRequest not working as intended (Bob Koon)
|
From: Rao Y. <ra...@ya...> - 2004-04-02 16:35:10
|
Bob you are correct . all the while i was thinking there were duplicate declarations of status cpaId, service et. al. that was the reason i suggested for a return inside. but just went thru the code and found that they are declared right at the start of the method. -Venkat ebx...@li... wrote: Send ebxmlms-develop mailing list submissions to ebx...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop or, via email, send a message with subject or body 'help' to ebx...@li... You can reach the person managing the list at ebx...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of ebxmlms-develop digest..." Today's Topics: 1. Re: StatusRequest not working as intended (Bob Koon) 2. Re: Error from build of latest source code , HTTP response code = 409 (Bob Koon) 3. Re: Problems with MIME headers on error messages (Bob Koon) 4. Re: Problems with MIME headers on error messages (Bob Koon) 5. Re: Problems receiving error messages (Bob Koon) --__--__-- Message: 1 Date: Thu, 01 Apr 2004 15:41:08 +0800 From: Bob Koon To: ebx...@li... Subject: Re: [ebxmlms-develop] StatusRequest not working as intended Reply-To: ebx...@li... Thanks for your suggestion. However I cannot get out the different on adding the return statement. The rough logic flow of MessageServer.getMessageStatus() is as following String[] getMessageStatus() { // ... set all things null try { // do some query. if (!resultSet.next()) { //return error status. } else { //set those response... // <- where you suggest on adding the return statement. } } catch (MessageServerException e) { //mark down exception } catch (Exception e) { //mark down exception } finally { //throw exception } return new String[] {status, timestamp, cpaid, conversationId, service, action}; } I cannot figure out the different if there exist/doesn't exist the return statement, since if it flows to the else part, it will finally flow to the last return statement. Regards, Bob Koon Yerubandi Rao wrote: >All, >with the build from the latest cvs source code , i found out that StatusRequest is not working as intended. i think i have figured out the problem . >i am including a patch for the fix . > > >Index: MessageServer.java >=================================================================== >retrieving revision 1.149 >diff -u -r1.149 MessageServer.java >--- MessageServer.java 10 Feb 2004 03:12:52 -0000 1.149 >+++ MessageServer.java 1 Apr 2004 01:19:18 -0000 >@@ -1969,7 +1969,13 @@ > status = Constants.STATUS_PROCESSED; > } else { > status = Constants.STATUS_UN_AUTHORIZED; >- } >+ } >+ // local variables ( status, timestamp, cpaId, conversationId, service, action) >+ // are initialized in this block and a return is being made outside the block, >+ // .. so if the below return statement is not present , always String[] of nulls will be >+ // returned and the correct StatusResponse will not be generated >+ return new String[]{status, timestamp, cpaId, conversationId, >+ service, action}; > } > } catch (MessageServerException e) { > exception = e; >@@ -1993,8 +1999,8 @@ > if (exception != null) { > throw new MessageServerException(exception.getMessage()); > } >- >- logger.debug("<= MessageServer.getMessageStatus"); >+ >+ logger.debug("<= MessageServer.getMessageStatus"); > } > return new String[]{status, timestamp, cpaId, conversationId, > service, action}; > <> > >-Venkat > > --__--__-- Message: 2 Date: Thu, 01 Apr 2004 15:42:45 +0800 From: Bob Koon To: ebx...@li... Subject: Re: [ebxmlms-develop] Error from build of latest source code , HTTP response code = 409 Reply-To: ebx...@li... Thanks for your reporting. I need some time to fix it, so I will reply=20 when I fixed it up. Regards, Bob Koon Yerubandi Rao wrote: >All, >i got the latest hermes code from CVS and deployed it on JBoss. when i t= ry to send a simple request i get the following error=20 > > >Message: Cannot parse SOAP message >10:55:21,810 ERROR [STDERR] hk.hku.cecid.phoenix.message.handler.Request= Exceptio >n: >Fail to send EbxmlMessage to MessageServiceHandler: > HTTP response code =3D 409 > HTTP response message =3D [10008] HTTP POST request failed - [10002] U= nknown err >or Exception: java.io.IOException Message: [10002] Unknown error Excepti= on: java >x.xml.soap.SOAPException Message: Cannot parse SOAP message >10:55:21,870 ERROR [STDERR] at hk.hku.cecid.phoenix.message.handler.= Request. >sendMessage(Request.java:1712) >10:55:21,880 ERROR [STDERR] at hk.hku.cecid.phoenix.message.handler.= Request. >send(Request.java:1173) >10:55:21,900 ERROR [STDERR] at Ping.runPing(Ping.java:554) >10:55:21,910 ERROR [STDERR] at Ping.doPost(Ping.java:45) >10:55:21,920 ERROR [STDERR] at Ping.doGet(Ping.java:31) >10:55:21,930 ERROR [STDERR] at javax.servlet.http.HttpServlet.servic= e(HttpSe >rvlet.java:740) >10:55:21,930 ERROR [STDERR] at javax.servlet.http.HttpServlet.servic= e(HttpSe >rvlet.java:853) >10:55:21,930 ERROR [STDERR] at org.apache.catalina.core.ApplicationF= ilterCha >in.internalDoFilter(ApplicationFilterChain.java:247) >10:55:21,930 ERROR [STDERR] at org.apache.catalina.core.ApplicationF= ilterCha >in.doFilter(ApplicationFilterChain.java:193) >10:55:21,930 ERROR [STDERR] at org.apache.catalina.core.StandardWrap= perValve >.invoke(StandardWrapperValve.java:256) >10:55:21,930 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:643) >10:55:22,020 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line.inv >oke(StandardPipeline.java:480) >10:55:22,020 ERROR [STDERR] at org.apache.catalina.core.ContainerBas= e.invoke >(ContainerBase.java:995) >10:55:22,020 ERROR [STDERR] at org.apache.catalina.core.StandardCont= extValve >.invoke(StandardContextValve.java:191) >10:55:22,080 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:643) >10:55:22,080 ERROR [STDERR] at org.jboss.web.tomcat.security.JBossSe= curityMg >rRealm.invoke(JBossSecurityMgrRealm.java:220) >10:55:22,080 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:641) >10:55:22,080 ERROR [STDERR] at org.apache.catalina.valves.Certificat= esValve. >invoke(CertificatesValve.java:246) >10:55:22,080 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:641) >10:55:22,080 ERROR [STDERR] at org.jboss.web.tomcat.tc4.statistics.C= ontainer >StatsValve.invoke(ContainerStatsValve.java:76) >10:55:22,171 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:641) >10:55:22,171 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line.inv >oke(StandardPipeline.java:480) >10:55:22,181 ERROR [STDERR] at org.apache.catalina.core.ContainerBas= e.invoke >(ContainerBase.java:995) >10:55:22,221 ERROR [STDERR] at org.apache.catalina.core.StandardCont= ext.invo >ke(StandardContext.java:2417) >10:55:22,231 ERROR [STDERR] at org.apache.catalina.core.StandardHost= Valve.in >voke(StandardHostValve.java:180) >10:55:22,231 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:643) >10:55:22,231 ERROR [STDERR] at org.apache.catalina.valves.ErrorDispa= tcherVal >ve.invoke(ErrorDispatcherValve.java:171) >10:55:22,231 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:641) >10:55:22,231 ERROR [STDERR] at org.apache.catalina.valves.ErrorRepor= tValve.i >nvoke(ErrorReportValve.java:172) >10:55:22,321 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:641) >10:55:22,321 ERROR [STDERR] at org.jboss.web.tomcat.security.Securit= yAssocia >tionValve.invoke(SecurityAssociationValve.java:65) >10:55:22,321 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:641) >10:55:22,321 ERROR [STDERR] at org.apache.catalina.valves.AccessLogV= alve.inv >oke(AccessLogValve.java:577) >10:55:22,391 INFO [MessageServiceHandler] Process command: Get message = (32) >10:55:22,401 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:641) >10:55:22,401 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line.inv >oke(StandardPipeline.java:480) >10:55:22,401 ERROR [STDERR] at org.apache.catalina.core.ContainerBas= e.invoke >(ContainerBase.java:995) >10:55:22,401 ERROR [STDERR] at org.apache.catalina.core.StandardEngi= neValve. >invoke(StandardEngineValve.java:174) >10:55:22,401 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line$Sta >ndardPipelineValveContext.invokeNext(StandardPipeline.java:643) >10:55:22,401 ERROR [STDERR] at org.apache.catalina.core.StandardPipe= line.inv >oke(StandardPipeline.java:480) >10:55:22,501 ERROR [STDERR] at org.apache.catalina.core.ContainerBas= e.invoke >(ContainerBase.java:995) >10:55:22,501 ERROR [STDERR] at org.apache.coyote.tomcat4.CoyoteAdapt= er.servi >ce(CoyoteAdapter.java:197) >10:55:22,501 ERROR [STDERR] at org.apache.coyote.http11.Http11Proces= sor.proc >ess(Http11Processor.java:781) >10:55:22,501 ERROR [STDERR] at org.apache.coyote.http11.Http11Protoc= ol$Http1 >1ConnectionHandler.processConnection(Http11Protocol.java:549) >10:55:22,501 ERROR [STDERR] at org.apache.tomcat.util.net.TcpWorkerT= hread.ru >nIt(PoolTcpEndpoint.java:605) >10:55:22,501 ERROR [STDERR] at org.apache.tomcat.util.threads.Thread= Pool$Con >trolRunnable.run(ThreadPool.java:677) > >After digging thru the code i found that the headers passed to >MessageFactory.newInstance().createMessage() have no=20 >Content-Type set. Hence an exception ( Absent Content-type ) is being t= hrown and it is being re-thrown as an >SOAPException ( " Cannot parse SOAP message") >Line 1677 : EbxmlMessage.java=20 >-Venkat > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk >_______________________________________________ >ebxmlms-develop mailing list >ebx...@li... >https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop > > > =20 > --__--__-- Message: 3 Date: Thu, 01 Apr 2004 15:45:12 +0800 From: Bob Koon To: ebx...@li... Subject: Re: [ebxmlms-develop] Problems with MIME headers on error messages Reply-To: ebx...@li... This is a multi-part message in MIME format. --------------010409050709090407040600 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Thanks for your reporting. I need some time have a good trace on the why the mime header from the parseOutput won't works, and will reply you all if I fixed it up. Regards, Bob Koon Mayne, Peter wrote: > I'm using Hermes pulled from CVS this morning. > > When I receive an error message, Hermes couldn't build the bytes into > a SOAP message. I tracked this down to > EbxmlMessage.getMessageFromDataSource(), which contains: > > /* > final MimeHeaders headers = new MimeHeaders(); > headers.addHeader(Constants.CONTENT_TYPE, > Constants.TEXT_XML_TYPE); > */ > final MimeHeaders headers = parsedOutput.getMimeHeaders(); > > It seems that parsedOutput.getMimeHeaders() doesn't work properly: it > wasn't producing any headers, so building the SOAP message was failing > with a "no content-type" exception. > > Going back to the predefined header by switching the comments around: > > final MimeHeaders headers = new MimeHeaders(); > headers.addHeader(Constants.CONTENT_TYPE, > Constants.TEXT_XML_TYPE); > /* > final MimeHeaders headers = parsedOutput.getMimeHeaders(); > */ > > now the message builds properly. > > PJDM > -- > Peter Mayne > Technology Consultant > Spherion Technology Solutions > Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 > T: 61 2 62689727 F: 61 2 62689777 > > > > > > --------------010409050709090407040600 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ns.csis.hku.hk id i317f4N7007569 content=3D"text/html;charset=3Dwindows-1252"> Thanks for your reporting. I need some time have a good trace on the why the mime header from the parseOutput won't works, and will reply you all if I fixed it up. Regards, Bob Koon Mayne, Peter wrote: cite=3D"mid...@s-...= m.au"> content=3D"MS Exchange Server version 5.5.2654.45"> I'm using Hermes pulled from CVS this morning.t> When I receive an error message, Hermes couldn't build the bytes into a SOAP message. I tracked this down to EbxmlMessage.getMessageFromDataSource(), which contains: =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 final MimeHeaders he= aders =3D new MimeHeaders(); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 headers.addHeader(Co= nstants.CONTENT_TYPE, Constants.TEXT_XML_TYPE); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 */ =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 final MimeHeaders he= aders =3D parsedOutput.getMimeHeaders(); It seems that parsedOutput.getMimeHeaders() doesn't work properly: it wasn't producing any headers, so building the SOAP message was failing with a "no content-type" exception. Going back to the predefined header by switching the comments around: =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 final MimeHeaders= headers =3D new MimeHeaders(); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 headers.addHeader(Co= nstants.CONTENT_TYPE, Constants.TEXT_XML_TYPE); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 final MimeHeaders he= aders =3D parsedOutput.getMimeHeaders(); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 */ now the message builds properly. PJDM -- Peter Mayne Technology Consultant Spherion Technology Solutions Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602ont> T: 61 2 62689727=A0 F: 61 2 62689777 =A0 ff"> =A0 --------------010409050709090407040600-- --__--__-- Message: 4 Date: Thu, 01 Apr 2004 16:45:40 +0800 From: Bob Koon To: ebx...@li... CC: Yer...@su... Subject: Re: [ebxmlms-develop] Problems with MIME headers on error messages Reply-To: ebx...@li... This is a multi-part message in MIME format. --------------090905060800070208050808 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit I have just fixed the bug and committed it to CVS. (Include adding unit test case) However, since the sourceforge's CVS doesn't work quite stable (when I commit, I see that it cannot generate acknowledgment to the mailing list... and from previous experience, the user may not checkout the latest version just after I committed), therefore you may not able check it out from CVS. Thanks for reporting those bugs. Regards, Bob Koon Mayne, Peter wrote: > I'm using Hermes pulled from CVS this morning. > > When I receive an error message, Hermes couldn't build the bytes into > a SOAP message. I tracked this down to > EbxmlMessage.getMessageFromDataSource(), which contains: > > /* > final MimeHeaders headers = new MimeHeaders(); > headers.addHeader(Constants.CONTENT_TYPE, > Constants.TEXT_XML_TYPE); > */ > final MimeHeaders headers = parsedOutput.getMimeHeaders(); > > It seems that parsedOutput.getMimeHeaders() doesn't work properly: it > wasn't producing any headers, so building the SOAP message was failing > with a "no content-type" exception. > > Going back to the predefined header by switching the comments around: > > final MimeHeaders headers = new MimeHeaders(); > headers.addHeader(Constants.CONTENT_TYPE, > Constants.TEXT_XML_TYPE); > /* > final MimeHeaders headers = parsedOutput.getMimeHeaders(); > */ > > now the message builds properly. > > PJDM > -- > Peter Mayne > Technology Consultant > Spherion Technology Solutions > Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 > T: 61 2 62689727 F: 61 2 62689777 > > > > > > --------------090905060800070208050808 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ns.csis.hku.hk id i318fWN7010570 content=3D"text/html;charset=3Dwindows-1252"> I have just fixed the bug and committed it to CVS. (Include adding unit test case) However, since the sourceforge's CVS doesn't work quite stable (when I commit, I see that it cannot generate acknowledgment to the mailing list... and from previous experience, the user may not checkout the latest version just after I committed), therefore you may not able check it out from CVS. Thanks for reporting those bugs. Regards, Bob Koon Mayne, Peter wrote: cite=3D"mid...@s-...= m.au"> content=3D"MS Exchange Server version 5.5.2654.45"> I'm using Hermes pulled from CVS this morning.t> When I receive an error message, Hermes couldn't build the bytes into a SOAP message. I tracked this down to EbxmlMessage.getMessageFromDataSource(), which contains: =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 final MimeHeaders he= aders =3D new MimeHeaders(); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 headers.addHeader(Co= nstants.CONTENT_TYPE, Constants.TEXT_XML_TYPE); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 */ =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 final MimeHeaders he= aders =3D parsedOutput.getMimeHeaders(); It seems that parsedOutput.getMimeHeaders() doesn't work properly: it wasn't producing any headers, so building the SOAP message was failing with a "no content-type" exception. Going back to the predefined header by switching the comments around: =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 final MimeHeaders= headers =3D new MimeHeaders(); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 headers.addHeader(Co= nstants.CONTENT_TYPE, Constants.TEXT_XML_TYPE); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 /* =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 final MimeHeaders he= aders =3D parsedOutput.getMimeHeaders(); =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 */ now the message builds properly. PJDM -- Peter Mayne Technology Consultant Spherion Technology Solutions Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602ont> T: 61 2 62689727=A0 F: 61 2 62689777 =A0 ff"> =A0 --------------090905060800070208050808-- --__--__-- Message: 5 Date: Thu, 01 Apr 2004 17:29:44 +0800 From: Bob Koon To: ebx...@li... Subject: Re: [ebxmlms-develop] Problems receiving error messages Reply-To: ebx...@li... This is a multi-part message in MIME format. --------------060900060807080509000409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit The problem is due to my code fault when I try to make the send with registeration part feature.... will be fixed ASAP. Regards, Bob Koon Mayne, Peter wrote: > I'm using Hermes pulled from CVS this morning. > > When I receive an error message (action "MessageError" with an > in the header), I'm getting null pointer exceptions. > > So far, I've tracked it down to MessageServiceHandler.dispatchMessage(): > > if (isError) { > logger.debug("Error message received"); > final String refToMessageId = > ebxmlMessage.getMessageHeader(). > getRefToMessageId(); > logger.debug("RefToMessageId: " + refToMessageId); > if (refToMessageId != null) { > final ApplicationContext refToAppContext = > > messageServer.getApplicationContext(refToMessageId, tx); > if (refToAppContext != null) { > appContext = refToAppContext; > mshConnection = (appContext == null ? null : > > (MessageServiceHandlerConnection) > > mshConnectionTable.get(appContext)); > > At this point, appContext is "appContext > =cecid:send_generate_cpaid, > =0.7193359494581163, =0.40606018618039663, > =0.01091177446510061", and mshConnection is null. > > Near the end of dispatchMessage(), there is this code: > > Delivery delivery = new Delivery(this, appContext, > mshConnection.getMessageServiceHandlerConfig(). > getMessageListener(), ebxmlMessage); > > Because mshConnection is null, I get a NullPointerException. > > I'm not sure which direction I should go in from here. Any clues? > > Thanks. > > PJDM > -- > Peter Mayne > Technology Consultant > Spherion Technology Solutions > Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 > T: 61 2 62689727 F: 61 2 62689777 > > > > > > --------------060900060807080509000409 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit The problem is due to my code fault when I try to make the send with registeration part feature.... will be fixed ASAP. Regards, Bob Koon Mayne, Peter wrote: cite="mid...@s-..."> content="MS Exchange Server version 5.5.2654.45"> I'm using Hermes pulled from CVS this morning. When I receive an error message (action "MessageError" with an <eb:ErrorList> in the header), I'm getting null pointer exceptions. So far, I've tracked it down to MessageServiceHandler.dispatchMessage(): if (isError) { logger.debug("Error message received"); final String refToMessageId = ebxmlMessage.getMessageHeader(). getRefToMessageId(); logger.debug("RefToMessageId: " + refToMessageId); if (refToMessageId != null) { final ApplicationContext refToAppContext = messageServer.getApplicationContext(refToMessageId, tx); if (refToAppContext != null) { appContext = refToAppContext; mshConnection = (appContext == null ? null : (MessageServiceHandlerConnection) mshConnectionTable.get(appContext)); At this point, appContext is "appContext <CPAId>=cecid:send_generate_cpaid, <ConversationId>=0.7193359494581163, <Service>=0.40606018618039663, <Action>=0.01091177446510061", and mshConnection is null. Near the end of dispatchMessage(), there is this code: Delivery delivery = new Delivery(this, appContext, mshConnection.getMessageServiceHandlerConfig(). getMessageListener(), ebxmlMessage); Because mshConnection is null, I get a NullPointerException. I'm not sure which direction I should go in from here. Any clues? Thanks. PJDM -- Peter Mayne Technology Consultant Spherion Technology Solutions Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 T: 61 2 62689727 F: 61 2 62689777 --------------060900060807080509000409-- --__--__-- _______________________________________________ ebxmlms-develop mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop End of ebxmlms-develop Digest --------------------------------- Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway - Enter today |
