How to install and use CDI on Tomcat?

Question

I'm creating my first project Java EE 7, but I'm having trouble. Appreciate any help.

Tomcat 7.0.34
JSF 2.2
Primefaces 3.5
javaee-api-7.0.jar

When the application start, the Tomcat log shows the following message:

"validateJarFile (C:\...\build\web\WEB-INF\lib\javaee-api-7.0.jar)-jar not loaded. See Servlet 2.3 Spec, section 9.7.2. Offending class: javax/servlet/Servlet .class"

when I click on the button that calls the managed bean, I get the error:

Advertência: /index.xhtml @18,66 value="#{indexMB.user}": Target Unreachable, identifier 'indexMB' resolved to null
javax.el.PropertyNotFoundException: /index.xhtml @18,66 value="#{indexMB.user}": Target Unreachable, identifier 'indexMB' resolved to null

IndexMB

@Named("indexMB")
@RequestScoped
public class IndexMB {

private String password;
private String user;

public String loginTest(){
    return (this.user.equals("admin") ? "adminPage" : "inOutPage");
}

// getters and setters
}

index.xhtml

<html ...>

<f:loadBundle basename="i18n" var="bundle" />
<h:head>
    <title>#{bundle['index_title']}</title>
</h:head>
<h:body>
    #{bundle['index_appname']}
    <br />
    <h:form id="frmIndex">
        <p:panelGrid columns="2">
            <p:outputLabel for="user" value="#{bundle['lblUser']}" />
            <p:inputText id="user" value="#{indexMB.user}" />

            <p:outputLabel for="password" value="#{bundle['lblPassword']}" />
            <p:password id="password" value="#{indexMB.password}" />
        </p:panelGrid>
        <p:commandButton action="#{indexMB.loginTest}" value="#{bundle['btn_login']}" />
    </h:form> 
</h:body>

faces-config.xml

<?xml version='1.0' encoding='UTF-8'?>
<faces-config version="2.2"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd">

<application>
    <locale-config>
        <default-locale>pt_BR</default-locale>
        <supported-locale>en</supported-locale>
        <supported-locale>fr</supported-locale>
    </locale-config>
</application>

These topics have not helped me:

Thank's @Kalathoki, file added. Almost nothing, because I'm using annotations. — Rogério Arantes, Sep 25 '13 at 04:30

BalusC · Accepted Answer · 2020-11-08T17:30:03.603

Tomcat as being a barebones JSP/Servlet container doesn't support CDI out the box. How exactly did you install CDI? Did you really drop javaee-api.jar in /WEB-INF/lib just to get your code to compile? Oh please no, this is not the right way. The Java EE API JAR contains solely the API classes, not the concrete implementation. Get rid of the whole JAR. It can cause many other portability troubles like as the ones described in this answer: How do I import the javax.servlet API in my Eclipse project? You should actually be installing the concrete implementation along with the specific API.

You have 2 options:

Drop Tomcat and go for a true Java EE container. As you're using Tomcat, just step over to TomEE. It's really simple, download the TomEE web profile zip file, extract it and integrate it in Eclipse exactly the same way as you did for Tomcat. Don't forget to remove the Java EE JAR file from webapp and alter the Targeted Runtime property in project's properties from Tomcat to TomEE so that Java EE dependencies are properly resolved.

No additional JARs or configuration is necessary. You can even remove the JSF JARs from your webapp. TomEE as being a true Java EE container already provides among others JSF and CDI out the box. In case you're using Maven, the below coordinate is sufficient.
```
 <dependency>
     <groupId>javax</groupId>
     <artifactId>javaee-web-api</artifactId>
     <version></version>
     <scope>provided</scope>
 </dependency>
```
Note the importance of provided and its meaning as in "the target runtime already provides this out the box". See also How to properly install and configure JSF libraries via Maven?.
Install a true CDI implementation on Tomcat. Weld is one of the available CDI implementations. In the Weld installation guide you can find instructions how to integrate it in Tomcat. For sake of completeness and future reference, here are the steps:
1. Drop the weld-servlet-shaded.jar in webapp's /WEB-INF/lib. In case you're using Maven, use this coordinate:
```
 <dependency>
     <groupId>org.jboss.weld.servlet</groupId>
     <artifactId>weld-servlet-shaded</artifactId>
     <version>3.1.5.Final</version>
 </dependency>
```
2. Create /META-INF/context.xml file in webapp with following content:
```
 <Context>
     <Resource name="BeanManager" 
         auth="Container"
         type="javax.enterprise.inject.spi.BeanManager"
         factory="org.jboss.weld.resources.ManagerObjectFactory"/>
 </Context>
```
  Note that this step is not strictly necessary when you're using Mojarra 2.2.11 or newer as it will be able to find it via ServletContext when absent in JNDI.
3. Create a /WEB-INF/beans.xml file in webapp. It can be kept empty.
4. Only if your web.xml is declared conform Servlet version 4.0 instead of 3.1, then you also need to put the @javax.faces.annotation.FacesConfig annotation on an arbitrary CDI managed bean somewhere in the project (usually the one representing the "application-wide config" would be OK).
```
 package com.example;

 import javax.enterprise.context.ApplicationScoped;
 import javax.faces.annotation.FacesConfig;

 @FacesConfig
 @ApplicationScoped
 public class Config {
     // ...
 }
```
  It is indeed utterly unnecessary, but it is what it is.
That's it (note: in older Weld Servlet versions, you'd need to explicitly register the CDI bean manager and Weld listener in web.xml too, but that's unnecessary with current versions).

In case you prefer OpenWebBeans above Weld as CDI implementation, head to this blog for detailed Maven installation instructions: How to install CDI in Tomcat?

Unrelated to the concrete problem, the JSP/Servlet APIs of Tomcat 7 do not comply those APIs of Java EE 7, instead it complies Java EE 6 (Servlet 3.0 / JSP 2.2). If you want the Tomcat equivalent of Java EE 7 (Servlet 3.1 / JSP 2.3), then you should be looking at Tomcat 8. See also Apache Tomcat version matrix.

As I said, "it's my first Java EE 7 project". Thank you very much. — Rogério Arantes, Sep 25 '13 at 12:55
I switched to TomEE, but to initialize it shows the following error: `com.sun.faces.config.ConfigurationException: Factory 'javax.faces.application.ApplicationFactory' was not configured properly.` I saw the topic [could not find Factory: javax.faces.context.FacesContextFactory](http://stackoverflow.com/questions/7886035/could-not-find-factory-javax-faces-context-facescontextfactory), but it didn't help. Any comments? — Rogério Arantes, Sep 26 '13 at 02:41
I switched to Glassfish 4 and I got the same initial error (`Target Unreachable, identifier 'indexMB' resolved to null`). I removed javaee-api-7.0.jar . Comments? — Rogério Arantes, Sep 26 '13 at 02:53
As to TomEE, it already bundles JSF (MyFaces). If you still bundle another JSF impl in your webapp, then you get exactly this exception. Just remove JSF JARs from your webapp. As to GlassFish 4, not sure on that, but it's likely also caused by a dirty classpath. — BalusC, Sep 26 '13 at 11:02
Proceeding. ... The startup errors on TomEE stopped, but now the JSF does not load (though not display no error on log). GlassFish maintains the initial error. The only libs loaded are: primefaces-3.5.jar, commons-io.jar, commons-fileupload.jar — Rogério Arantes, Sep 27 '13 at 01:52
Looking best, the startup errors on TomEE console stopped, but TomEE log shows `Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener java.lang.NoClassDefFoundError: com/sun/faces/config/configprovider/MetaInfFaceletTaglibraryConfigProvider`, and JSF does not load. — Rogério Arantes, Sep 27 '13 at 02:45
Even so, for CDI 1.2 and JSF 2.2, we only need Servlet 3.0. I did not try, but that should mean that we can deploy those on Tomcat 7. — YoYo, Nov 02 '14 at 02:42
For me this was not enough. I'm not using CDI at all, but rather Spring, but I want OmniFaces 2+. I'm getting `javax.naming.NamingException: WELD-001300: Unable to locate BeanManager`. So additionally to the above instructions I had to introduce at least 1 stub CDI bean annotated with `@javax.inject.Named` to be located under `/WEB-INF/classes` to get it fixed. — Pavel S., Jun 28 '16 at 11:52

score 0 · Answer 2 · answered Jun 03 '14 at 12:27

0

Other possible option is leaving beans.xml in your deployment.

answered Jun 03 '14 at 12:27

lucasvc

624
1
9
31

How to install and use CDI on Tomcat?

2 Answers2

Linked

Related