-0 I think the OSGi headers should not import the javax.security.jacc package which is exported by this bundle. I don't think it's really harmful because there's no other version of the jacc spec afaik, but in this case, this bundle only provides the api in version 1.1, so it makes no sense to import it.
On Fri, Sep 11, 2009 at 02:16, David Jencks <[email protected]> wrote: > I've built a release candidate for the jacc spec jar: > > https://repository.apache.org/content/repositories/geronimo-staging-002/ > > Site is staged here: > > http://people.apache.org/~djencks/staging-site/maven/specs/geronimo-jacc_1.1_spec/1.0.2/ > > Along with a bunch of build improvements this includes these fixes: > > GERONIMO-4357 don't double escape pre-escaped colons in web permissions > > GERONIMO-4587 fix EJBMethodPermission construction problem when a method > param is an array, patch (slightly modified) from Shawn Jiang > > r788107 ensure HTTPMethodSpec.getActions() returns right information - > otherwise reserialized permission objects could loose some vital > information. Also, add serialVersionUID constants > > GERONIMO-4721 represent 'all http methods' with '' rather than '\!' when > computing the actions string in web permissions > > GERONIMO-4735 serialize EJBMethodPermissionCollection contents only once > > GERONIMO-4734 fix web permissions HTTPMethodSpec equals method > > GERONIMO-4766, sort of. Use generics and make policy context handler > registration slightly more thread safe. > > [ ] +1 release it > [ ] 0 dunno > [ ] -1 Don't release it > > Vote open for 72 hours > > thanks > david jencks > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
