[ https://issues.apache.org/jira/browse/DELTASPIKE-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14486713#comment-14486713 ]
Charlee Chitsuk commented on DELTASPIKE-870: -------------------------------------------- After full building my project against the latest checked out Apache DeltaSpike 1.3.1-SNAPSHOT, it work great. I can confirm that the issue has been fixed already. Thank you very much for your quick response. > Partial Bean with signed jar trouble. > ------------------------------------- > > Key: DELTASPIKE-870 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-870 > Project: DeltaSpike > Issue Type: Bug > Components: PartialBean > Affects Versions: 1.3.0 > Environment: Windows 7 64 bits > JDK 1.8.0_40 64bits > Reporter: Charlee Chitsuk > Assignee: Thomas Andraschko > Fix For: 1.3.1 > > > I've a utility jar which uses the partial beam for querying by using the JPA. > This utility jar also has been signed by using the jar signer. Previously it > works great with Apache DeltaSpike 1.2.1 > Anyhow when I try to upgrade the Apache DeltaSpike to version 1.3.0 the > system show me the exception as > Caused by: java.lang.SecurityException: class > "some.package.PolicyFinder$$DSPartialBeanProxy"'s signer information does not > match signer information of other classes in the same package > I also have a chance to ask via the user mailing list as [1]. Thomas > Andraschko mentioned as the following: - > "AFAIR our old javassist proxies created the proxy class also in the same > package as the original jar. > Maybe the old proxy used another classloader or javassist reuses the > ProtectionDomain." > [1] > http://mail-archives.apache.org/mod_mbox/deltaspike-users/201504.mbox/%3CCAFBJWv6WhZxZ6Q7ngsCwtBs_w9CqWea2sN5p2M75W1rW7oi%2BPg%40mail.gmail.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)