[jbossws-issues] [JBoss JIRA] (JBWS-4051) Revisit details on available cryptography for tests

[Jan Blizňák (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-4051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Blizňák updated JBWS-4051:
------------------------------
    Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/21


> Revisit details on available cryptography for tests
> ---------------------------------------------------
>
>                 Key: JBWS-4051
>                 URL: https://issues.jboss.org/browse/JBWS-4051
>             Project: JBoss Web Services
>          Issue Type: Enhancement
>          Components: jbossws-cxf
>    Affects Versions: jbossws-cxf-5.1.6.Final
>            Reporter: Jan Blizňák
>            Assignee: Jan Blizňák
>            Priority: Optional
>
> Currently there are two tests classes that informs user about actual BouncyCastle and unlimited stregth cryptography availability:
> org.jboss.wsf.test.CryptoCheckMain that informs about BC availibility during execution of test-utils module
> org.jboss.wsf.test.CryptoHelper that provides hints for exceptions in security related tests.
> But both only recognize BouncyCastleProvider installed within security providers while JBossWS 5+ can also load BC provider from classpath. Thus the current mechanism can wrap actual exception in false warning on missing BC.
> The proposal is to move printing info from test-utils to testsuite module to be printed where it actually matters.
> The second proposal is to merge both classes and also detect the BC on test classpath.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)