All geek questions in one place

Using Spring Pitchfork to have Java EE compatible code that runs in a non Java Java container

I came across a decision to drop a Java EE 5 container instead of using a web container (with Spring). According to interface 21, Spring Pitchfork allows you to use elements of the Java EE programming model in Spring. This way I get a subset of Java EE annotations inside the Spring container. Since I prefer to maintain compatibility with Java EE, this seems like an attractive option for me. What is your experience with Pitchfork and what have you done using it?

+3
source share
2 answers

No experience with Pitchfork, but a lot with Spring. Prior EJBs were not a problem. POJOs were more than adequate.

Two other alternatives:

You can use OpenEJB with Tomcat if you need EJBs, want to stick with Tomcat, and don't want to switch to a purchased or open Java EE application server.

You can try Spring dm Server with OSGi. Eat a shell and an egg - go all the way.

+1
source

I use forks to unit test EJB3 and JPA components outside the container, and it works very well. I can connect everything I need, including a transaction manager, a second level caching provider, etc.

+1
source

Source: https://habr.com/ru/post/1702475/

More articles:


All Articles