WebListener | based web server | Command Line Interface library

I solved it, by registering the responces at main activity, as:

The only way to disable a listener annotated with @WebListener in the WEB-INF/classes folder is to disable annotation scanning altogether through the metadata-complete attribute in the WEB-INF/web.xml descriptor:

I think you just use the forward of getRequestDispatcher :

Exemple:

Because of transitive dependencies are not included when dependency is provided, so I had to restructure the modules this way.

Modules:

• app (pom)
• app-ear
  • jasperreports (compiled) MOVED FROM APP-COMMONS
• app-back
  • app-commons (provided)
• app-front
  • app-commons (provided)
• app-commons ...

I was not able to change app-commons dependency to compiled because it is dependent of app-front and app-back. In app-commons as compiled I have an @ApplicationScope class that it would produce ambiguous Beans pointing to the class in app-commons because of jakartaee context management.

I'm confused. You've configured the persistence unit to point to a data source managed by your container (java:global/mariadb) and also configured the JDBC properties? You have to make up your mind, either use the datasource provided by the container or configure it yourself, but not both at the same time (in other words, the jta-data-source property is mutually exclusive with the javax.persistence.jdbc.* properties).

You're getting the error because you've set the persistence unit to use JTA, and then you're trying to begin a transaction somewhere using em.getTransaction(), which is not allowed for JTA. Also, you put @PersistenceContext on top of entityManager, which means right after the constructor gets invoked, the entityManager is probably getting overwritten by an injected instance.

The solution is, assuming you do actually want to use JTA, to inject the EntityManager using @PersistenceContext (you shouldn't have to initialize it manually), and then annotating the methods that you want to execute atomically with @Transactional, instead of trying to use entityManager.getTransaction().

Class initializer blocks static { ...} run as a part of the class loading process. Normally classes are loaded on demand, when they are needed. If nothing in your code uses the ConnectionUtil class, it's never loaded, and the initializer block never runs.

Add a static method to ConnectionUtil and call it from BaclkgroundJobManager. The method doesn't have to do anything, but having it will ensure that the class gets loaded.

Another possibility is to load the class using the reflection API

A common problem with ScheduledExecutorService is that if the scheduled command throws an exception, the exception is silently swallowed. The code in the question does not seem to throw exceptions, but in more complex code it is difficult to avoid (for example unexpected NullPointerExceptions)

A quick fix is to put all of the Runnable.run method in a try-catch block:

My temporary solution for this problem is I removed apostrophe, semi-colon, quotes, hyphen from my site. Now it's working fine post are loading fully. In JSON data hyphen is encoded as – In webview only "&" is shown after this remaining lines are gone. So I managed to remove special characters.

You need to use an XML Spring configuration; a Java configuration won't work. See "Unable to obtain SessionCookieConfig".