You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2012/08/13 21:20:37 UTC

[jira] [Comment Edited] (CXF-4469) 2.6.x rt-ws-security bundle is requiring opensaml

    [ https://issues.apache.org/jira/browse/CXF-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433344#comment-13433344 ] 

Aki Yoshida edited comment on CXF-4469 at 8/14/12 6:18 AM:
-----------------------------------------------------------

Hi Colm,
Okay. Thanks.

I looked at manifest in the wss4j.1.6.6.jar bundle and I saw the org.opensaml* stuff with optional resolution. So, I thought opensaml is still optional. But I saw they are referenced in rt-ws-security's WSS4JInInterceptor, so they seem to be required.

But I am still wondering if opensaml is declared as optional in wss4j 1.6.6, some ws security functionality may be provided without opensaml?

Regards, Aki
                
      was (Author: ay):
    Hi Colm,
I might be missing something.

I looked at manifest in the wss4j.1.6.6.jar bundle, and I saw the org.opensaml* stuff with optional resolution. So, I thought opensaml is still optional.

Regards, Aki
                  
> 2.6.x rt-ws-security bundle is requiring opensaml
> -------------------------------------------------
>
>                 Key: CXF-4469
>                 URL: https://issues.apache.org/jira/browse/CXF-4469
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.6.1
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 2.6.2
>
>
> The CXF's 2.6.x's rt-ws-security bundle is requiring opensaml, although opensaml is supposed to be optional.
> The cxf all bundle declares opensaml* as optional and not requiring them.
> The rt-ws-security's pom also needs this optional import declaration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira