-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sean,
On 1/12/18 11:34 AM, Sean Brett wrote:
> In case anyone else has such an issue, it appears that this was all
> caused by the rt.jar in the webapps WEB-INF/lib directory.
>
> I removed that jar for one of the other webapps exhibiting the same
In case anyone else has such an issue, it appears that this was all caused
by the rt.jar in the webapps WEB-INF/lib directory.
I removed that jar for one of the other webapps exhibiting the same issue
and it resolved the issue.
On 12/01/2018 14:38, "Sean Brett" wrote:
>Comments at the bottom.
Comments at the bottom. (Spoiler alert: Good news!)
On 11/01/2018 22:38, "Christopher Schultz"
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Sean,
>
>On 1/11/18 11:58 AM, Sean Brett wrote:
>> On 11/01/2018 15:48, "Christopher Schultz"
>> wrote:
>>
>>
>>> -BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sean,
On 1/11/18 11:58 AM, Sean Brett wrote:
> On 11/01/2018 15:48, "Christopher Schultz"
> wrote:
>
>
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>
>> Sean,
>>
>> (Thanks for moving to the mailing list; it's a much better forum
>> for
Thanks for the input Chris, I’ve responded inline...
On 11/01/2018 15:48, "Christopher Schultz"
wrote:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Sean,
>
>(Thanks for moving to the mailing list; it's a much better forum for
>getting into a protracted discussion. See below for more, in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sean,
(Thanks for moving to the mailing list; it's a much better forum for
getting into a protracted discussion. See below for more, inline.)
On 1/10/18 9:08 AM, Sean Brett wrote:
> I've been tasked with migrating a site from one institution to
> a
I've been tasked with migrating a site from one institution to another. As
part of the process we are attempting to update the versions the site
uses.
Initially I was asked to use Java 8 with Tomcat 5.5 (on Linux), which led
to issues - not to mention Tomcat 5 being 'out of support¹. I have sinc
