Re: [jetty-users] TLD scanner warning at boot time

[Jan Bartel <janb@xxxxxxxxxxx>]

All jar scanning should be performed by jetty classes, _not_ by the apache jasper classes as per your stack trace.  The `oej.ee8.webapp.MetaInfConfiguration` class  gathers the TLD resources and puts them into a context attribute ready to be picked up by the oej.ee8.apache.jsp.JettyJasperIntializer  servlet container initializer. It is a fallback of the latter class to use apache jasper scanning if it can't find the pre-scanned TLDs. Maybe you're not even using the JettyJasperInitializer any more. I would run with debug turned on for org.eclipse.jetty.ee8 to see what is going on, and ensure that the proper jetty classes are being used.

Jan

On Mon, 10 Mar 2025 at 14:24, Guus der Kinderen via jetty-users <jetty-users@xxxxxxxxxxx> wrote:

Hi all,

Our software project, Openfire, is a Java-based project that embeds two Jetty servers (using Jetty12/EE8).

We use JSPC precompliation of JSP pages.

Recently, we've added Oracle JDBC drivers to our project. Since then, we're getting a lot of warnings like the one attached to this email at boot time (not during compilation). What is confusing me is that this doesn't happen in all environments.

What's the cause of this? How can we prevent this from happening?

I'm far from an expert, but I think this relates to an automatic scan for TLD libraries. Given that we're using JSP pre-compliation, should this even be happening?

Kind regards,

  Guus

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users

--

Jan Bartel <janb@xxxxxxxxxxx>

www.webtide.com
Expert assistance from the creators of Jetty and CometD