ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (Closed) (JIRA)" <>
Subject [jira] [Closed] (WSS-74) Allow Actions and Processors to be customizable
Date Mon, 03 Oct 2011 09:04:36 GMT


Colm O hEigeartaigh closed WSS-74.

> Allow Actions and Processors to be customizable
> -----------------------------------------------
>                 Key: WSS-74
>                 URL:
>             Project: WSS4J
>          Issue Type: Improvement
>            Reporter: Fred Dushin
>             Fix For: 1.5.4
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message