Have just attempted to do this upgrade.
Apps all deploy, but am getting the following so no JSP's compile.
INFO | jvm 1| 2018/06/12 17:20:11 | [qtp687479235-48] WARN
org.eclipse.jetty.server.handler.ErrorHandler - EXCEPTION
INFO | jvm 1| 2018/06/12 17:20:11 | javax.servlet.ServletExce
Ah, the WstxInputFactory is because of some system properties we were
crudely using.
-Djavax.xml.stream.XMLEventFactory=com.ctc.wstx.stax.WstxEventFactory
-Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory
-Djavax.xml.stream.XMLOutputFactory=com.ctc.wstx.stax.WstxOutputFactory
Hi All,
A quick question, can JAAS expose request URL to the login module?
I see from the Jetty document that, RequestParameterCallback can be used by
Login modules to get access to the ServletRequest that is involved in the
authentication, but seems it only exposed parameters? How can I
How are you deploying your apps, with the distro or embedded? Can you
please enable server.dumpAfterStart=true (in server.ini), and report the
output?
thanks
Jan
On 12 June 2018 at 13:16, Lord Buddha wrote:
> Ah, the WstxInputFactory is because of some system properties we were
> crudely using
We deploy via context xml files in a directory external to both jetty and
jetty.base
It turns out that removing those global system properties has fixed both
the issues, so, woohoo.
On 13 June 2018 at 04:31, Jan Bartel wrote:
> How are you deploying your apps, with the distro or embedded? Can
Hi
It's probably better to use the embedded xml stream parser with the jvm.
The Apache jsp compiler [1] is using xml stream parser so if you force a
factory this must available in the classpath. (see details here [2])
Regards
Olivier
[1]
https://github.com/apache/tomcat/blob/trunk/java/org/apache/
