i have upgraded from fop 2.2 to 2.3 and excluded xalan and xml-apis
again. it seems to be working ok at the moment on my development
machine. i will try again on production
org.apache.xmlgraphics
fop
${fop.version}
thanks Jean-Louis. i tried excluding xalan maven artifact from the pom
but then FOP doesn't work. i might try to create a reproducer using
tomee webapp archetype if possible
On 17/07/18 12:46, Jean-Louis Monteiro wrote:
This usually indicates you have the same class loaded into 2 different
This usually indicates you have the same class loaded into 2 different
classloaders which makes them different.
In this scenario, I would check if you don't have duplicate xalan jars in
tomee/lib and in the WEB-INF/lib of your application.
Hope it helps
--
Jean-Louis Monteiro
Hello,
thank you for the answer! To be clear, by duplicate jars, you mean
in the tomee lib/ folder, or the pom.xml, correct?
If that's what you mean, I think both are OK, as I wrote in another
email to this list, in the lib/ folder we've only added the postgresql
driver, and in the
Hello,
thank you for the advice. Yes it's by checking the web.xml that we
stumbled upon the prettyfaces dependency which we now removed. I'm
attaching the web.xml in case you maybe spot another oddity.
Compared to the lib/ folder from the tomee 7.0.3 distribution, we
have added in our
Hello,
we have two products using the same core library. On one product
we've seen this error once and a restart fixed it. On the other product
we've had to abort an upgrade, tried to restart the app more than 5
times and it would fail every time. But we can't "experiment" on that
