I did my last major commit about an hour ago with incremental JavaDoc commits since then. You might want to do an SVN update...
On Wed, Jul 23, 2008 at 6:18 PM, Dain Sundstrom <[EMAIL PROTECTED]> wrote: > That's just me. I typically read the javadoc and skim the source code > (just incase they don't match). In this case there wasn't any javadoc :) > > Anyway, I'll let you know how it works out for us, and if I find anything > fishy in the impl. > > Oh, are there any changes for this code in trunk (or in the pipeline) that > I should be aware of. > > -dain > > > On Jul 23, 2008, at 2:10 PM, Les Hazlewood wrote: > > That reminds me - Dain, do you have any questions or suggestions about how >> WildcardPermission might not meet your needs? If you're looking into the >> guts of this class, that leads me to believe that maybe we could improve >> something... >> >> On Wed, Jul 23, 2008 at 5:09 PM, Les Hazlewood <[EMAIL PROTECTED]> wrote: >> >> Hi Dain, >>> >>> I don't think Jeremy (our original WildcardPermission author) has >>> migrated >>> the following post into the documentation yet, but hopefully this helps a >>> bit: >>> >>> http://www.jsecurity.org/node/1041#comment-155 >>> >>> Jeremy, any chance you could write the JavaDoc for WildcardPermission >>> sometime soon? >>> >>> Cheers, >>> >>> Les >>> >>> >>> On Wed, Jul 23, 2008 at 5:02 PM, Dain Sundstrom <[EMAIL PROTECTED]> wrote: >>> >>> Is there a spec somewhere that explains how the default encoded >>>> permission >>>> string maps to the construction of a permission object? I tried to >>>> follow >>>> the code but got lost trying to follow how the string is split-up >>>> between >>>> permission construction and the WildcardPermission. I'm also interested >>>> in >>>> how you escape special characters like comma and colon. >>>> >>>> Also, is there a spec for WildcardPermission.implied(). >>>> >>>> -dain >>>> >>>> >>> >>> >
