Weld, JSF 2.0 And Google App Engine

By: Karthik, Last Updated: May 22, 2017

When trying to build a Weld application to run in Google App Engine. Google have done a great job providing a richly featured cloud platform with plenty of good documentation and a helpful online community, and the free quotas they provide are more than enough for the average low traffic web site. If you are a typical Java EE developer though, you have to approach GAE development with a slightly different development mindset. To get started, you’ll need just 2 things – a JDK and Eclipse.Downloading the Google App Engine SDK Eclipse Plug-in

The GAE SDK is an essential ingredient for GAE app development. It handles all the work of setting up your project, enhancing your entity classes, running your app in local development mode and even deploying your app straight to the production GAE environment.

To install the SDK plug-in for Eclipse, you can follow the instructions here:http://code.google.com/appengine/docs/java/tools/eclipse.htmlFor the impatient though, here’s a summary of the installation steps (for Eclipse 3.5):1. Click the Help menu -> Install New Software2. In the Work with box, enter http://dl.google.com/eclipse/plugin/3.5 , then click the Add button then click OK.3. Expand the Plug-in entry and check the ‘Google Plug-in for Eclipse 3.5’ item, then expand the SDKs entry and check the ‘Google App Engine Java SDK 1.3.0’ item.4. Click the Next button, and accept any terms of service.5. Click the Finish button, wait for installation to complete and then when asked if you want to restart Eclipse, select ‘Yes’.

Create an App Engine account If you don’t have one already, then you’ll need a GAE account. They’re free; all you need is a Google account. So go to the following page and sign up: http://appengine.google.comOnce you’ve done that, you should be presented with the ‘My Applications’ screen, containing an empty list and a ‘Create an Application’ button:

Create an Application To be able to deploy an application to GAE, you need to give it a unique application identifier. Clicking the ‘Create an Application’ button will take you to the following screen, where you can enter your application identifier and a title for your application.

For the authentication options, you either have the choice of using Google Accounts which allows anyone with a Google account to sign in, or you can restrict your application just to the users of a Google Apps domain. We’re going to choose door number one, and allow any user with a Google account to sign in. Of course, if you don’t want to then you don’t have to require your users to sign in to your application at all (by not specifying any security restrictions for your pages, which we’ll get to a bit later). If you do want some kind of security though, the advantage of using the Google accounts API is that you don’t have to worry about building the screens, creating user/role entities, writing action code, etc for managing the users in your app – Google takes care of all that for you.

Creating the project Once you’ve created a new application with a unique application identifier, you’ll be presented with an ‘Application Registered Successfully‘ message. Click the ‘View the dashboard…’ link to view the dashboard for your new app:

Now that we’ve created our new app, it’s time to create the project. In Eclipse, click File -> New -> Web Application Project to get the following dialog:

Enter a project name and the default package for your classes. Uncheck the ‘Use Google Web Toolkit’ option (we’ll be using JSF 2.0 for our view) and then click Finish to create the new project. Then, right click on the new project in the Package Explorer and select Google -> App Engine Settings. In the ‘Application ID’ box, enter the unique application identifier that you registered for your application. For the Version, just enter 1, then click OK to save your settings. The values actually get saved in /war/WEB-INF/appengine-web.xml, so open this file up now and take a look at what it contains. Actually, there’s one more setting you need to add to this file, to be able to support user sessions in your app. Add the following line to the file: true The complete file should look something like this:

myapplication 1 true

Configuring JSF Like any servlet-based application, the web.xml file is where most of the important stuff is configured. JSF requires quite a lot of config, so let’s look at the options one at a time. By the way, Google actually have some documentation on configuring JSF 2.0 for GAE, so if you’re interested you can check it out here. The first thing we need to do is disable some of the multi-threaded stuff in JSF, as GAE doesn’t support multi-threaded applications. Add the following two entries to /war/WEB-INF/web.xml:

com.sun.faces.enableMultiThreadedStartup false

com.sun.faces.enableThreading false

Next, we need to configure the Faces servlet. This will alllow requests that end in the .jsf suffix to be handled by JSF:

Faces Servlet javax.faces.webapp.FacesServlet 1

Faces Servlet *.jsf

Next, we need to configure EL:

com.sun.faces.expressionFactory com.sun.el.ExpressionFactoryImpl

And we also need to tell JSF what the default suffix is for the files containing our view definitions:

javax.faces.DEFAULT_SUFFIX .xhtml

Finally, there’s a couple more options recommended by Google. From what I’ve read, version 1.3.0 onward of the SDK now supports server-side state saving, however I haven’t tried it yet so let’s just leave it as client-side for now – the reason for this is to avoid a DatastoreTimeoutException issue that can possibly render a user’s session broken until their session has expired (there’s a Google Groups thread on this subject here if you’re interested).

javax.faces.STATE_SAVING_METHOD client

The following option is mentioned on the JSF 2.0 and GAE compatibility issues page, and is required to prevent a ConfigurationException from occurring because of a threading issue:

javax.faces.PROJECT_STAGE Production

Once you’ve added all these options to web.xml, you also need to create a faces-config.xml file in the WEB-INF directory also. Thankfully in JSF 2.0 there is minimal configuration required, basically an empty file (although later you’ll be putting your navigation rules here):

Adding the JSF libs to your project Due to the way that JSF 2.0 checks if it can use InitialContext (see the processJndiEntries() method in WebConfiguration.java), we need to use a hacked version of jsf-impl.jar that comments out the body of the processJndiEntries() method. You can download a modified jsf-impl.jar from Josh Carrier’s blog, direct link here. Once you download it, place it in the WEB-INF/lib directory in your project. You’ll also need jsf-api.jar, which you can get from the JSF 2.0 distribution downloadable from this page, – once you get it stick it in the WEB-INF/lib directory also. We’ll also need to download the EL libraries. I couldn’t really find an official download page just for EL, so just download them straight from the java.net Maven repository: •http://download.java.net/maven/2/javax/el/el-api/2.2/el-api-2.2.jar• http://download.java.net/maven/2/org/glassfish/web/el-impl/2.2/el-impl-2.2.jarOnce you download them both put them in the WEB-INF/lib directory. Configuring Weld The configuration for Weld is quite simple, all you need to do is add the following entry to web.xml:

org.jboss.weld.environment.servlet.Listener

Next, create an empty file (no contents whatsoever) called beans.xml in the /war/WEB-INF directory. This is so Weld can find your beans. Getting the Weld libs is a little more work, unfortunately. We’ve made a few fixes to the Weld code to address some issues with running in GAE, so you can’t use the 1.0 download. The option here is to either a) build it yourself (which I’ll go through the steps for in a moment, since you might be impatient 😉 or b) wait for the 1.0.1.RC2 release, which should be out any day now.

Building Weld from SVNCompiling the Weld libs from source is really not as scary as many people think, all you need is an SVN client and Maven 2. Start by checking out Weld core from SVN: svn checkout http://anonsvn.jboss.org/repos/weld/core/trunk/ Once you’ve checked it out, simply run mvn clean install to build. It will seem busy for a while, and eventually you should get a BUILD SUCCESSFUL message – done! Next, we need the Weld servlet module, so check it out from SVN also: svn checkout http://anonsvn.jboss.org/repos/weld/servlet/trunk/ Once you have the source, build it the same way again with mvn clean install. Once it’s built, copy the weld-servlet-xxx.jar file from the build/target directory into the WEB-INF/lib directory of your project. This is the only jar file you need to add to your project for Weld support. With all the required libraries now in your project’s WEB-INF/lib directory, do a refresh in Eclipse (either press F5 or right click on your project and select Refresh) then go into the Java Build Path page (right click on project -> Properties -> Java Build Path) and click on the Libraries tab. Click the ‘Add Jars’ button and browse to your project’s war/WEB-INF/lib directory and select weld-servlet.jar, then click OK. This will allow us to use the CDI annotations in our classes. Hello World Now that we’ve got our project set up and all the required libraries in place, it’s time to write some code. Just to ensure that everything is working ok, we’re going to start with a simple Hello World example. First of all, create the following bean class in your new project: import javax.inject.Named;

Running your app locallyTo take your new application for a test run it’s best to try running it locally before you deploy it to production. Right-click on your project, then click Run As -> Web Application. You should see a few log messages as the servlet container starts up, and then the following message: The server is running athttp://localhost:8888/Once you see this, it means your app is up and running. Open your web browser and go to http://localhost:8888/helloworld.jsf. If everything is in order you should see the following page:

If you see this page, then congratulations! It’s time to deploy your app to the GAE production environment. If you don’t see this page, then go through all the previous steps to make sure you haven’t missed anything. After that, if you still can’t get this page to display then post a comment describing where you’re stuck and we’ll try to help you out.Deploying to Google App Engine Now it’s time to deploy your application. Right click on your project, and select Google -> Deploy To App Engine. You will be prompted for your Google accounts username and password, so enter them here. After entering them the deployment process will take a little while complete, but eventually you’ll get a ‘Deployment completed successfully’ message. To see if your deployment was successful, go to your web browser and open your application page – Google apps are deployed to .appspot.com, where the app-id is your unique application ID.

If all has gone well, then you should see the same Hello, World message that you saw when running your application locally.