When it comes to the Java EE 7 Batch Processing facility, there are 2 ways in passing properties / parameters to the chunks and batchlets. This quick guide shows you the 2 ways, which could be use very frequently when developing batch processing the Java EE 7 way. (more…)
REST has made a lot of conveniences when it comes to implementing web services with the already available HTTP protocol at its disposal. By just firing GET, POST and other HTTP methods through the designated URL, you’ll sure to get something done through a response out of a REST service. But whatever conveniences which REST has given to the developers, the subject of security and access control should always be addressed. This article will show you how to implement simple user based authentication with the use of HTTP Headers and JAX-RS 2.0 interceptors. (more…)
Java EE REST application usually works well out of the box on a development machine where all server side resources and client side UIs point to “localhost” or 127.0.0.1. But when it comes to cross domain deployment (when the REST client is no longer on the same domain as the server that host the REST APIs), some work-around is required. This article is about how to make Cross Domain or better known as Cross-origin Resource Sharing a.k.a CORS work when it comes to Java EE 7 / JAX-RS 2.0 REST APIs. It is not the intention of this article to discuss about browser and other security related mechanisms, you may find this on other websites; but what we truly want to achieve here is again, to get things working as soon as possible. (more…)
I have posted this on stackoverflow.com, but I’m posting this here for other readers and myself as a reference just in case anybody bump into this issue. This as a short solution/workaround for those who encounters error in using Datastax’s Java Driver on Glassfish 4 through Maven deployment. (more…)
This is a quick tutorial especially for Windows users who would like to configure Ubuntu Linux to only allow SSH private/public key access and it is also a HowTo for Windows users to access Ubuntu Linux with only SSH private/public key. (more…)
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.
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:
There was a web application project, PHP in nature, that my team and I had developed for the past couple of months and it was time to setup and move all of the application to the production server which is running on Ubuntu Linux. The application data stored in MySQL is a combination of both English and the Chinese Simplified characters (because of bilingualism). Unfortunately, most of our selenium functional test failed right after we ran it and we’d discovered that any form of data gotten from the MySQL database was displayed only with ???? characters for the data in the Chinese language. This caused me to look for a solution and I’m happy to document this in case some poor souls out there encounter the same problem as we did.
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.
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.
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.
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.
This site consists mainly of articles and tutorials on some specific areas of Java EE, Unix-es, DBs (Oracle, MySQL, etc.) and Java EE App Servers.