Running e.g. a Jetty WebApp Container we’ve got some Portlet bridging code which does have a check like this:
return ThreadPortletContext.getPortletRequest() != null
where ThreadPortletContext.getPortletRequest() return a PortletContext instance if in a portal or null if a pure servlet environment is running.
This does not work with the new agent (version 6.4.7, version 6.5.2). Using no agent works fine, the legacy one does work too.
The new agent results in this exception being thrown:
Caused by: java.lang.NoClassDefFoundError: javax/portlet/PortletRequest
at org.apache.wicket.portlet.ThreadPortletContext.getPortletRequest(ThreadPortletContext.java:56)
Please fix that behaviour to match the legacy agent / non-agent scenario of the JVM.