org.xml.sax.SAXException: Bad envelope tag: HTML
Hi All,
We are developing an application which is invoking Sharepoint Webservices.
Everyday during 1st unit test run we get the exeception below. Just ignoring
it and running the application once again, it works fine.
What is the cause of this error, which only occurs mostly during very 1st run
in a day?
Appreciate any help on this
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad envelope tag: HTML
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: Bad
envelope tag: HTML
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:71)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationC
ontext.java:1048)
at org.apache.crimson.parser.Parser2.maybeElement(Unknown Source)
at org.apache.crimson.parser.Parser2.parseInternal(Unknown Source)
at org.apache.crimson.parser.Parser2.parse(Unknown Source)
at org.apache.crimson.parser.XMLReaderImpl.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.
java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChec
ker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.microsoft.schemas.sharepoint.soap.AdminSoapStub.createSite(AdminSoapStub.
java:237)
at migration.client.MigrateWS.createSite(MigrateWS.java:284)
at migration.client.MigrateWS.traverseNodes(MigrateWS.java:125)
at migration.client.MigrateWS.parseDocument(MigrateWS.java:102)
at migration.client.MigrateWS.migrate(MigrateWS.java:70)
at migration.client.MigrateWS.main(MigrateWS.java:60)
{http://xml.apache.org/axis/}hostname:mabais-w2k
org.xml.sax.SAXException: Bad envelope tag: HTML
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChec
ker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
com.microsoft.schemas.sharepoint.soap.AdminSoapStub.createSite(AdminSoapStub.
java:237)
at migration.client.MigrateWS.createSite(MigrateWS.java:284)
at migration.client.MigrateWS.traverseNodes(MigrateWS.java:125)
at migration.client.MigrateWS.parseDocument(MigrateWS.java:102)
at migration.client.MigrateWS.migrate(MigrateWS.java:70)
at migration.client.MigrateWS.main(MigrateWS.java:60)
Caused by: org.xml.sax.SAXException: Bad envelope tag: HTML
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:71)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationC
ontext.java:1048)
Regards,
Mangesh Bais
P.S. We have used WSDL2Java tool of axis 1.4 for generating the client
classes
Re: Bad envelope tag : html
--- anil kumar [EMAIL PROTECTED] wrote:
Hi,
I have a service deployed on a secured server. When
I make a call to the
servcie I get the following error:
[12/14/05 8:43:53:948 EST] 615994 SystemErr R
AxisFault faultCode: {
*http://schemas.xmlsoap.org/soap/envelope/}Server.userException
*http://schemas.xmlsoap.org/soap/envelope/%7DServer.userExceptionfaultSubcode:
faultString: org.xml.sax.SAXException: Bad envelope
tag: HTML faultActor:
faultNode: faultDetail: { *
http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException*http://xml.apache.org/axis/%7DstackTrace:org.xml.sax.SAXException:
Bad envelope tag: HTML at
org.apache.axis.message.EnvelopeBuilder.startElement
(EnvelopeBuilder.java:71)
at
org.apache.axis.encoding.DeserializationContext.startElement(
DeserializationContext.java:1048) at
org.apache.xerces.parsers.AbstractSAXParser.startElement(
AbstractSAXParser.java:446) at
org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement
(
XMLNamespaceBinder.java:835) at
org.apache.xerces.impl.XMLNamespaceBinder.startElement(
XMLNamespaceBinder.java:568) at
org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:809)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement
(
XMLDocumentFragmentScannerImpl.java:752) at
org.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook
(XMLDocumentScannerImpl.java:950) at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(
XMLDocumentFragmentScannerImpl.java:1524) at
org.apache.xerces.impl.XMLDocum
entFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333)
at
org.apache.xerces.parsers.StandardParserConfiguration.parse(
StandardParserConfiguration.java :525) at
org.apache.xerces.parsers.StandardParserConfiguration.parse(
StandardParserConfiguration.java:581) at
org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:147)
at
org.apache.xerces.parsers.AbstractSAXParser.parse
(AbstractSAXParser.java:1158)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(
DeserializationContext.java:227) at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java
:696) at
org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(
MustUnderstandChecker.java:62) at
org.apache.axis.client.AxisClient.invoke(
AxisClient.java:206) at
org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at
org.apache.axis.client.Call.invoke(Call.java:2767)
at
org.apache.axis.client.Call.invoke(Call.java:2443)
at
org.apache.axis.client.Call.invoke(Call.java:2366)
at
org.apache.axis.client.Call.invoke(Call.java:1812)
at
agencyserviceClient.AgencySweepPaymentWebServiceSoapBindingStub.verifySweepPaymentEligibility(Unknown
Source) at
org.apache.jsp._AgencySweepInput._jspService(_AgencySweepInput.java:99)
at
com.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service(
JspServlet.java :365) at
com.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile(
JspServlet.java:715) at
com.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:813)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java
:853) at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(
StrictServletInstance.java :110) at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(
StrictLifecycleServlet.java:174) at
com.ibm.ws.webcontainer.servlet.IdleServletState.service
(
StrictLifecycleServlet.java:313) at
com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(
StrictLifecycleServlet.java:116) at
com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at
com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(
ValidServletReferenceState.java:42) at
com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(
ServletInstanceReference.java:40) at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(
WebAppRequestDispatcher.java:1073) at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(
WebAppRequestDispatcher.java:598) at
com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(
WebAppRequestDispatcher.java :206) at
com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:80)
at
com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(
WebAppInvoker.java:214) at
com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation
(
CachedInvocation.java:71) at
com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(
CacheableInvocationContext.java:116) at
com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(
ServletRequestProcessor.java :186
Re: Bad envelope tag : html
Hi Wade,
When i hit the URL (which is https), it pops up two security alerts related to certficates, then when i click 'yes' twice it shows the
Hi there, this is an AXIS service!
Any ideas?
Thanks
A
On 12/14/05, Wade Chandler [EMAIL PROTECTED] wrote:
--- anil kumar [EMAIL PROTECTED] wrote: Hi,
I have a service deployed on a secured server. When I make a call to the servcie I get the following error: [12/14/05 8:43:53:948 EST] 615994 SystemErr R AxisFault faultCode: {
*http://schemas.xmlsoap.org/soap/envelope/}Server.userException*
http://schemas.xmlsoap.org/soap/envelope/%7DServer.userExceptionfaultSubcode: faultString: org.xml.sax.SAXException: Bad envelope tag: HTML faultActor: faultNode: faultDetail: { *
http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException*
http://xml.apache.org/axis/%7DstackTrace:org.xml.sax.SAXException: Bad envelope tag: HTML at org.apache.axis.message.EnvelopeBuilder.startElement (EnvelopeBuilder.java:71) at
org.apache.axis.encoding.DeserializationContext.startElement( DeserializationContext.java:1048) atorg.apache.xerces.parsers.AbstractSAXParser.startElement( AbstractSAXParser.java:446) at
org.apache.xerces.impl.XMLNamespaceBinder.handleStartElement ( XMLNamespaceBinder.java:835) atorg.apache.xerces.impl.XMLNamespaceBinder.startElement( XMLNamespaceBinder.java:568) at
org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:809) atorg.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement ( XMLDocumentFragmentScannerImpl.java
:752) atorg.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook (XMLDocumentScannerImpl.java:950) atorg.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch
( XMLDocumentFragmentScannerImpl.java:1524) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:333) atorg.apache.xerces.parsers.StandardParserConfiguration.parse
( StandardParserConfiguration.java :525) atorg.apache.xerces.parsers.StandardParserConfiguration.parse( StandardParserConfiguration.java:581) atorg.apache.xerces.parsers.XMLParser.parse
(XMLParser.java:147) at org.apache.xerces.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:1158) at javax.xml.parsers.SAXParser.parse(Unknown Source) atorg.apache.axis.encoding.DeserializationContext.parse
( DeserializationContext.java:227) atorg.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java :696) atorg.apache.axis.Message.getSOAPEnvelope(Message.java:435) at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke( MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke( AxisClient.java:206) atorg.apache.axis.client.Call.invokeEngine
(Call.java:2784) at org.apache.axis.client.Call.invoke(Call.java:2767) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812) atagencyserviceClient.AgencySweepPaymentWebServiceSoapBindingStub.verifySweepPaymentEligibility(Unknown Source) at
org.apache.jsp._AgencySweepInput._jspService(_AgencySweepInput.java:99) atcom.ibm.ws.webcontainer.jsp.runtime.HttpJspBase.service(HttpJspBase.java:89) atjavax.servlet.http.HttpServlet.service
(HttpServlet.java:853) atcom.ibm.ws.webcontainer.jsp.servlet.JspServlet$JspServletWrapper.service( JspServlet.java :365) atcom.ibm.ws.webcontainer.jsp.servlet.JspServlet.serviceJspFile
( JspServlet.java:715) atcom.ibm.ws.webcontainer.jsp.servlet.JspServlet.service(JspServlet.java:813) atjavax.servlet.http.HttpServlet.service(HttpServlet.java :853) at
com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService( StrictServletInstance.java :110) atcom.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service( StrictLifecycleServlet.java
:174) atcom.ibm.ws.webcontainer.servlet.IdleServletState.service ( StrictLifecycleServlet.java:313) atcom.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service( StrictLifecycleServlet.java
:116) atcom.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283) atcom.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch( ValidServletReferenceState.java
:42) atcom.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch( ServletInstanceReference.java:40) atcom.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(
WebAppRequestDispatcher.java:1073) atcom.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch( WebAppRequestDispatcher.java:598) atcom.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward
( WebAppRequestDispatcher.java :206) atcom.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:80) atcom.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(
WebAppInvoker.java:214) atcom.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation ( CachedInvocation.java:71) atcom.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke
Bad envelope tag: html
Ron, Thanks ! It did solve the problem.
Now I am facing some other problem. ( Bad envelop tag problem).
Do you know about this ?
C:\Tomcat 5.5\webapps\axis\Simplejava -cp %AXISCLASSPATH% org.apache.axis.ct.AdminClient -lhttp://localhost:8080/axis/Simple Simple.wsddlog4j:WARN No appenders could be found for logger (
org.apache.axis.i18n.ProjesourceBundle).log4j:WARN Please initialize the log4j system properly.Processing file Simple.wsddException: AxisFaultfaultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.userExceptionfaultSubcode:faultString: org.xml.sax.SAXException: Bad envelope tag: htmlfaultActor:faultNode:faultDetail: {
http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: Bavelope tag: html at org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuiljava:70) at org.apache.axis.encoding.DeserializationContext.startElement
(DeseizationContext.java:1048) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknownce) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(own Source) at
org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatchcanRootElementHook(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentConDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocumenknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source at org.apache.xerces.parsers.XML11Configuration.parse
(Unknown Source at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse
(Unknownce) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.apache.axis.encoding.DeserializationContext.parse(DeserializaContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope
(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope(Message.java:424) at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSendava:796) at org.apache.axis.transport.http.HTTPSender.invoke
(HTTPSender.java:
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSendava:727) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStry.java:32) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118) at org.apache.axis.SimpleChain.invoke(SimpleChain.java
:83) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165) at org.apache.axis.client.Call.invokeEngine(Call.java:2765) at org.apache.axis.client.Call.invoke(Call.java:2748) at
org.apache.axis.client.Call.invoke(Call.java:1784) at org.apache.axis.client.AdminClient.process(AdminClient.java:439) at org.apache.axis.client.AdminClient.process(AdminClient.java:404) at
org.apache.axis.client.AdminClient.process(AdminClient.java:410) at org.apache.axis.client.AdminClient.process(AdminClient.java:320) at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
{http://xml.apache.org/axis/}hostname:IBM-900DE7D8334
On 10/5/05, Ron Reynolds [EMAIL PROTECTED] wrote:
there's a whitespace (space, CR, tab) in your classpath that's being interpretted by the java exe as a delimiter
between CP and the main class name.you might try quoting the whole CP( java -classpath %AXISCLASSPATH% ...) tho all those extra quotes might throw it off,or use the DOSified version of your directory name (TOMCAT~1.5) instead to avoid spaces.
or move your jars into a simple \dev\lib directory and use a classpath like this:set AXIS_CP=.set AXIS_CP=%AXIS_CP%;/dev/lib/axis-1.2.1.jarset AXIS_CP=%AXIS_CP%;/dev/lib/jaxrpc-1.1.jarset AXIS_CP=%AXIS_CP%;/dev/lib/commons-
logging-1.0.4.jarset AXIS_CP=%AXIS_CP%;/dev/lib/commons-discovery-0.2.jarset AXIS_CP=%AXIS_CP%;/dev/lib/wsdl4j-1.5.1.jarset AXIS_CP=%AXIS_CP%;/dev/lib/saaj-1.2.jarset AXIS_CP=%AXIS_CP%;/dev/lib/xmlsec-1.2.1.jar
set AXIS_CP=%AXIS_CP%;/dev/lib/junit-3.8.1.jar(jar names may vary - i add version numbers to all jars if they're missing)hth..ron. Has anybody seen this error before, if so what is the fix.
I am running Win XP.Here is my output of AXISCLASSPATH- . C:\Tomcat 5.5\webapps\axisecho %AXISCLASSPATH% C:\Tomcat 5.5\webapps\axis\WEB-INF\lib\axis.jar;C:\Tomcat
5.5\webapps\axis\WE B-INF\lib\commons-discovery.jar; C:\Tomcat 5.5\webapps\axis\WEB-INF\lib \comm ons-logging.jar;C:\Tomcat 5.5\webapps\axis\WEB-INF\lib\jaxrpc.jar;C:\Tomcat
5 .5\webapps\axis\WEB-INF\lib\saaj.jar; C:\Tomcat 5.5\webapps\axis\WEB-INF\lib \log4j-1.2.8.jar;C:\Tomcat 5.5\webapps\axis\WEB-INF\lib\xml-apis.jar ;C:\Tomca
t 5.5\webapps\axis\WEB-INF\lib\xercesImpl.jar Here is the output of running the Admin client- not sure why it is not working. C:\Tomcat 5.5\webapps\axisjava -cp %AXISCLASSPATH%
org.apache.axis.client.Admin Client -l ttp://localhost:8080/axis/Simple Simple.wsdd Exception in thread main java.lang.NoClassDefFoundError
: C:\Tomcat 5/5\webapps
Re: Bad envelope tag: html
the response you're getting back from the server is HTML, not SOAP. (also you
don't have a log4j.properties file in
your client's classpath, which is why you see that log4j:WARN No appenders
could be found ... error). if you do
create a log4j.properties file put this in it to get a dump of all out-going
and in-coming traffic:
log4j.rootCategory=DEBUG, LOGFILE
log4j.appender.CONSOLE =
org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout = org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern = %-4r [%t] %-5p %c %x - %m%n
log4j.appender.LOGFILE = org.apache.log4j.FileAppender
log4j.appender.LOGFILE.File = log4j.log
log4j.appender.LOGFILE.Append = true
log4j.appender.LOGFILE.Threshold= DEBUG
log4j.appender.LOGFILE.layout = org.apache.log4j.PatternLayout
log4j.appender.LOGFILE.layout.ConversionPattern = %-4r [%t] %-5p %c %x - %m%n
log4j.logger.org.apache.axis.transport.http.HTTPSender = DEBUG, CONSOLE
(the HttpSender category logs all incoming/outgoing traffic). sending all
debug to the console causes information
overload - but this will channel it all to a log4j.log file for later analysis.
oh, that error is from the AdminClient - are you running the Axis Servlet on
port 8080? also you don't need (or want)
that -l part - it defaults to http://localhost:8080/axis/servlet/AxisServlet;
so if your webapp is mapped to /axis
leave it off and it should work (as long as there's something like tomcat or
the axis simpleserver running on port
8080).
sorry for the detour above - i left it in this email as a future suggestion
(for those who want to make sense of their
request/responses without out all the clutter of a full DEBUG-to-CONSOLE
configuration).
ron.
Ron, Thanks ! It did solve the problem.
Now I am facing some other problem. ( Bad envelop tag problem).
Do you know about this ?
C:\Tomcat 5.5\webapps\axis\Simplejava -cp %AXISCLASSPATH% org.apache.axis.c
t.AdminClient -lhttp://localhost:8080/axis/Simple Simple.wsdd
log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.Proj
esourceBundle).
log4j:WARN Please initialize the log4j system properly.
Processing file Simple.wsdd
Exception: AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad envelope tag: html
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException: Ba
velope tag: html
at org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuil
java:70)
at org.apache.axis.encoding.DeserializationContext.startElement(Dese
izationContext.java:1048)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
ce)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(
own Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatch
canRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentCon
Dispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocumen
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
ce)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContext.parse(Deserializa
Context.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSend
ava:796)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSend
ava:727)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStr
y.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:1784)
at org.apache.axis.client.AdminClient.process(AdminClient.java:439)
at org.apache.axis.client.AdminClient.process(AdminClient.java:404)
at org.apache.axis.client.AdminClient.process(AdminClient.java:410)
at org.apache.axis.client.AdminClient.process(AdminClient.java:320)
at org.apache.axis.client.AdminClient.main(AdminClient.java:463)
{http
Re: Bad envelope tag: html
Ahah... I think the server returns an HTML document
with the results instead of a traditional response. I
would like to use AXIS to get this document. (The
service I am connecting to suggests NuSOAP for PHP.)
Are there any way to do this?
Thanks for everyone's help!
JR
--- Ron Reynolds [EMAIL PROTECTED] wrote:
i've seen this when i got redirected by an auth
filter and the auth server sent an HTML form
(assuming the client was
a browser) which, of course, doesn't parse as soap
very well. it may be your server is trying to
return some form of
HTML error page or perhaps a generated directory
listing (if the URL maps to a directory). relay
through tcp mon or
get the client-side to dump the response to log to
at least see what the client is getting.
hth.
.ron.
I have been working on using Apache Axis 1.2 to
interact with a Web Service that is using nuSOAP.
I
get the following error:
- Exception in AddressingHandler
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad
envelope
tag: html
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Bad envelope tag: html
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:70)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
What are the possible causes of this?
Thanks for the help,
JR
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Re: Bad envelope tag: html
depends on how much control you have over the server. to support both html and
soap responses i would add a seperate
handler/url on the server to return a soap response instead of html. or if you
want to use the same url you could add
a url parameter to dictate a soap response (and the lack of the parameter would
indicate html so as to not impact
current html clients). and if you have no control over the server you could
create your own custom client which would
have to parse the html (perhaps using jtidy to convert it to xml for easier
parsing). i don't think a custom
serializer on the client would work because i think there's a
soap-envelope-parsing layer between receiving the
response and invoking the deserializers, but i haven't delved into this piece
of axis yet, tho today i'm actually
starting on creating custom serializer/deserializers so if it turns out you can
handle the response as pure HTML i'll
let you know, tho i'm pretty sure at the very least the (de)serializers get a
DOM Document object which means the
response has already gone through an XML parser so if it's not well-formed html
(i.e., xhtml) it won't get past that
parser.
hth.
..ron.
Ahah... I think the server returns an HTML document
with the results instead of a traditional response. I
would like to use AXIS to get this document. (The
service I am connecting to suggests NuSOAP for PHP.)
Are there any way to do this?
Thanks for everyone's help!
JR
--- Ron Reynolds [EMAIL PROTECTED] wrote:
i've seen this when i got redirected by an auth
filter and the auth server sent an HTML form
(assuming the client was
a browser) which, of course, doesn't parse as soap
very well. it may be your server is trying to
return some form of
HTML error page or perhaps a generated directory
listing (if the URL maps to a directory). relay
through tcp mon or
get the client-side to dump the response to log to
at least see what the client is getting.
hth.
.ron.
I have been working on using Apache Axis 1.2 to
interact with a Web Service that is using nuSOAP.
I
get the following error:
- Exception in AddressingHandler
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad
envelope
tag: html
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Bad envelope tag: html
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:70)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
What are the possible causes of this?
Thanks for the help,
JR
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Re: Bad envelope tag: html
Unfortunately, I don't have much control over the
server. (It is owned by a different organization.)
I am doing this for part of a school project... if I
couldn't use Axis... what JAVA library or otherwise
would you suggest for getting the HTML response taken
care of? Basically, I'm only interested in getting a
client that I can get the correct output and
eventually be able to parse.
JR
--- Ron Reynolds [EMAIL PROTECTED] wrote:
depends on how much control you have over the
server. to support both html and soap responses i
would add a seperate
handler/url on the server to return a soap response
instead of html. or if you want to use the same url
you could add
a url parameter to dictate a soap response (and the
lack of the parameter would indicate html so as to
not impact
current html clients). and if you have no control
over the server you could create your own custom
client which would
have to parse the html (perhaps using jtidy to
convert it to xml for easier parsing). i don't
think a custom
serializer on the client would work because i think
there's a soap-envelope-parsing layer between
receiving the
response and invoking the deserializers, but i
haven't delved into this piece of axis yet, tho
today i'm actually
starting on creating custom serializer/deserializers
so if it turns out you can handle the response as
pure HTML i'll
let you know, tho i'm pretty sure at the very least
the (de)serializers get a DOM Document object which
means the
response has already gone through an XML parser so
if it's not well-formed html (i.e., xhtml) it won't
get past that
parser.
hth.
..ron.
Ahah... I think the server returns an HTML
document
with the results instead of a traditional
response. I
would like to use AXIS to get this document.
(The
service I am connecting to suggests NuSOAP for
PHP.)
Are there any way to do this?
Thanks for everyone's help!
JR
--- Ron Reynolds [EMAIL PROTECTED] wrote:
i've seen this when i got redirected by an auth
filter and the auth server sent an HTML form
(assuming the client was
a browser) which, of course, doesn't parse as
soap
very well. it may be your server is trying to
return some form of
HTML error page or perhaps a generated directory
listing (if the URL maps to a directory). relay
through tcp mon or
get the client-side to dump the response to log
to
at least see what the client is getting.
hth.
.ron.
I have been working on using Apache Axis 1.2 to
interact with a Web Service that is using
nuSOAP.
I
get the following error:
- Exception in AddressingHandler
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad
envelope
tag: html
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Bad envelope tag: html
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:70)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
What are the possible causes of this?
Thanks for the help,
JR
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Re: Bad envelope tag: html
once you get the HttpUrlConnection InputStream then you might consider running
it through a library like JTidy (
http://sourceforge.net/projects/jtidy ) to convert it to a DOM tree you can use.
in the case of a project i play with from time to time of gathering all the
dilbert images onto one page i found that
JTidy couldn't parse the HTML into XML (HTML can be so badly formatted only a
very forgiving browser can present it)
so i switched to using regular expressions to extract the specific lines i was
looking for and then reg-exp capture
groups to pick out the URLs i'm interested in. this also worked very well
writing a link-validator engine to find bad
links on web pages.
the problem very much depends on what the HTML you're getting back looks like.
and then what you want to extract from
it (URLs, particular strings, etc). and you always have to watch for the HTML
format being changed over time as it
may break your parser. and hope that the server doesn't use JavaScript or some
other scripting language to modify the
DOM at display time. also if you can convert the HTML into XML you can apply
XSLT to extract any parts you want quite
easily.
contact me directly if you have specific questions - i enjoy web-page scraping
projects. :)
...ron.
Unfortunately, I don't have much control over the
server. (It is owned by a different organization.)
I am doing this for part of a school project... if I
couldn't use Axis... what JAVA library or otherwise
would you suggest for getting the HTML response taken
care of? Basically, I'm only interested in getting a
client that I can get the correct output and
eventually be able to parse.
JR
--- Ron Reynolds [EMAIL PROTECTED] wrote:
depends on how much control you have over the
server. to support both html and soap responses i
would add a seperate
handler/url on the server to return a soap response
instead of html. or if you want to use the same url
you could add
a url parameter to dictate a soap response (and the
lack of the parameter would indicate html so as to
not impact
current html clients). and if you have no control
over the server you could create your own custom
client which would
have to parse the html (perhaps using jtidy to
convert it to xml for easier parsing). i don't
think a custom
serializer on the client would work because i think
there's a soap-envelope-parsing layer between
receiving the
response and invoking the deserializers, but i
haven't delved into this piece of axis yet, tho
today i'm actually
starting on creating custom serializer/deserializers
so if it turns out you can handle the response as
pure HTML i'll
let you know, tho i'm pretty sure at the very least
the (de)serializers get a DOM Document object which
means the
response has already gone through an XML parser so
if it's not well-formed html (i.e., xhtml) it won't
get past that
parser.
hth.
..ron.
Ahah... I think the server returns an HTML
document
with the results instead of a traditional
response. I
would like to use AXIS to get this document.
(The
service I am connecting to suggests NuSOAP for
PHP.)
Are there any way to do this?
Thanks for everyone's help!
JR
--- Ron Reynolds [EMAIL PROTECTED] wrote:
i've seen this when i got redirected by an auth
filter and the auth server sent an HTML form
(assuming the client was
a browser) which, of course, doesn't parse as
soap
very well. it may be your server is trying to
return some form of
HTML error page or perhaps a generated directory
listing (if the URL maps to a directory). relay
through tcp mon or
get the client-side to dump the response to log
to
at least see what the client is getting.
hth.
.ron.
I have been working on using Apache Axis 1.2 to
interact with a Web Service that is using
nuSOAP.
I
get the following error:
- Exception in AddressingHandler
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad
envelope
tag: html
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Bad envelope tag: html
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:70)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
What are the possible causes of this?
Thanks for the help,
JR
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
Re: Bad envelope tag: html
i've seen this when i got redirected by an auth filter and the auth server sent
an HTML form (assuming the client was
a browser) which, of course, doesn't parse as soap very well. it may be your
server is trying to return some form of
HTML error page or perhaps a generated directory listing (if the URL maps to a
directory). relay through tcp mon or
get the client-side to dump the response to log to at least see what the client
is getting.
hth.
.ron.
I have been working on using Apache Axis 1.2 to
interact with a Web Service that is using nuSOAP. I
get the following error:
- Exception in AddressingHandler
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad envelope
tag: html
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXException:
Bad envelope tag: html
at
org.apache.axis.message.EnvelopeBuilder.startElement(EnvelopeBuilder.java:70)
at
org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1048)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown
Source)
What are the possible causes of this?
Thanks for the help,
JR
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
org.xml.sax.SAXException: Bad envelope tag: html - What does it mean?
Hello,
i tested a Service which works fine yesterday but now
i get an AxisFault.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXException: Bad
envelope tag: html
faultActor:
faultNode:
faultDetail:
Any Ideas?
There are no changes at the wsdl file.
___
Produktion und Entwicklung
NEXNET GmbH
Am Borsigturm 12
13507 Berlin
Tel.:
+49 30 726297 411
Mail: [EMAIL PROTECTED]
