[
https://issues.apache.org/jira/browse/AXIS2-3536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665403#action_12665403
]
Andrei Ivanov commented on AXIS2-3536:
--------------------------------------
This doesn't affect the codegen component only
I was trying to start a service that used an external policy and it fails,
because the same code is being used.
It seems that best practices aren't exactly encouraged with Axis
> Problem accessing policy via external URI
> -----------------------------------------
>
> Key: AXIS2-3536
> URL: https://issues.apache.org/jira/browse/AXIS2-3536
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.3
> Reporter: Michael Drapkin
>
> Storing policy information in a separate file and referencing it from within
> WSDL via wsp:PolicyReference/@URI attribute does not work. When I embed the
> policy details within the WSDL and then reference the policy internally (e.g.
> <wsp:PolicyReference URI="#operation_policy"/>) running wsdl2code produces
> desired results. However when referencing the same policy information via an
> external URI (e.g. <wsp:PolicyReference
> URI="http://host/policy.xml#operation_policy"/>) the policy is ignored while
> wsdl2code prints out an error "ERROR: Ignoring policy - null". Having traced
> this flow I can see that the policy is retrieved from the external URI,
> however when the call is made to AxisPolicyLocator.register() the latter
> raises an UnsupportedOperationException which causes the "Ignoring policy"
> message to be printed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
