[jira] Commented: (WSCOMMONS-316) PolicyReference.serialize(..) does not declare policy namespace

["Detelin Yordanov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WSCOMMONS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589070#action_12589070 ] 

Detelin Yordanov commented on WSCOMMONS-316:
--------------------------------------------

Hello guys,
  I saw you've cut the 2.0.3 release and this bug is still opened :-(
The fix is as simple as adding the following line in the PolicyReference.serialize(XMLStreamWriter) method:

 writer.writeNamespace(Constants.ATTR_WSP, Constants.URI_POLICY_NS);

In the SVN log I can see this was present in the initial implementation provided by dims and later got lost.

Because of this issue Axis2 users are currently not able to deploy a POJO service with a user provided WSDL
containing <wsp:PolicyReference xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" URI="RM_Inactivity_Policy"/> 
elements.

> PolicyReference.serialize(..) does not declare policy namespace
> ---------------------------------------------------------------
>
>                 Key: WSCOMMONS-316
>                 URL: https://issues.apache.org/jira/browse/WSCOMMONS-316
>             Project: WS-Commons
>          Issue Type: Bug
>          Components: Policy
>         Environment: Windows XP, Tomcat 5.5, Axis2 1.3, Neethi 2.0.2
>            Reporter: Detelin Yordanov
>
> The PolicyReference.serialize(..) method does not write namespace declarations (e.g. for the "wsp" namespace).
> This happens to be a problem, when a PolicyReference instance is serialized to a non-namespace repairing XMLOutputWriter as it happens in Axis2 PolicyUtil.getPolicyComponentAsOMElement(..).
> The issue appears only if the PolicyReference is serialized and then parsed as a single element, since if it is part of a larger document, it will most probably
> already contain the namespace declaration.

-- 
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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org