deltaspike-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Andraschko <andraschko.tho...@gmail.com>
Subject Re: DeltaSpike 1.3.1: Partial Bean with signer trouble.
Date Wed, 08 Apr 2015 17:59:31 GMT
Hi,

i probably fixed it in trunk.
Could you please give it a try?

2015-04-08 10:43 GMT+02:00 Charlee Chitsuk <charlee.ch@gmail.com>:

>    Hi,
>
>       The issue has been created as [1]
>
> [1] https://issues.apache.org/jira/browse/DELTASPIKE-870
>
> --
>    Best Regards,
>
>    Charlee Ch
>
> 2015-04-08 15:04 GMT+07:00 Thomas Andraschko <andraschko.thomas@gmail.com
> >:
>
> > Hi,
> >
> > 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.
> >
> > Please create an issue.
> >
> >
> >
> >
> > 2015-04-08 6:21 GMT+02:00 Charlee Chitsuk <charlee.ch@gmail.com>:
> >
> > > Hi All,
> > >
> > > 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
> > >
> > > Could you please help to advise further? Am I doing something wrong?
> > >
> > > Thank you very much for your help in advance. I'm looking forward to
> > > hearing from you soon.
> > >
> > > --
> > >    Best Regards,
> > >
> > >    Charlee Ch.
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message