9. JSF: Solving common problems

1. Target Unreachable, identifier [bean] resolved to null

When you reference a bean in a xhtml file with "#{bean.method}" and get this error, you should verify that:

The bean implements Serializable.
The references (javax.servlet-api.4.0.0, javax.faces.2.3.3, javax.el.api.3.0.1, org.primefaces.6.1) have been selected in your pom.xml
You have created the files bean.xml and faces-config.xml in the webapp/WEB-INF folder
You have used the correct annotations from CDI (javax.inject.Named and javax.enterprise.context.SessionScoped, ...) and not ManagedBean or jsf2.2 scopes.

2. Bean declaring a passivating scope must be passivation capable

This error causes server not starting and fills up the console with long chained exceptions. It is very annoying.

SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/OpenWebMaven]]
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 .....................
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/OpenWebMaven]]
 at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441)
 .....................
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-000072: Bean declaring a passivating scope must be passivation capable.  Bean:  Managed Bean [class openadmin.util.lang.LangUtils] with qualifiers [@Default @Any @Named]
 at org.jboss.weld.bean.ManagedBean.checkType(ManagedBean.java:216)
 at org.jboss.weld.bean.AbstractBean.initializeAfterBeanDiscovery(AbstractBean.java:108)
 at org.jboss.weld.bean.ManagedBean.initializeAfterBeanDiscovery(ManagedBean.java:122)
...................

Dec 06, 2017 7:38:04 PM org.apache.catalina.core.ContainerBase startInternal
SEVERE: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: A child container failed during start
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 ......
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:355)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)
Caused by: org.apache.catalina.LifecycleException: A child container failed during start
 at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:956)

This may be due to:

You have created a class annotated with @Named and @xxxscoped and is used as a utility class that only provides static methods.
A bean annotated with @Named and @xxxscoped has not been declared as "implements Serializable".
The solutions to previous error can be applied here.

3. Hibernate Validation annotations not used in DDL when creating entities

Hibernate JPA when is called from a Java Application, does not use Hibernate Validator annotations, but when used in a web environment they are used. See previous post or Stackoverflow.

4. Unexpected errors that make you think they are due to compilation or deployment processes

We are using Maven with Eclipse Oxygen. Some problems have been solved this way:

1. Take care that the files are correctly located. See these posts:

1.a Including additional files in Maven
1.b Creating a Maven Project.

2. In web projects, we need somewhat powerful computers. So the process of creating war or jar files can be slow. The deployment process may sometimes crash or have some residual files from older builds. Sometimes the process of building the project may be blocked and other times the application server (Tomcat) has not been initialized well. So when something strange happens, you should follow this steps:

2.a Stop server

2.b Right-click on the project-> Run As -> Maven Clean. (Once it failed and I had to delete a configuration file I don't remember which one)

2.c Right-click on the project-> Maven -> Update Project ->Select options as the next image

Wait for a moment until the process has finished. Now you can run your project. Most of the problems should have disappeared.

2.d If you continue having problems, make the servers window visible (Window-show View -Servers) and Right-click on the server and select:

2.d.1 Clean Tomcat Work Directory and also:
2.d.2 Clean

This should have solved nearly all your problems. (You have to wait for a moment too) and

2.e Restart Eclipse or maybe your computer.

3. Verify that the files are deployed well in the deployment folder. You can see where the deployment folder this way: Right-click a xhtml file -> Run Configurations -> Select the arguments tab and you can see the deployment folder

4. @OneToOne or @ManyToOne on references an unknown entity

In my case, the unknown entity is NOT in the persistence.xml as:

<class>openadmin.model.control.ClassNameEdu </class>

And I have excluded the classes that are not here by means of this XML sentence

<exclude-unlisted-classes>true</exclude-unlisted-classes>

As I use several persistence units, I don't want the entities to be created in every persistence unit. I want them to be created only in its own persistence unit.

5. Server fails to start with other projects deployed on the same server.

Remove all the projects from the server (except the project you want to execute) when your Run your application as "Run on server" (Select undesired project and Use remove button)

6. Server fails to start. Failed to start component .. Catalina. WELD-001414: Bean name is ambiguous. Name "anyName" resolves to beans managed Bean bean1 and managed bean bean2.

There are 2 beans with annotations @Named(value = "anyName") and have the same value in the annotation. So Tomcat rejects to start with 2 beans that have the same name reference. Change the value of the @Named annotation.

7. Pom-xml Missing artifact com.sun.xml.ws:jaxws-ri:jar:2.3.0

In this case I have this reference in the pom.xml that Eclipse complains as:

Missing artifact com.sun.xml.ws:jaxws-ri:jar:2.3.0

<dependency>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-ri</artifactId>
<version>2.3.0</version>
</dependency>

1. In StackOverflow is a possible solution to the problem. Basically Window - Show View - Other -Maven

Open Global Repositories and right-click on central (https://repo.mvane.apache.org/maven2)

Select Update Index and/or Rebuild Index

Take care that this operation can take a long time!!!

2. But the problem with this reference is that IT IS NOT A JAR. It should be referenced as another type,for instance pom

<dependency>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-ri</artifactId>
<version>2.3.0</version>
<type>pom</type>
</dependency>

8. SEVERE: A child container failed during start. java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@5b057c8c] at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)

The whole trace is:

SEVERE: A child container failed during start

java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@5b057c8c]

at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)

at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)

at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:947)

at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:839)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1425)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1415)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)

at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)

at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:941)

at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:258)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

at org.apache.catalina.core.StandardService.startInternal(StandardService.java:422)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:770)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

at org.apache.catalina.startup.Catalina.start(Catalina.java:671)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:564)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:355)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:495)

Caused by: org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@5b057c8c]

at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:441)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:139)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:173)

at org.apache.catalina.webresources.StandardRoot.startInternal(StandardRoot.java:724)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4758)

at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4893)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1425)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1415)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)

at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)

at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:941)

... 21 more

Caused by: java.lang.IllegalArgumentException: java.util.zip.ZipException: ZipFile invalid LOC header (bad signature)

at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:114)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)

... 33 more

Caused by: java.util.zip.ZipException: ZipFile invalid LOC header (bad signature)

at java.base/java.util.zip.ZipFile$ZipFileInputStream.initDataOffset(ZipFile.java:751)

at java.base/java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:761)

at java.base/java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:407)

at java.base/java.util.zip.InflaterInputStream.read(InflaterInputStream.java:159)

at java.base/java.io.InputStream.readAllBytes(InputStream.java:240)

at java.base/java.util.jar.JarFile.getBytes(JarFile.java:770)

at java.base/java.util.jar.JarFile.getManifestFromReference(JarFile.java:397)

at java.base/java.util.jar.JarFile.getManifest(JarFile.java:384)

at org.apache.catalina.webresources.AbstractSingleArchiveResourceSet.initInternal(AbstractSingleArchiveResourceSet.java:112)

... 34 more

Feb 16, 2018 6:38:21 PM org.apache.catalina.core.ContainerBase startInternal

SEVERE: A child container failed during start

java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: A child container failed during start