axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glen Daniels <g...@thoughtcraft.com>
Subject Re: [jira] Closed: (AXIS-1186) SOAP headers can't be deserialized to Java objects if SOAP 1.2 is enforced
Date Tue, 23 Mar 2004 20:48:56 GMT
Hi dims,

TestHeaderAttrs doesn't test what he's talking about... the samples.echo
tests would test that though (when it does the echo header).  I wouldn't
close this just yet.

--Glen

----- Original Message ----- 
From: <jira@apache.org>
To: <axis-dev@ws.apache.org>
Sent: Tuesday, March 23, 2004 11:45 AM
Subject: [jira] Closed: (AXIS-1186) SOAP headers can't be deserialized to
Java objects if SOAP 1.2 is enforced


> Message:
>
>    The following issue has been closed.
>
>    Resolver: Davanum Srinivas
>        Date: Tue, 23 Mar 2004 8:45 AM
>
> Unable to recreate the problem. test.soap12.TestHeaderAttrs works fine.
> ---------------------------------------------------------------------
> View the issue:
>   http://issues.apache.org/jira/secure/ViewIssue.jspa?key=AXIS-1186
>
> Here is an overview of the issue:
> ---------------------------------------------------------------------
>         Key: AXIS-1186
>     Summary: SOAP headers can't be deserialized to Java objects if SOAP
1.2 is enforced
>        Type: Bug
>
>      Status: Closed
>  Resolution: CANNOT REPRODUCE
>
>     Project: Axis
>  Components:
>              Serialization/Deserialization
>    Versions:
>              current (nightly)
>
>    Assignee:
>    Reporter: Teemu Koponen
>
>     Created: Thu, 15 Jan 2004 9:36 AM
>     Updated: Tue, 23 Mar 2004 8:45 AM
> Environment: Operating System: Other
> Platform: Other
>
> Description:
> After enforcing the Axis generated client stubs to use SOAP 1.2 with
>
"_call.setSOAPVersion(org.apache.axis.soap.SOAPConstants.SOAP12_CONSTANTS);"
the
> Axis SOAP server side is no more able to deserialize them.  However, if
nothing
> else is changed, the very same client works if SOAP 1.1 is enforced.
>
> The SOAP request itself looks proper (checked with tcpmon) and in fact,
the
> server does have the headers as SOAPHeaderElement objects inside the
SOAPHeader
> object.  However, neither calling SOAPHeaderElement.getObjectValue(Class)
nor
> SOAPHeaderElement.getObValueAsType(QName) gives anything else than 'null'
for
> the caller.
>
>
> ---------------------------------------------------------------------
> JIRA INFORMATION:
> This message is automatically generated by JIRA.
>
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
>
> If you want more information on JIRA, or have a bug to report see:
>    http://www.atlassian.com/software/jira
>
>

Mime
View raw message