[
https://issues.apache.org/jira/browse/WSS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred Dushin resolved WSS-74.
----------------------------
Resolution: Fixed
A fix for this was committed.
> Allow Actions and Processors to be customizable
> -----------------------------------------------
>
> Key: WSS-74
> URL: https://issues.apache.org/jira/browse/WSS-74
> Project: WSS4J
> Issue Type: Improvement
> Reporter: Fred Dushin
> Attachments: wss-74.patch
>
>
> WSS4J has a hard-wired set of Actions (for WSHandlers) and Processors (for
> message handling), but it would also be good to support user-replaceability
> of Actions, on the producing side, and Processors, on the consuming side of
> endpoints that use WSS4J.
> The included patch supports this replaceability. Applications can register
> Actions and Processors through the WSSConfig class. Two new operations are
> added on this type: setAction and setProcessor, allowing applications to add
> or override their own Actions or Processors, respectively. All previous
> behavior is preserved by not calling either of these operations.
> The WSHandler doSenderAction has been modified to take the WSSConfig from the
> RequestData first -- if it's not there, it will create a default one, as
> before. It has also been modified to call a custom action, if so configured.
> A static dependency between the WSSConfig and WSSecuityEngine types has been
> removed, so that static instances of the WSSConfig type are created (and
> cached) lazily, at runtime, instead of a class load time.
--
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]
