You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by Kartheek Hirode <ka...@centegy.com> on 2000/10/10 04:11:12 UTC
If port is not specified in the end-point URL....
Hello,
Wasn't this bug fixed? I see the Release Notes says it does.
But when I don't specify a port in the URL for rpcrouter, the
Call.invoke seems to bomb out.
But as soon as I specify 80, everything is hunky-dory.
Thanks,
KH
org.xml.sax.SAXParseException:
White space is required between the public identifier and the system
identifier.
at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
at
org.apache.xerces.framework.XMLDTDScanner.reportFatalXMLError(XMLDTDScanner.
java:645)
at
org.apache.xerces.framework.XMLDTDScanner.scanExternalID(XMLDTDScanner.java:
1190)
at
org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java
:1098)
at
org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDeclXMLDocumentSca
nner.java:2177)
at
org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.j
ava:2133)
at
org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
LDocumentScanner.java:775)
at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:380)
at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
at
org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
5)
at org.apache.soap.rpc.Call.invoke(Call.java:157)
Re: If port is not specified in the end-point URL....
Posted by George I Matkovits <ma...@uswest.net>.
In the header it is NOT fixed. It is OK with my URL connection within SSLSoap.
Regards - George
Kartheek Hirode wrote:
> Groan...
>
> I see its fixed in HTTPUtils. Btw, where is the second place?
> Thanks,
> KH
>
> -----Original Message-----
> From: George I Matkovits [mailto:matkovitsg@uswest.net]
> Sent: Wednesday, October 11, 2000 8:47 AM
> To: soap-dev@xml.apache.org
> Subject: Re: If port is not specified in the end-point URL....
>
> IMHO currently you MUST use a port number. It is only partially fixed in the
> current release. There were two places in the code which had to be patched
> but
> only the 1st one was actually done.
> Regards - George
>
> Kartheek Hirode wrote:
>
> > Hello,
> > Wasn't this bug fixed? I see the Release Notes says it does.
> > But when I don't specify a port in the URL for rpcrouter, the
> > Call.invoke seems to bomb out.
> >
> > But as soon as I specify 80, everything is hunky-dory.
> > Thanks,
> > KH
> >
> > org.xml.sax.SAXParseException:
> > White space is required between the public identifier and the system
> > identifier.
> > at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
> > at
> >
> org.apache.xerces.framework.XMLDTDScanner.reportFatalXMLError(XMLDTDScanner.
> > java:645)
> > at
> >
> org.apache.xerces.framework.XMLDTDScanner.scanExternalID(XMLDTDScanner.java:
> > 1190)
> > at
> >
> org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java
> > :1098)
> > at
> >
> org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDeclXMLDocumentSca
> > nner.java:2177)
> > at
> >
> org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.j
> > ava:2133)
> > at
> >
> org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
> > LDocumentScanner.java:775)
> > at
> >
> org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
> > java:380)
> > at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
> > at
> >
> org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
> > 5)
> > at org.apache.soap.rpc.Call.invoke(Call.java:157)
Re: If port is not specified in the end-point URL....
Posted by George I Matkovits <ma...@uswest.net>.
In the header it is NOT fixed. It is OK with my URL connection within SSLSoap.
Regards - George
Kartheek Hirode wrote:
> Groan...
>
> I see its fixed in HTTPUtils. Btw, where is the second place?
> Thanks,
> KH
>
> -----Original Message-----
> From: George I Matkovits [mailto:matkovitsg@uswest.net]
> Sent: Wednesday, October 11, 2000 8:47 AM
> To: soap-dev@xml.apache.org
> Subject: Re: If port is not specified in the end-point URL....
>
> IMHO currently you MUST use a port number. It is only partially fixed in the
> current release. There were two places in the code which had to be patched
> but
> only the 1st one was actually done.
> Regards - George
>
> Kartheek Hirode wrote:
>
> > Hello,
> > Wasn't this bug fixed? I see the Release Notes says it does.
> > But when I don't specify a port in the URL for rpcrouter, the
> > Call.invoke seems to bomb out.
> >
> > But as soon as I specify 80, everything is hunky-dory.
> > Thanks,
> > KH
> >
> > org.xml.sax.SAXParseException:
> > White space is required between the public identifier and the system
> > identifier.
> > at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
> > at
> >
> org.apache.xerces.framework.XMLDTDScanner.reportFatalXMLError(XMLDTDScanner.
> > java:645)
> > at
> >
> org.apache.xerces.framework.XMLDTDScanner.scanExternalID(XMLDTDScanner.java:
> > 1190)
> > at
> >
> org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java
> > :1098)
> > at
> >
> org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDeclXMLDocumentSca
> > nner.java:2177)
> > at
> >
> org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.j
> > ava:2133)
> > at
> >
> org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
> > LDocumentScanner.java:775)
> > at
> >
> org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
> > java:380)
> > at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
> > at
> >
> org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
> > 5)
> > at org.apache.soap.rpc.Call.invoke(Call.java:157)
RE: If port is not specified in the end-point URL....
Posted by Kartheek Hirode <ka...@centegy.com>.
Groan...
I see its fixed in HTTPUtils. Btw, where is the second place?
Thanks,
KH
-----Original Message-----
From: George I Matkovits [mailto:matkovitsg@uswest.net]
Sent: Wednesday, October 11, 2000 8:47 AM
To: soap-dev@xml.apache.org
Subject: Re: If port is not specified in the end-point URL....
IMHO currently you MUST use a port number. It is only partially fixed in the
current release. There were two places in the code which had to be patched
but
only the 1st one was actually done.
Regards - George
Kartheek Hirode wrote:
> Hello,
> Wasn't this bug fixed? I see the Release Notes says it does.
> But when I don't specify a port in the URL for rpcrouter, the
> Call.invoke seems to bomb out.
>
> But as soon as I specify 80, everything is hunky-dory.
> Thanks,
> KH
>
> org.xml.sax.SAXParseException:
> White space is required between the public identifier and the system
> identifier.
> at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
> at
>
org.apache.xerces.framework.XMLDTDScanner.reportFatalXMLError(XMLDTDScanner.
> java:645)
> at
>
org.apache.xerces.framework.XMLDTDScanner.scanExternalID(XMLDTDScanner.java:
> 1190)
> at
>
org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java
> :1098)
> at
>
org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDeclXMLDocumentSca
> nner.java:2177)
> at
>
org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.j
> ava:2133)
> at
>
org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
> LDocumentScanner.java:775)
> at
>
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
> java:380)
> at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
> at
>
org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
> 5)
> at org.apache.soap.rpc.Call.invoke(Call.java:157)
RE: If port is not specified in the end-point URL....
Posted by Kartheek Hirode <ka...@centegy.com>.
Groan...
I see its fixed in HTTPUtils. Btw, where is the second place?
Thanks,
KH
-----Original Message-----
From: George I Matkovits [mailto:matkovitsg@uswest.net]
Sent: Wednesday, October 11, 2000 8:47 AM
To: soap-dev@xml.apache.org
Subject: Re: If port is not specified in the end-point URL....
IMHO currently you MUST use a port number. It is only partially fixed in the
current release. There were two places in the code which had to be patched
but
only the 1st one was actually done.
Regards - George
Kartheek Hirode wrote:
> Hello,
> Wasn't this bug fixed? I see the Release Notes says it does.
> But when I don't specify a port in the URL for rpcrouter, the
> Call.invoke seems to bomb out.
>
> But as soon as I specify 80, everything is hunky-dory.
> Thanks,
> KH
>
> org.xml.sax.SAXParseException:
> White space is required between the public identifier and the system
> identifier.
> at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
> at
>
org.apache.xerces.framework.XMLDTDScanner.reportFatalXMLError(XMLDTDScanner.
> java:645)
> at
>
org.apache.xerces.framework.XMLDTDScanner.scanExternalID(XMLDTDScanner.java:
> 1190)
> at
>
org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java
> :1098)
> at
>
org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDeclXMLDocumentSca
> nner.java:2177)
> at
>
org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.j
> ava:2133)
> at
>
org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
> LDocumentScanner.java:775)
> at
>
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
> java:380)
> at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
> at
>
org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
> 5)
> at org.apache.soap.rpc.Call.invoke(Call.java:157)
Re: If port is not specified in the end-point URL....
Posted by George I Matkovits <ma...@uswest.net>.
IMHO currently you MUST use a port number. It is only partially fixed in the
current release. There were two places in the code which had to be patched but
only the 1st one was actually done.
Regards - George
Kartheek Hirode wrote:
> Hello,
> Wasn't this bug fixed? I see the Release Notes says it does.
> But when I don't specify a port in the URL for rpcrouter, the
> Call.invoke seems to bomb out.
>
> But as soon as I specify 80, everything is hunky-dory.
> Thanks,
> KH
>
> org.xml.sax.SAXParseException:
> White space is required between the public identifier and the system
> identifier.
> at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
> at
> org.apache.xerces.framework.XMLDTDScanner.reportFatalXMLError(XMLDTDScanner.
> java:645)
> at
> org.apache.xerces.framework.XMLDTDScanner.scanExternalID(XMLDTDScanner.java:
> 1190)
> at
> org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java
> :1098)
> at
> org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDeclXMLDocumentSca
> nner.java:2177)
> at
> org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.j
> ava:2133)
> at
> org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
> LDocumentScanner.java:775)
> at
> org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
> java:380)
> at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
> at
> org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
> 5)
> at org.apache.soap.rpc.Call.invoke(Call.java:157)
Re: If port is not specified in the end-point URL....
Posted by George I Matkovits <ma...@uswest.net>.
IMHO currently you MUST use a port number. It is only partially fixed in the
current release. There were two places in the code which had to be patched but
only the 1st one was actually done.
Regards - George
Kartheek Hirode wrote:
> Hello,
> Wasn't this bug fixed? I see the Release Notes says it does.
> But when I don't specify a port in the URL for rpcrouter, the
> Call.invoke seems to bomb out.
>
> But as soon as I specify 80, everything is hunky-dory.
> Thanks,
> KH
>
> org.xml.sax.SAXParseException:
> White space is required between the public identifier and the system
> identifier.
> at org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1008)
> at
> org.apache.xerces.framework.XMLDTDScanner.reportFatalXMLError(XMLDTDScanner.
> java:645)
> at
> org.apache.xerces.framework.XMLDTDScanner.scanExternalID(XMLDTDScanner.java:
> 1190)
> at
> org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java
> :1098)
> at
> org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDeclXMLDocumentSca
> nner.java:2177)
> at
> org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner.j
> ava:2133)
> at
> org.apache.xerces.framework.XMLDocumentScanner$XMLDeclDispatcher.dispatch(XM
> LDocumentScanner.java:775)
> at
> org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
> java:380)
> at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
> at
> org.apache.soap.util.xml.XercesParserLiaison.read(XercesParserLiaison.java:8
> 5)
> at org.apache.soap.rpc.Call.invoke(Call.java:157)