[
https://issues.apache.org/jira/browse/AXIS2-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519686
]
Angel Todorov commented on AXIS2-3105:
--------------------------------------
This is from the WS-PolicyAttachment specification, to which both JAX-WS (WSIT)
and WCF (Windows Communication Foundation) stick:
4. Attaching Policies Using WSDL 1.1
The RECOMMENDED means of associating a Policy with a Policy Subject that has a
WSDL 1.1 [WSDL 1.1] description is to attach a reference to the Policy within
the WSDL component corresponding to the target Policy Subject.
WSDL 1.1 disallows the use of extensibility elements on certain elements and
the use of extensibility attributes on others. However, the WS-I Basic Profile
1.1 [BP 1.1] overrules this restriction and allows element extensibility
everywhere. Therefore, the Policy reference SHOULD be attached using
<wsp:PolicyReference> as child element unless it is absolutely necessary to
maintain the original WSDL 1.1 restriction, in which case the @wsp:PolicyURIs
attribute should be used for those restricted cases.
If it is necessary to include the actual Policy Expressions within the WSDL
description itself, it is RECOMMENDED that their <wsp:Policy> elements be
included as children of the <wsdl:definition> element, and referenced using the
mechanisms just described. Alternatively, the Policy Expressions MAY be made
available through some other means, such as WS-MetadataExchange
[WS-MetadataExchange].
To ensure that consumers of Policy-annotated WSDL elements are capable of
processing such Policy Attachments, attachments using <wsp:PolicyReference>
SHOULD be marked as a mandatory extension (e.g., with a @wsdl:required="true"
attribute).
Regards,
Angel
> 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]
