[Bug 68909] JSP compilation error due to classpath problems

2024-05-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 Mark Thomas changed: What|Removed |Added CC||ranjit.vadak...@gmail.com --- Comment

[Bug 68909] JSP compilation error due to classpath problems

2024-04-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 Chris changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 68909] JSP compilation error due to classpath problems

2024-04-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 --- Comment #8 from Mark Thomas --- Arguably the this issue isn't a Tomcat issue. This bug is a result of the application using the work-around of setting the system property. That in turn is used due to application and/or library issues

[Bug 68909] JSP compilation error due to classpath problems

2024-04-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 --- Comment #7 from Chris --- Hi, we have a central utility method to create our own instances of "com.ctc.wstx.stax.WstxInputFactory" that is not the issue. But we use libraries, that in the depth just call "XMLInputFactory.newFactory()".

[Bug 68909] JSP compilation error due to classpath problems

2024-04-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 --- Comment #6 from Christopher Schultz --- Is it possible for you to use your custom XMLInputFactory directly instead of calling getInstance(), or do you need Tomcat's JSP compiler to use your custom XMLInputFactory? -- You are receiving

[Bug 68909] JSP compilation error due to classpath problems

2024-04-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 --- Comment #5 from Chris --- You are absolutely right. Setting a SystemProperty within a web application is not a desired approach. The circumstances of our web application are rather homogeneous: it is always installed as the one and only

[Bug 68909] JSP compilation error due to classpath problems

2024-04-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 --- Comment #4 from Konstantin Kolinko --- (In reply to Chris from comment #2) > > System.setProperty(javax.xml.stream.XMLInputFactory.class.getName(), > WstxInputFactory.class.getName()); > The above line of code affects the whole JVM, not

[Bug 68909] JSP compilation error due to classpath problems

2024-04-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 --- Comment #3 from Christopher Schultz --- :( Sorry about that. We'll re-evaluate our solution to the opposite problem, which is ClassLoader-pinning when the webapp's ClassLoader is used to obtain the XMLInputFactory. -- You are receiving

[Bug 68909] JSP compilation error due to classpath problems

2024-04-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 --- Comment #2 from Chris --- Yeah, it comes down to these changes: https://github.com/apache/tomcat/commit/a2167e13c19115aecd220cd3be19d43d36126f3b https://github.com/apache/tomcat/commit/3b8f277a7ffc1193ed6c6d4fff85db6dc7327e39 We set a

[Bug 68909] JSP compilation error due to classpath problems

2024-04-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=68909 Chris changed: What|Removed |Added OS||All --- Comment #1 from Chris --- I located