So far, we’ve covered Maven deployment of Java EE EAR to Glassfish 3.x, JBoss 5.x & 6.x. In this article, I’m going to show you how to deploy the EAR through Maven to Oracle’s WebLogic (both 10.3.x and 12.x). I truly have to give credit to the WebLogic team as regardless of the area of Maven deployment or Maven Java EE project dependency, WebLogic is by far the easiest and the simplest among all of the Application Servers that I have dealt with in terms of Maven. Although the production licenses are a little pricy, but remember this, what you pay is what you get.
(more…)
I was performing a Java EE App migration to Weblogic 10.3.6, that worked very well in other Java EE Application Servers. The Java EE App runs on MySQL DB. Unfortunately, there was this annoying little problem that caused the whole application to fail. Everytime when I deploy the EAR, it gives an exception stack like the below:
(more…)
We’ve discussed the Deployment to Glassfish 3.x in Part 3 of the series. In this article, we’ll do Maven deployment to JBoss AS 5.x and JBoss AS 6.x. For readers regardless if you are new to the series or had been following it, you don’t have to finish reading all the article parts before coming to this, all you have to do is to first complete or understand Part 1 and Part 2 of the series (you can skip Part 3) before carrying out the deployment steps for JBoss Application Server in this article.
(more…)
Things have changed since the JBoss team officially adopted HornetQ as their messaging module on the Application Server Version 6 onwards. This is just a short note for the developers who need to get the Queue/Topic and custom connection factories working in the nick of time. This is for non-XA and non-Clustered only.
(more…)
This is just a short reference for the impatiens or people who are always forgetful (like me) when it comes to getting the connection factories, queues and topics working on JBoss 5.x Application Server. This short note is good for developers who need to get JBoss 5.x running in the nick of time for their MDB/JMS development. This is a non-XA and non-Clustered setup configuration.
(more…)
In Part 1 and Part 2 of this series, we have discussed about the directory layout and the Java EE demo project source codes that we had and further to be used to demonstrate the whole Java EE project development and deployment through Maven. From this part onwards, I will only be writing Application Server specific deployment configuration in Maven (using the contents from Part 1 and Part 2), at the same time, utilizing various plugins that are available. In this part, it is specifically about the deployment of the demo Java EE 5 project to Glassfish Ver 3.x Application Server. Again, for folks how came to this article directly, I would highly suggest that you read both Part 1 and Part 2 of this series to know what’s had been going on.
In the previous part: Building and Deploying Java EE EAR with Maven to Java EE Application Server (Part 1) – Project Directory Structure & Module Generation Through archetype:generate of the series, we have lay down the directory structure for the Java EE EAR project through Maven’s archetype:generate command. In this part, we’ll be dwelling into where to place the source codes and we’ll discuss the the necessary dependency and plugins that are needed to be included in the respective pom.xml files. For those who are reading for the first time, I highly suggest that you read from Part 1 and for those whom had been following us, if necessary, you may need to refer back and forth from the first part of the series to this part of the series as to iron out the glitches of understanding.
(more…)
Maven wasn’t very popular and wide used when it was first released, but after version 2, it had gain lots of traction amount Java developers and it then became widely used as a project build and management tool not only for private projects, but we can also see that there are a tremendously large amount of open source projects being managed, maintained and build by Maven.
(more…)
This is just a quick fix post for those whom are having this problem when running JBoss 6.x with Netbeans 7.x.
(more…)
This is the last part in the series of “Making sense of EJB3.x Transaction Attributes“. So far, we’ve discussed transaction attribute type REQUIRES_NEW, MANDATORY, SUPPORTSand NOT_SUPPORTED. Here, we’ll cover the last attribute which is “NEVER“. The NEVER transaction attribute type is a simple one, but yet sometimes, it is difficult and confusing to where it can be applied in your Java EE project. This is a very short article with no code samples except to tell you where I think the NEVER transaction attribute type should be used.
(more…)