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
Priority: Critical
Fix For: nightly
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
