On Thu, 2010-02-25 at 11:17 -0600, David M. Lloyd wrote:
> One possible workaround solution would be to allow you to
somehow
> specify that the unsigned jar should create its own local package.
> i.e. instead of searching the ClassLoaderDomain for the existing package
> you just create one locally.
Out of curiosity, is there a reason we don't do this already (i.e. a javaee
spec or something)? I'd think that by default each JAR should have a
separate package space, but I guess there could be exceptions in certain cases.
Package sealing wouldn't work. It would see them as two
separate packages.
- DML
--
xxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss by Redhat
xxxxxxxxxxxxxxxxxxxxx