Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <288053265.1217579792383.JavaMail.jira@brutus>
Date: Fri, 1 Aug 2008 01:36:32 -0700 (PDT)
From: "Nandana Mihindukulasooriya (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Resolved: (AXIS2-3907) Message level policy not serialized
 correctly in wsdl 1.1
In-Reply-To: <1155958425.1216025853138.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nandana Mihindukulasooriya resolved AXIS2-3907.
-----------------------------------------------

    Resolution: Fixed

> Message level policy not serialized correctly in wsdl 1.1
> ---------------------------------------------------------
>
>                 Key: AXIS2-3907
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3907
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.4
>         Environment: any
>            Reporter: Stefan Vladov
>            Assignee: Sanka Samaranayake
>             Fix For: 1.4.1
>
>         Attachments: AxisService2WSDL11_message_policy.txt, TestEcho2.wsdl, TestEcho2Result.wsdl
>
>
> AxisService2WSDL11 serializes a policy reference attached on the message (in or out message) at the input (respectively output) of the wsdl operation in the portType definition. This essentially happens in the generatePortType method that is calling 
> addPolicyAsExtElement(inaxisMessage, input) 
> (respectively 
> addPolicyAsExtElement(outAxisMessage, output)
>  for the output). On the other hand the WSDL11ToAxisServiceBuilder expects to find the eventual policy at the message declaration in the wsdl definition. Examining the
> WSDL11ToAxisServiceBuilder #populateOperations
>  when calling 
> copyExtensibleElements
>  for the respective message the builder passes 
> message.getExtensibilityElements()
>  instead of for example 
> wsdl4jInputMessage.getExtensibilityElements()
> (which would get the policy reference from the Input rather than from the message declaration.) As a result the message level policy is not read from the wsdl generated by the same engine.
> I'm not sure which is the right place for the message policy (probably both are right) or whether there is a recommendation about this but it would be nice to have the policy reference deserialized from and serialized at the same place - for example at the message declaration. I'll attach a patch if you like the proposal...

-- 
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