[jboss-jira] [JBoss JIRA] (AS7-3618) Testsuite org.jboss.staxmapper.XMLExtendedStreamWriterFactory causes problems when using signed/sealed jars
Paul Gier (JIRA)
jira-events at lists.jboss.org
Sat Feb 4 13:33:48 EST 2012
[ https://issues.jboss.org/browse/AS7-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier reassigned AS7-3618:
------------------------------
Assignee: Paul Gier (was: Andrew Rubinger)
> Testsuite org.jboss.staxmapper.XMLExtendedStreamWriterFactory causes problems when using signed/sealed jars
> -----------------------------------------------------------------------------------------------------------
>
> Key: AS7-3618
> URL: https://issues.jboss.org/browse/AS7-3618
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Test Suite
> Reporter: Paul Gier
> Assignee: Paul Gier
> Fix For: 7.1.1.Final
>
>
> The smoke tests contain a class called org.jboss.staxmapper.XMLExtendedStreamWriterFactory. When using signed AS jars, this causes a security exception in any tests which use this class because the package name is the same as the classes in org.jboss:staxmapper jar.
> {noformat}
> class "org.jboss.staxmapper.XMLExtendedStreamWriterFactory"'s signer information does not match signer information of other classes in the same package
> {noformat}
> Possible solutions are to:
> 1. Change the package name of this class. But this might be difficult because it current accesses a package protected staxmapper class.
> 2. Add this class to the staxmapper jar, or a test jar in the staxmapper build.
> 3. Sign the testsuite classes with the same key as the staxmapper jar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list