This week we set up a developoment environment on a new PC for a JavaEE project using Tomcat 8.5 (we downloaded the recently released version 8.5.49 to be specific). We started up the IDE, deployed the WAR on a Tomcat server and ran into the following error: javax.faces.view.facelets.TagAttributeException: […] Could not Resolve Variable [Overflow]: … After some research using our favorite search engine we came across: https://stackoverflow.com/questions/35372187/jsf-uiinclude-recursion-causes-java-lang-stackoverflowerror and http://balusc.omnifaces.org/2016/02/recursive-tree-of-composite-components.html So… sounds like there is a recursive file include? Strangely some weeks ago the project ran on our old developoment environment that had a Tomcat 8.5.14… Also these posts were relatively…

The container management system Docker is quite useful for running services or applications in a controlled, isolated environment. In a lot of situations it is also useful to have directories inside a docker container mapped to a local folder on the host system. Especially in a development environment, where this setup allows you to modify source files (e.g. for a web application) in the host-volume directly in your IDE, and have the running docker service find those updated files immediately without the need for a deployment. Although Docker containers usually run Linux binaries, there is also the “Docker Desktop” suite…

This article describes how to bundle a database driver and the datasource configuration into an enterprise archive (EAR).  In my case I used WildFly 15 and MariaDB JDBC Client as the database driver for MySQL. The Java MySQL JDBC driver is under the GPL license and cannot be bundled into the application (at least for me).

While working on automatically deploying a maven artifact to a WildFly server using the WildFly Maven Plugin, I could not find a full working example on the corresponding webpage. It took quite some time, even if it is not much code. Below is everything you need to deploy a maven artifact to WildFly.

For a testing platform, we a have a typical basic authentication in front of our actual platform. The application server is a WildFly 14 with PrimeFaces as the frontend framework. In order for every JavaScript file not being downloaded separately, we also use the CombinedResourceHandler from OmniFaces. However, on this beta platform we always got a 401 response for the request of  the combined Javascript in Internet Explorer.

This blog post solves an error I encountered while trying to display some data in a PrimeFaces line chart graph (Version 6.2). Each time I opened the page with the graph, the Browser crashed with an “Out of Memory” message in the console. The error always occurred in Primeface’s chart.js