On 10/03/17 00:14, Hoa Phan wrote:
> looks like I can't overwrite the webapp context.xml with tomcat
> context.xml. I have no control over the WAR file until tomcat deployed it :(
I have confirmed (via remote debugging) that using
...
in $CATALINA_BASE/conf/context.xml disables manifest
looks like I can't overwrite the webapp context.xml with tomcat
context.xml. I have no control over the WAR file until tomcat deployed it :(
If I try to use tomcat server.xml and add
inside it somehow breaks the webapp.
Is there any other way for me to set this scanmanifest to false.
Sa
On 09/03/17 21:38, Hoa Phan wrote:
> I'll try that and see how it goes, thanks Mark. Btw, when I was debugging I
> couldn't find where this method get called at all:
> public void setScanManifest(boolean scanManifest) {
> this.scanManifest = scanManifest;
> }
>
> This props default
I'll try that and see how it goes, thanks Mark. Btw, when I was debugging I
couldn't find where this method get called at all:
public void setScanManifest(boolean scanManifest) {
this.scanManifest = scanManifest;
}
This props default to true:
private boolean scanManifest = true
On 09/03/17 13:15, Hoa Phan wrote:
> Hi,
>
> I see that since 8.0.38 we added a scanManifest props to JarScanner.
> But when I added the props
> into: container/tomcat8x/apache-tomcat-8.0.38/conf/context.xml
>
>
> WEB-INF/web.xml
> ${catalina.base}/conf/web.xml
>
>
>
>
>
Hi,
I see that since 8.0.38 we added a scanManifest props to JarScanner.
But when I added the props
into: container/tomcat8x/apache-tomcat-8.0.38/conf/context.xml
WEB-INF/web.xml
${catalina.base}/conf/web.xml
It doesn't work and the prop is still true on startup:
