axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Andrade (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-4058) WSDL11ToAxisServiceBuilder: the wrapped attribute of the AxisMessage class is not being populated
Date Tue, 07 Oct 2008 14:53:44 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Antonio Andrade updated AXIS2-4058:
-----------------------------------

    Attachment: AXIS2-4058.patch

Patch to WSDL11ToAxisServiceBuilder class: populating the wrapped attribute of the AxisMessage
class while the bindings are being populated.

> WSDL11ToAxisServiceBuilder: the wrapped attribute of the AxisMessage class is not being
populated
> -------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4058
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4058
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.4, nightly
>         Environment: Windows XP. 4GB RAM Intel Xeon dual-core @2.75Ghz
>            Reporter: Antonio Andrade
>            Priority: Minor
>         Attachments: AXIS2-4058.patch
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> Observed Behavior: 
> 1) The wrapped attribute of the AxisMessage class is not being populated by the WSDL11ToAxisServiceBuilder
class. The information is persisted in its BindingOperationEntry inner class (through the
wrappedInput and wrappedOutput attributes) but it's never set into the appropriate AxisMessage
instance.
> 2) In AxisMessage, the wrapped attribute defaults to 'true' when it should not (see attribute
declaration/initialization). Note that BindingOperationEntry, the wrappedInput  and wrappedOutput
 attributes default to 'true'. This IS perfectly fine since BindingOperationEntry objects
are only instantiated whenever the encoding style for the operation is RPC/Literal of when
the binding is HTTP and the message parts reference type definitions so it's OK for them to
default to 'true'.
> Expected Behavior: 
> 1) The wrapped attribute of the AxisMessage class should be populated by the WSDL11ToAxisServiceBuilder
class while the bindings are being populated (see WSDL11ToAxisServiceBuilder.populateBinding
method) just before the addQNameReference methods are called.
> 2) In AxisMessage, the wrapped attribute should be initialized (either explicitly or
implicitly) to 'false' and the DocLitBareSchemaGenerator.processMethods method should be updated
accordingly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message