Our application encountered class loading exceptions after upgrading to
Tomcat 10.1.33 (embedded), but only in the presence of the DataDog Java
Agent. Upgrading to Tomcat 10.1.34 seems to have resolved the issue
(thanks for the release!), so likely no further investigation is needed.
I'm report
Thanks, Tomcat team, for cranking out another release!
I noticed a minor discrepancy on the main website home page
(https://tomcat.apache.org/). In the "Tomcat 9.0.73 Released" section,
"Tomcat 9 changelog" links to the 9.0.71 bookmark
("#Tomcat_9.0.71_(remm)") instead of the 9.0.73 bookmark.
On 6/14/2021 12:38 PM, Mark Thomas wrote:
On 14/06/2021 20:31, Adam Rauch wrote:
As you're probably aware, all Boolean, Byte, Character, Double,
Float, Integer, Long, and Short constructors were deprecated in JDK
9,
https://www.oracle.com/java/technologies/javase/9-deprecated-features
As you're probably aware, all Boolean, Byte, Character, Double, Float,
Integer, Long, and Short constructors were deprecated in JDK 9,
https://www.oracle.com/java/technologies/javase/9-deprecated-features.html#JDK-8065614.
They were then marked forRemoval=true in JDK 16.
Jasper generates code
On 9/14/2020 6:19 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Adam,
On 9/11/20 19:30, Adam Rauch wrote:
I have implemented a custom JspWriter and registered it for use by
our JSPs using the approach described here:
https://stackoverflow.com/questions
On 9/12/2020 2:15 AM, Mark Thomas wrote:
On 12/09/2020 00:30, Adam Rauch wrote:
I have implemented a custom JspWriter and registered it for use by our
JSPs using the approach described here:
https://stackoverflow.com/questions/29508245/jsp-using-a-delegate-for-out-jspwriter-with-jsp-includes-to
I have implemented a custom JspWriter and registered it for use by our
JSPs using the approach described here:
https://stackoverflow.com/questions/29508245/jsp-using-a-delegate-for-out-jspwriter-with-jsp-includes-to-change-the-beh
I created a custom JspFactory that returns a custom JspContext t
On 11/17/2019 9:01 AM, Mark Thomas wrote:
On 16/11/2019 22:08, Adam Rauch wrote:
While testing 8.5.48, we now see NullPointerExceptions when our
ImageServlet code attempts to forward a request to a new location. In
8.5.47, the code works fine.
Thanks for reporting this. I can see what the
While testing 8.5.48, we now see NullPointerExceptions when our
ImageServlet code attempts to forward a request to a new location. In
8.5.47, the code works fine.
A simplified version of our code:
public void sendResource(HttpServletRequest request,
HttpServletResponse response) throws IO
When attempting to connect to a DataSource that specifies a database
that doesn't exist, Tomcat 8.5.46 throws an informative SQLException;
for example: java.sql.SQLException: Cannot create
PoolableConnectionFactory (FATAL: database "labkey19.3" does not exist)
In the same situation, Tomcat 7.0
On 1/3/2019 11:53 AM, Mark Thomas wrote:
On 02/01/2019 19:50, Adam Rauch wrote:
Our build pre-compiles JSPs by invoking JspC following a pattern similar
to the JspC JavaDoc example configuration:
https://tomcat.apache.org/tomcat-8.5-doc/api/org/apache/jasper/JspC.html
Starting with 9.0.14 and
Our build pre-compiles JSPs by invoking JspC following a pattern similar
to the JspC JavaDoc example configuration:
https://tomcat.apache.org/tomcat-8.5-doc/api/org/apache/jasper/JspC.html
Starting with 9.0.14 and 8.5.37, our build stopped pre-compiling JSPs;
JspC no longer converts a tree of
Our code retrieves DataSources using JNDI, with code similar to this:
new InitialContext().lookup("java:comp/env/jdbc/labkeyDataSource");
With a simple DataSource definition that doesn't specify a "factory"
attribute, this code now throws in Tomcat 7.0.86. (It works in 7.0.85,
8.0.50, 8.5.
On 10/16/2017 1:27 PM, Net Dawg wrote:
Profuse apologies. We are unable reproduce this. However out tests were
failing for another reason.
8.5.23 returns 400 error with header "HTTP/1.1 400" where as version 8.0.47 returns the same as
"HTTP/1.1 400 Bad Request". When the tests check for th
I noticed that the current element for the new EOL page is:
"Apache Tomcat® - End of life for Apache Tomcat 6.0.x". You may want to
adjust the version to "8.0.x."
Thanks,
Adam
-
To unsubscribe, e-mail: users-unsubscr...@tomca
Is Tomcat 8.5.15 officially released? The home page
(http://tomcat.apache.org/index.html) seems to indicate that it was released
2017-05-10. however, the text of the section references the "release of
version 8.5.14" and "notable changes compared to 8.5.13." And the changelog
link hits the 8.5.14 a
16 matches
Mail list logo
