apache-tomee

Using TomEE and open JPA, i get the following error: SEVERE: JAVA AGENT NOT INSTALLED

末鹿安然 提交于 2021-02-19 07:45:08
问题 I'm getting the following error using TomEE and JPA: SEVERE: JAVA AGENT NOT INSTALLED. The JPA Persistence Provider requested installation of a ClassFileTransformer which requires a JavaAgent. See http://openejb.apache.org/3.0/javaagent.html Is having a java agent required for openJPA to function properly? (Specifically is it needed for "openjpa.jdbc.SynchronizeMappings") If so, how do I install it properly in eclipse? 回答1: -javaagent:openejb-javaagent-3.0-beta-2.jar Add that to your VM

Tomcat/TomEE SSL config with Cloudflare

拈花ヽ惹草 提交于 2021-01-05 07:04:45
问题 I have been having problems with the correct way to configure tomee with cloudflare provided SSL. First time doing this, so here is the situation: 1) First i create the keystore file: keytool -keysize 2048 -genkey -alias tomee -keyalg RSA -keystore tomee.keystore 2) Then i import the generated keystore: keytool -importkeystore -srckeystore tomee.keystore -destkeystore tomee.keystore -deststoretype pkcs12 3) After importing, I create the CSR file for issuing a certificate request: keytool

CDI | Application / Dependent Scope | Memory Leak - javax.enterprise.inject.Instance<T> Not Garbage Collected

被刻印的时光 ゝ 提交于 2020-08-24 08:17:59
问题 I am using Instance as a lazy / dynamic injector in a TomEE Java application, and I have noticed a memory leak in my application. This is a first for me, so it's actually surprising to see a memory leak warning that has been outlined in the Java EE Library : package javax.enterprise.inject; public interface Instance<T> extends Iterable<T>, Provider<T> { /** * Destroy the given Contextual Instance. * This is especially intended for {@link javax.enterprise.context.Dependent} scoped beans *

CDI | Application / Dependent Scope | Memory Leak - javax.enterprise.inject.Instance<T> Not Garbage Collected

杀马特。学长 韩版系。学妹 提交于 2020-08-24 08:17:19
问题 I am using Instance as a lazy / dynamic injector in a TomEE Java application, and I have noticed a memory leak in my application. This is a first for me, so it's actually surprising to see a memory leak warning that has been outlined in the Java EE Library : package javax.enterprise.inject; public interface Instance<T> extends Iterable<T>, Provider<T> { /** * Destroy the given Contextual Instance. * This is especially intended for {@link javax.enterprise.context.Dependent} scoped beans *

how to make java - tomee application HTTPS? [closed]

只谈情不闲聊 提交于 2020-08-10 22:59:33
问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed 2 years ago . Improve this question I have been developing a web application with java and apache tomee, but I want to make it https so I can offer it to a few clients but I have no idea on how to create the certificates and make the application go through a secure channel. I have tried a few

How to avoid XOP generation in CXF - behaviour changed between 3.3.2 and 3.3.4

岁酱吖の 提交于 2020-08-10 19:15:25
问题 This issue involves recent CXF change (3.3.2->3.3.4). We are sending a SOAP request to our partner with image contents On TomEE 8.0.0 (CXF 3.3.2), the SOAP request generated doesn't include XOP generation : <ns3:Picture> <ns6:Image> <ns6:StorageFormat>JPG</ns6:StorageFormat> <ns6:Length>13286</ns6:Length> <ns6:Buffer>/9j/4AAQSkZJRgABAAEAlgCWAAD//gAfTE (...) VBRCB=</ns6:Buffer> </ns6:Image> </ns3:Picture> <ns3:Signature> <ns6:Image> <ns6:StorageFormat>TIF</ns6:StorageFormat> <ns6:Length>700<

How to avoid XOP generation in CXF - behaviour changed between 3.3.2 and 3.3.4

痴心易碎 提交于 2020-08-10 19:15:07
问题 This issue involves recent CXF change (3.3.2->3.3.4). We are sending a SOAP request to our partner with image contents On TomEE 8.0.0 (CXF 3.3.2), the SOAP request generated doesn't include XOP generation : <ns3:Picture> <ns6:Image> <ns6:StorageFormat>JPG</ns6:StorageFormat> <ns6:Length>13286</ns6:Length> <ns6:Buffer>/9j/4AAQSkZJRgABAAEAlgCWAAD//gAfTE (...) VBRCB=</ns6:Buffer> </ns6:Image> </ns3:Picture> <ns3:Signature> <ns6:Image> <ns6:StorageFormat>TIF</ns6:StorageFormat> <ns6:Length>700<

How can I configure the JAX-RS base path in TomEE+?

假装没事ソ 提交于 2020-08-09 09:37:27
问题 I have a WAR with some JAX-RS services, deployed into TomEE Plus. Given a service annotated with @Path("myservice") , TomEE+ publishes it to localhost:8080/mywebapp/myservice . However, that also makes accessing a JSP at localhost:8080/mywebapp/index.jsp impossible - JAXRSInInterceptor complains that No root resource matching request path has been found, Relative Path: /index.jsp . So I would like to configure a path prefix api to all services, which changes the myservice URL to localhost

Error executing TommEE 1.0 with JSF 2.0

血红的双手。 提交于 2020-01-06 15:00:53
问题 I'm trying use apache-tomee-1.0.0 with my JSF 2.0 web app... but I can't do it :(. My problem is when I run the server logs this error: 30-ago-2012 18:49:39 org.apache.catalina.core.StandardContext listenerStart GRAVE: Excepción enviando evento inicializado de contexto a instancia de escuchador de clase com.sun.faces.config.ConfigureListener java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! org.apache.openejb.jsf.CustomApplicationFactory at com.sun