ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Namrata Jaiswal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WSS-461) org.apache.ws.security.processor.SignatureProcessor does not allow to add custom resolver
Date Fri, 12 Jul 2013 07:51:50 GMT

     [ https://issues.apache.org/jira/browse/WSS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Namrata Jaiswal updated WSS-461:
--------------------------------

    Priority: Critical  (was: Major)
    
> org.apache.ws.security.processor.SignatureProcessor does not allow to add custom resolver
> -----------------------------------------------------------------------------------------
>
>                 Key: WSS-461
>                 URL: https://issues.apache.org/jira/browse/WSS-461
>             Project: WSS4J
>          Issue Type: Improvement
>          Components: WSS4J Core
>    Affects Versions: 1.5.12
>            Reporter: Namrata Jaiswal
>            Assignee: Colm O hEigeartaigh
>            Priority: Critical
>
> org.apache.ws.security.processor.SignatureProcessor does not provide api to add resource
resolver. To explain it more,
> I received a soap message with a particular ID pattern and for that ID pattern, I would
like to provide my own implementation for ResourceResolverSpi( that can be added to resource
signature element). If some api is exposed that allows user to provide their own implementation
for resourceresolver then it would great.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


Mime
View raw message