What level of issue is it, if the default file isn't found (fatal, error, warning)?
On Nov 22, 2007 1:07 PM, Andrew Jaquith <[EMAIL PROTECTED]> wrote: > For now, I think the best strategy would be, simply, to handle the NPE > more gracefully and print a useful error message. > > The idea of making the policy file configurable isn't a bad one, but I > don't think we need to do it now. It might indeed make sense when we > have multi-wiki support, but I'd rather do it at that time. > > On Nov 22, 2007, at 14:20, "Janne Jalkanen (JIRA)" <[EMAIL PROTECTED]> > wrote: > > > > > [ > https://issues.apache.org/jira/browse/JSPWIKI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544878 > > ] > > > > Janne Jalkanen commented on JSPWIKI-53: > > --------------------------------------- > > > > Question: Andrew, how does this play with whatever you were planning > > for multiwiki support? Each wiki is going to need its own policy. > > > >> NPE When jspwiki.policy file not found in WEB-INF > >> ------------------------------------------------- > >> > >> Key: JSPWIKI-53 > >> URL: https://issues.apache.org/jira/browse/JSPWIKI-53 > >> Project: JSPWiki > >> Issue Type: Bug > >> Components: Authentication&Authorization > >> Affects Versions: 2.6.0 > >> Environment: WinXP, Tomcat 5.5 > >> Reporter: Dave Wolf > >> Fix For: 2.6.0 > >> > >> > >> In the AuthorizationManager, a call is made to > >> AuthenticationManager.findConfigFile( engine, DEFAULT_POLICY ). If > >> this method does not find the jspwiki.policy file, then the > >> following line after the call will result in a NPE. > > > > -- > > This message is automatically generated by JIRA. > > - > > You can reply to this email to add a comment to the issue online. > > >
