You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Colm O hEigeartaigh (JIRA)" <ji...@apache.org> on 2012/12/18 12:04:12 UTC
[jira] [Resolved] (WSS-417) Cannot deploy WSS4J 1.6.8 to an OSGi
container
[ https://issues.apache.org/jira/browse/WSS-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh resolved WSS-417.
-------------------------------------
Resolution: Fixed
> Cannot deploy WSS4J 1.6.8 to an OSGi container
> ----------------------------------------------
>
> Key: WSS-417
> URL: https://issues.apache.org/jira/browse/WSS-417
> Project: WSS4J
> Issue Type: Bug
> Affects Versions: 1.6.8
> Reporter: Colm O hEigeartaigh
> Assignee: Colm O hEigeartaigh
> Priority: Critical
> Fix For: 1.6.9
>
>
> An unintended consequence of WSS-410 is that you can no longer deploy WSS4J to an OSGi container. Santuario will not be loaded correctly as a provider in WSSConfig.
--
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