[
https://issues.apache.org/jira/browse/AXIS2-5405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Lazarski resolved AXIS2-5405.
------------------------------------
Resolution: Incomplete
Closing as Incomplete. Filed against 1.6.2 in 2012 with no WSDL provided
and no response to the committer's request for a reproducer. The linked
StackOverflow issue reveals the root cause is in the Rampart/Neethi
policy builder interaction — SymmetricBindingBuilder.build() in
secpolicy11 receives the <wsp:Policy> wrapper element but expects
<sp:SymmetricBinding> with <wsp:Policy> as a child. The generated stub's
getPolicy() method passes the wrong XML element to Neethi's
PolicyEngine.getPolicy(). Fixing this requires understanding the
WS-SecurityPolicy 1.1 assertion builder contract and how Neethi's
PolicyBuilder.processOperationElement() dispatches to assertion builders
— it spans three projects (Axis2 codegen, Neethi, and Rampart secpolicy)
with no test coverage for this interaction. Not tractable without a WSDL
reproducer. If anyone can reproduce this on 2.0.x with Rampart 2.0.0,
please open a new issue with the WSDL and wsdl2java command used.
> Incorrect WS-Security namespace generation by wsdl2java
> -------------------------------------------------------
>
> Key: AXIS2-5405
> URL: https://issues.apache.org/jira/browse/AXIS2-5405
> Project: Axis2
> Issue Type: Bug
> Components: wsdl
> Affects Versions: 1.6.2
> Environment: Windows 7. Java 6 x64.
> Reporter: James Annesley
> Priority: Critical
>
> Mix up on WS-Security policy namespace in generated stubs [1]. Workaround to
> perform a "find replace" on <sp:policy> and </sp:policy> to <wsp:policy> and
> </wsp:policy> respectively [2].
> [1]
> http://stackoverflow.com/questions/8364193/illegalargumentexception-protectiontoken-is-not-a-wsppolicy-element
> [2] http://markmail.org/thread/6hhk72zzgtba5y3v
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
