Re: No Factories configured for this Application. This happens if the faces-initialization does not work at all

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 pom

Re: No Factories configured for this Application. This happens if the faces-initialization does not work at all

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

Re: No Factories configured for this Application. This happens if the faces-initialization does not work at all

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 environ

Re: No Factories configured for this Application. This happens if the faces-initialization does not work at all

Hi Maybe check your web.xml declaration of faces servlet, you classpath and webapp lib folder (some jsf api or impl leaking?) and finally ensure when you redeployed that you cleaned work/, conf/ and other temporary folders in your catalina.base folder. Le mar. 17 juil. 2018 00:22, Jean-Louis Mont

Re: No Factories configured for this Application. This happens if the faces-initialization does not work at all

Hello Emmanuel This exception sometimes (generally) occurred because of duplicate JSF jars in your application and some classloader issues. Could you please check your application that has any duplicate JSF (myfaces for example) JARS? Regards. Gurkan On Mon, Jul 16, 2018 at 2:54 PM, Emmanuel Touze

java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot be cast to org.apache.xml.dtm.DTMManager

i have a couple of problems... i have not been able to upgrade from TomEE 7.0.3 to 7.0.4 or 7.0.5 due to the error (it works fine in 7.0.3) java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot be cast to org.apache.xml.dtm.DTMManager which occurs when i run the follow

Re: No Factories configured for this Application. This happens if the faces-initialization does not work at all

Hi, Thanks for the detailed email with context and useful information. Is it random, or can you reproduce easily? Are you using JDK 8? Regards Jean-Louis -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Jul 16, 2018 at 1:54 PM, Emmanuel Touzery < emmanu

Re: cannot use ManagedExecutorService resource

yes, note that "name" doesn't need "java", the namespace is a "lookup" thing. personally I would recommand you to stay away from default resources since you have no idea how it will behave at runtime and I would just ensure to name correctly each resource I use. Romain Manni-Bucau @rmannibucau

Re: cannot use ManagedExecutorService resource

Many thanks for the fast and detailed answer! Do I understand correctly that I can simply use the default name in the resource.xml to extend the thread pool and should be able to use it everywhere I used to access the default service with default settings? @Resource(name="java:comp/DefaultManaged

Re: cannot use ManagedExecutorService resource

Hi yes, this is normal. TomEE defines defaults and you can override them. To supports all cases the defaults are auto-adjusted to the "prod" (hardcoded) resources - very handy in tests. If you don't activate openejb.offline=true then this is the behavior you have, if you set it then no implicit/de

No Factories configured for this Application. This happens if the faces-initialization does not work at all

Hello,     we have a TOMEE 7.0.3 application, which uses also JMS, which works without issues. We've recently made a new version of the application (one of the notable changes is a migration from using the JMS1.1 to the JMS2 API).     With the new version, we have an issue, but only on our P

cannot use ManagedExecutorService resource

Hi, we have problems using ManagedExecutorService resources in tomee 7.0.4 Using default ManagedExecutorService works fine, but if we try to define a new pool with more threads we cannot access the service In resource.xml we do this: Core = 40 Max = 50 KeepAlive = 5 s Queue = 150