tomee

TOMEE + Spring + JAX-RS (NoSuchMethodError) jar conflict

由 喜你入骨 提交于 2019-12-08 10:48:45
问题 I am trying to run my application in TomEE server, After much hassles I am able to run the application. However for some reason I am getting some sort of jar conflict for resteasy and hence an error as below whenever a resteasy resource class is being called from application Jun 05, 2015 5:57:34 AM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet [resteasy-servlet] in context with path [/MyApplicationName] threw exception [Servlet execution threw an

How to configure ActiveMQ memory settings under Apache Tomee?

由 五迷三道 提交于 2019-12-08 09:50:39
问题 I have an embedded ActiveMQ under Apache TomEE. TomEE configures JMS in a file called tomee.xml, in my case, it's configured like this <Resource id="Default JMS Resource Adapter" type="ActiveMQResourceAdapter"> BrokerXmlConfig = broker:(tcp://localhost:61616)?persistent=true ServerUrl = tcp://localhost:61616 DataSource = MyDataSource </Resource> Now, I'd like to specify custom memory settings, which is done in the activemq.xml file. TomEE can load activemq.xml configuration using Spring

TomEE, EJB and virtual-hosts

由 痴心易碎 提交于 2019-12-08 07:16:50
问题 I am simulating multiple TomEE (1.7.1) instances using virtual-hosts. I have multiple virtual-hosts that are deploying the same war with the same EJBs. This leads to: org.apache.openejb.DuplicateDeploymentIdException: Application cannot be deployed as it contains deployment-ids which are in use Any suggestions on how to solve this? 回答1: did you try openejb.deploymentId.format = {appId}/{ejbJarId}/{ejbName} in conf/system.properties? To make it even more portable coming 1.7.2 (release process

JSF/Primefaces ajax request returning response with HTTP 200 but intermittently not reaching the server

由 两盒软妹~` 提交于 2019-12-08 03:29:53
问题 I have developed a JSF/Primefaces application with the following stack: MyFaces JSF 2.2 Primefaces 6.0 TomEE 7.0.4 JDK 8 This application is using different Primefaces components. Apart from page navigation, all actions are performed ajaxically. The functionalities are working fine in my dev environment; I use Debian. When the application was deployed in the UAT server, which is CentOS; the ajax actions are not working properly. I can see in the browser's dev tool's networking that the

java.lang.IllegalStateException: Could not find backup for factory javax.faces.context.FacesContextFactory

由 谁说我不能喝 提交于 2019-12-07 19:57:48
问题 I'm getting the java.lang.IllegalStateException: Could not find backup for factory javax.faces.context.FacesContextFactory. when I deploy my webapp as a .war. Does anyone have an idea where to begin looking for the root cause of this problem? The application runs as expected in the Eclipse IDE, but when exported as a war for deploying on the publicly available stand-alone TomEE environment, it fails. Many thanks. My configuration: Apache TomEE - WebProfile 1.6.0.2 JSF 2.2.7 (com.sun.faces)

Configuring data source - tomee.xml, persistence.xml

由 廉价感情. 提交于 2019-12-07 16:59:06
问题 I'm doing some EJB with JPA project that maps/persists some entities to mysql database. I have defined persistence unit in persistence.xml like this: <persistence-unit name="MyAppPU" transaction-type="JTA"> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider> <jta-data-source>MyAppDS</jta-data-source> <properties> <property name="openjpa.jdbc.SynchronizeMappings" value="buildSchema(ForeignKeys=true)" /> <property name="openjpa.jdbc.DBDictionary" value="mysql" />

How to use Jackson as JSON provider for JAX-RS-Client instead of Johnzon in TomEE 7?

由 喜夏-厌秋 提交于 2019-12-07 11:40:32
问题 I use TomEE 7.0.1 with Jackson 2 as JAX-RS JSON provider (configured in openejb-jar.xml ). Posting json to jax-rs services works perfectly well and uses the jackson annotations. But using JAX-RS client (or cxf webclient) always uses Johnzon even if I provide Jackson to the Webclient.create method. After some debugging I am sure that TomEE adds Johnzon to the client factory somehow and no other message body parser for json can be used. Is this a bug with the TomEE CXF integration or do I miss

java.lang.IllegalStateException: Could not find backup for factory javax.faces.context.FacesContextFactory

由 。_饼干妹妹 提交于 2019-12-06 13:49:40
I'm getting the java.lang.IllegalStateException: Could not find backup for factory javax.faces.context.FacesContextFactory. when I deploy my webapp as a .war. Does anyone have an idea where to begin looking for the root cause of this problem? The application runs as expected in the Eclipse IDE, but when exported as a war for deploying on the publicly available stand-alone TomEE environment, it fails. Many thanks. My configuration: Apache TomEE - WebProfile 1.6.0.2 JSF 2.2.7 (com.sun.faces)(Mojarra lib 2.2.0) <-- This may be a problem? But why does the app run in the Eclipse environment but not

Configuring data source - tomee.xml, persistence.xml

由 徘徊边缘 提交于 2019-12-06 01:32:57
I'm doing some EJB with JPA project that maps/persists some entities to mysql database. I have defined persistence unit in persistence.xml like this: <persistence-unit name="MyAppPU" transaction-type="JTA"> <provider>org.apache.openjpa.persistence.PersistenceProviderImpl</provider> <jta-data-source>MyAppDS</jta-data-source> <properties> <property name="openjpa.jdbc.SynchronizeMappings" value="buildSchema(ForeignKeys=true)" /> <property name="openjpa.jdbc.DBDictionary" value="mysql" /> <property name="openjpa.Log" value="DefaultLevel=WARN, Tool=INFO" /> </properties> </persistence-unit> Then,

How to use Jackson as JSON provider for JAX-RS-Client instead of Johnzon in TomEE 7?

由 被刻印的时光 ゝ 提交于 2019-12-05 17:01:47
I use TomEE 7.0.1 with Jackson 2 as JAX-RS JSON provider (configured in openejb-jar.xml ). Posting json to jax-rs services works perfectly well and uses the jackson annotations. But using JAX-RS client (or cxf webclient) always uses Johnzon even if I provide Jackson to the Webclient.create method. After some debugging I am sure that TomEE adds Johnzon to the client factory somehow and no other message body parser for json can be used. Is this a bug with the TomEE CXF integration or do I miss something? Romain Manni-Bucau Johnzon is registered on the bus by default to have a default JSON
订阅 tomee