[ 
https://issues.apache.org/jira/browse/AXIS2-4272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693810#action_12693810
 ] 

Ed Komp commented on AXIS2-4272:
--------------------------------

There are a few related JIRA's that indicate that the handling of WS-Policy for 
WSDL 1.1 input
is not handled completely.
It would be great if these issues were addressed as well:

JIRA AXIS2-4065  
Policy attached to an input operation in a WSDL does not get copied to the Stub 
operation by WSDL2Java

This JIRA is well-documented and summarizes that
"Policy that is attached at the binding element gets passed by the client stub 
code to the operation, but policy that is attached to the message at 
wsdl:binding/wsdl:operation/wsdl:input does not. "

and closely related,
JIRA  AXIS2-4150
Message level policies are not added to wsdl2

The following which is perhaps less critical describes another method of 
attaching WS-Policy in WSDL that is not 
incorporated into the client stub.
JIRA AXIS2-3915
Policies attached using the wsp:PolicyURIs attribute are not included in the 
code generated Stub

I'm sorry to make the task just bigger.
If I can be assistance in developing a solution, please contact me.
I'm very interested in the complete transfer of WS-Policy from the WSDL to 
client stub.

thanks
Ed Komp



> Service stub missing WS-Policy information when codegen with WSDL20.
> --------------------------------------------------------------------
>
>                 Key: AXIS2-4272
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4272
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: codegen
>         Environment: jdk1.5 / ubuntu hardy
>            Reporter: Pradeep Fernando
>            Priority: Minor
>
> When codegen the service stub using WSDL20 the stub excludes any ws-policy 
> Information given in the WSDL.
> This is because the support is not yet implemented for WSDL20.(In the TODO 
> list).
> It works fine given a WSDL11.

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

Reply via email to