axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Hawkins <>
Subject Fw: [jira] Commented: (AXISCPP-136) Axis generates wrong response for response messages
Date Mon, 18 Oct 2004 08:16:21 GMT

Hi Folks,

as part of the planning of what we would like in 1.4 - I suggest we attempt
to reduce the number of outstanding major bugs (like the one below). In
order to track the bugs (and enhancements) that we want to fix in the
current release  (whatever that release may be) I suggest we set them as
"blocker" in JIRA. Any blockers should be fixed over and above other bugs
within the current release that is being worked on.

Does this seem sensible or do we need some other way of highlighting what
bugs we want to fix in a release? I haven't got around to changing the WIKI
yet but I would like to make it explicit in there what we are going to fix
in a release (but without pointing to individual bugs)

John Hawkins

----- Forwarded by John Hawkins/UK/IBM on 18/10/2004 09:12 -----
             18/10/2004 07:29            
             Please respond to                                     Subject 
              "Apache AXIS C           [jira] Commented: (AXISCPP-136)     
             Developers List"          Axis generates wrong response for   
                                       response messages                   

The following comment has been added to this issue:

     Author: Samisa Abeysinghe
    Created: Sun, 17 Oct 2004 11:29 PM
I *think* I know how to solve this. Basically there is an error on the
way complex objects are
serialized for RPC style on server side. (Not sure if the same apply
for the doc style)
This would prevent the Axis C++ server from interoperating with other
SOAP engines. (However it
works with Axis C++ clinets) This is *not* a client side problem, and
that is why C++ client can
work with Java server.

If we are to fix this we need to change not only the WSDL tool but also
the core serializer code
(namely SoapSerializer::addOutputCmplxParam and/or Param::serialize()
and the generated method for
complex types Axis_Serialize_ComplexTypeName) as per my understanding
as of now. However the
number of methods to be changed would expand as we go on fixing this.

I have been looking into the ways of providing a quick patch, however,
it is not possible to solve
the problem without changing the serializer code.

A fix would affect the client side, because at the moment the complex
type serialization is done using the same methods for both client and
server. In order to fix this issue we need to change the way how
serialization is done for server.
However at the moment both the SOAPSerializer and generated client code
uses the same  syntax/semantics for serializing, which
is incorrect)

It is too late and too risky to try and fix this for 1.3. However it is a
must that we fix this for 1.4

View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXISCPP-136
    Summary: Axis generates wrong response for response messages
       Type: Bug

     Status: Open
   Priority: Critical

    Project: Axis-C++
             1.1 Final
             1.2 Beta
             1.2 Alpha
             1.2 Final
             1.3 Beta

   Assignee: Samisa Abeysinghe
   Reporter: Marcus Tillmanns

    Created: Wed, 25 Aug 2004 3:22 AM
    Updated: Sun, 17 Oct 2004 11:29 PM
Environment: Windows 2000 Apache 2.50

Axis generates wrong response for well formed WSDL:

    <wsdl:message name="resumeJobResponse">
        <wsdl:part name="resumeJobReturn" type="s:JobState"/>

Instead of naming the return element "resumeJobReturn", Axis generates
"JobState", ignoring the correct Name of the part.

    <wsdl:message name="resumeJobResponse">
        <wsdl:part name="JobState" type="s:JobState"/>

Works, but only because now both (name and type) have the same name.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message