Can you create a Jira issue to investigate that approach? I'm not
sure whether it would work but it sounds like it's worth following up
on. If you can attach a small example that demonstrates the problem,
that would be great too. (If nothing else, maybe we could just try
the repackaging approach if we notice that the original JAR was
signed.)
Thanks,
Aaron
On 2/16/07, Spotts, Joel (ISS Atlanta) <[EMAIL PROTECTED]> wrote:
Is it possible the geronimo code creates the proxy in the same package as the target
class? If the proxy was created in a different package (like proxy.<targetclass
proxy>), IIRC, no SecurityException would be thrown.
Thanks,
Yoel
-----Original Message-----
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]
Sent: Mon 2/12/2007 10:23 PM
To: [email protected]
Cc:
Subject: Re: Gbean within a signed jar
Alternatively, just change the code that complains about the
signature. We could add a flag to the Geronimo class loader to hide
all signing data.
-dain
