Skip to content
Advertisement

Tag: apache-tomee

Gradle, Apache TomEE – TomEEWebappClassLoader loader constraint violation

The gradle project runtime at Apache TomEE plus has the error java.lang.LinkageError: loader constraint violation: loader (instance of org/apache/tomee/catalina/TomEEWebappClassLoader) previously initiated loading for a different type with name “javax/faces/context/ExternalContext” at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:756) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(WebappClassLoaderBase.java:2489) at org.apache.catalina.loader.WebappClassLoaderBase.findClass(WebappClassLoaderBase.java:875) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1376) at org.apache.tomee.catalina.TomEEWebappClassLoader.loadClass(TomEEWebappClassLoader.java:184) at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1220) at org.apache.tomee.myfaces.TomEEWebConfigProvider.getFacesServletMappings(TomEEWebConfigProvider.java:36) at org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:163) at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:103) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4766) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5230) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)

TOMEEE – Can’t lookup ejb

I have implemented a basic EJB Object in my code. Then I created a jar for this ejb. The jar file contains: package containing the ejb classes (home interface/remote bean interface/bean implementaion) META-INF folder containing the ejb-jar.xml ejb-jar.xml Then I deployed the EJB by placing the jar in webapps folder and from the server logs it seems to have been

Advertisement