Some time ago Adam Bien published on his blog the recording of the presentation delivered by him on the 33rd Degree Conference 2014 in Kraków. I was on the conference and this is the presentation I most liked. The exact title of the show is Rethinking Packaging, Modularization, Interfaces with Plain Java EE 7.
Some time ago when I was preparing for the Java EE 5 Business Component Developer exam I wrote few lines of code for exercise. I decided to make an order with the code to create a Java EE application. I believe it can bring an education value for those people who plan to attempt the exam or just want to learn JEE. I shared the Java EE application in github jee-bankapp. It is just named jee-bankapp because it implements bank account basic operations. This is not a full-working application to operate on an account. It is rather a skeleton which takes advantages of different JEE possibilities. Best practices are not always here followed whereas most emphasis is put on various approaches to JEE implementation.
There is created a separated page dedicated to this JEE app. You can expect that this page will be updated.
Collecting and analyzing results
In this post are executed EJB performance tests on the technical infrastructure designed in PART I. The aim of these tests is to perform local and remote calls between EJB components and collect information about time spent on these calls. In the beginning is given a brief introduction to a business interface then is elaborated a test scenario. The last part is a result presentation and an attempt to define final conclusion.
Technical infrastructure development
It is an obvious fact that local EJB calls are more efficient than remote. The aim here is to observe the difference between these calls in terms of time and resources consumption and finally provide observation results. In this post is given an overview and an explanation of a technical infrastructure with a goal to measure both local and remote EJB calls. The infrastructure consists of Java EE application suites and two managed servers running on Oracle WebLogic application server.
EJB components differ from Spring beans on the technical background whereas their concept is quite similar. The technical diversity might be an issue when composing dependencies between these two bean types. The purpose of this post it to give an idea to design solutions based on a mutual EJB and Spring beans interoperability. There are taken into account two main concerns: accessing EJB components from Spring beans and accessing Spring beans from EJB components. The post introduces technical aspects referring to a simple enterprise application implementing beans cooperation.
The way of loading a Spring Application Context in Java Web Applications and JSE applications is commonly known. For web applications packaged in WAR files, in a web.xml file need to be declared a ContextLoaderListener and a contextConfigLocation context parameter which refers to XML Spring Application Context configurations. On the other hand, for JSE applications a Spring Application Context is loaded manually in code.
This article tries to present how to design a Java EE application that gives a possibility to load a Spring Application Context without using a WebApplicationContext. It is not always required to have a web nature of a Java enterprise application.