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
>
