Hi Jason,

if you're using 2.10.1 you may be affected by
https://issues.apache.org/jira/browse/JSPWIKI-880

Other than that you shouldn't have any issues. Note that JSPWIKI-880 is
fixed on current trunk, so you could grab the latest snapshot from
https://repository.apache.org/content/groups/snapshots/org/apache/jspwiki/
and you should be set to go.

(this reminds me we should really look into releasing 2.10.2; there are
some i18n keys missing for some translations, but other than that current
trunk seems ok enough..)


HTH,
juan pablo

On Fri, Nov 13, 2015 at 1:55 AM, Jason Morris <jason.mor...@sydney.edu.au>
wrote:

> Thanks for the quick reply, Dave.
> I've had great success using JSPWiki on Tomcat... been using it for years.
> I tried exactly the procedure you mentioned, and I get wonky results with
> login not working using simple XML database authentication.
> I'll rip it all out, get the latest binary, and go through the config file
> again, and re-install from the Admin console.
> Can I ping you with questions? Don't want to spam you.
> Cheers,
> Jason
>
> -----Original Message-----
> From: Dave Koelmeyer [mailto:dave.koelme...@davekoelmeyer.co.nz]
> Sent: Friday, 13 November 2015 11:46 AM
> To: user@jspwiki.apache.org
> Subject: Re: Glassfish 4.0 installation instructions
>
> On 13/11/15 13:19, Jason Morris wrote:
> > Hello!
> > Does anyone have a complete and updated list of the instructions for
> installing & configuring JSPWiki on Glassfish 4.0?
> > Thanks!
>
> Hi Jason,
>
> I don't, but I do use GlassFish - assuming you're not using
> container-managed authentication it's as simple installing the WAR as a
> web app using the GlassFish GUI, and running the JSPWiki installer. Some
> of the paths for JSPWiki's configuration files will differ from Tomcat
> here and there, shoot if you need.
>
> (I'm planning to check out Payara at some stage however
> (http://www.payara.co/home), as a migration path from GlassFish.)
>
> --
> Dave Koelmeyer
> http://blog.davekoelmeyer.co.nz
> GPG Key ID: 0x238BFF87
>
>
>

Reply via email to