axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nandana Mihindukulasooriya (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-3105) WSDL generation with policies is not interoperable with WCF or JAX-WS/WSIT
Date Tue, 05 Aug 2008 09:48:44 GMT

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

Nandana Mihindukulasooriya resolved AXIS2-3105.
-----------------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4

This fixed now. Axis2 now attach policies to the binding using policy reference elements and
to the portType using wsp:PolicyURIs attributes. 

> WSDL generation with policies is not interoperable with WCF or JAX-WS/WSIT
> --------------------------------------------------------------------------
>
>                 Key: AXIS2-3105
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3105
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: nightly
>         Environment: Axis2 1.3 RC3 , Windows XP , Apache Tomcat 5.5.20
>            Reporter: Angel Todorov
>            Assignee: Deepal Jayasinghe
>            Priority: Critical
>             Fix For: 1.4
>
>
> I would first like to point out that this is not exactly a bug, but it's not a new feature
or improvement either. When policies are involved (such as security policies) , the Axis2
WSDL generation (when one generates the wsdl using ?wsdl on the axis servlet) puts the policies
directly in the <binding> element of the WSDL. Competing stacks such as WCF and JAX-WS/WSIT
both insert the policies as <PolicyReference> elements. The problem is that these two
frameworks cannot cope with policies that are not put in the WSDL in this manner, i.e. as
policy references. There is no concrete spec that dictates how PolicyAttachment is done in
the WSDL (most if the words in the spec are MAY, SHOULD or RECOMMEND). Therefore, neither
axis2 breaks the rules, nor WCF and JAX-WS. But in order for Axis2 to be interoperable and
gain more popularity where WS-SecurityPolicy (for example) is concerned, I think Axis2 should
change its way of generating WSDLs with policies in them. 
> Thanks for your feedback in advance.
> Regards,
> Angel

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