OK, the new code seems to work when I run on localhost Tomcat, at least
the policy file is being read, but I have more debugging/testing to do
on localhost (and on OpenShift)--more config changes to make to ensure
it's all running smoothly. All those WatchDog error messages in the
logs are quite an eyesore.
Glen
On 12/22/2013 04:45 PM, Glen Mazza wrote:
Hmm, getting the same NPE exception as below when deploying to
OpenShift. This is my configuration entry in my
jspwiki-custom.properties:
# Authorization file
jspwiki.policy.file=jspwiki-custom.policy
I'll look more into this on my side, but it may not be until next
weekend before I can do so. I'll change my vote from a -1 to a 0,
this is inconvenient but not a show-stopper.
Thanks,
Glen
On 12/22/2013 09:02 AM, Glen Mazza wrote:
Awesome, thanks Harry! I'll test today and respond back, hopefully
soon.
Glen
On 12/22/2013 08:44 AM, Harry Metske wrote:
this NPE should have been fixed now, it was a classloading issue,
combined
with the leading slash of the resource.
Can you try once more.
regards,
Harry
On 22 December 2013 00:43, Glen Mazza <glen.ma...@gmail.com> wrote:
-1 right now, just one thing, I hope to fix soon unless someone
else can
get to it. Namely, the "jspwiki.policy.file" property in
jspwiki-custom.properties doesn't seem to be working--I get an NPE
on just
about any value I put there (unless I use "jspwiki.policy" itself,
in which
case it probably incorrectly looks for the default one under
WEB-INF.) I
should be able to have this setting in my jspwiki-custom.properties
file:
jspwiki.policy.file=mycustom.policy
And place mycustom.policy in my $CATALINA_HOME/lib folder, and that
policy
file should get picked up. I've tried multiple ways to specify the
customization file--full path, with/without leading "/", etc., they
all
fail with this NPE:
java.lang.NullPointerException
at org.apache.wiki.auth.AuthenticationManager.findConfigFile(
AuthenticationManager.java:646)
at org.apache.wiki.auth.AuthorizationManager.initialize(
AuthorizationManager.java:494)
at org.apache.wiki.WikiEngine.initialize(WikiEngine.java:586)
at org.apache.wiki.WikiEngine.<init>(WikiEngine.java:430)
I'd like this property to work because I'm about to update my blog
entry
on hosting JSPWiki on OpenShift, and I would like users to be able
to just
deploy the WAR & a separate policy file without needing to do "war
surgery", i.e., open up and modify the jspwiki.policy file loaded
there by
default. We no longer require war surgery for the
jspwiki.properties file,
it would be very nice for it to be the same for the policy file.
Regards,
Glen
On 12/20/2013 06:02 PM, Juan Pablo Santos Rodríguez wrote:
This is a release vote for Apache JSPWiki, version 2.10.0. The
vote will
be
open for at least 72 hours from now.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12310732&version=12323941
Note that we are voting upon the source (tag), binaries are
provided for
convenience.
Everybody is encouraged to vote.
Source and binary files:
http://people.apache.org/~juanpablo/releases/2.10.0-rc1
The tag to be voted upon:
http://svn.apache.org/repos/asf/jspwiki/tags/jspwiki_2_10_0_rc1
JSPWiki's KEYS file containing PGP keys we use to sign the release:
http://www.apache.org/dist/jspwiki/KEYS
*** Please download, test and vote:
[ ] +1 Approve the release
[ ] 0 Don't mind
[ ] -1 Disapprove the release (please provide specific comments)
br,
juan pablo
