Spring vs Java EE Web Dev

Setting Up logentries for OSGi Applications in Apache Karaf

2012-12-29T19:12:00.002-08:00

What You'll Get

-->

How To

Get an account at logentries. For a start, you'll get free forever account for 1 GB of logs per month, which is cool. :-)

We need to patch leappender-1-1.5.jar by adding OSGi manifest headers and attach it as fragment to pax-logging-service. (in CentOS/Amazon Linux, jar requires java-1.7.0-openjdk-devel yum package)

wget

'https://github.com/downloads/logentries/le_java/leappender-1.1.5.jar'

unzip
-d leappender leappender-1.1.5.jar

mkdir
-vp leappender/META-INF


nano
leappender/META-INF/MANIFEST.MF

Replace with:

Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: com.logentries.leappender
Bundle-SymbolicName: com.logentries.leappender
Bundle-Version: 1.1.5
Created-By: 1.7.0_09-icedtea (Oracle Corporation)
Export-Package: com.logentries.log4j;uses:="org.apache.log4j.spi";version="1.1.5"
Import-Package: org.apache.log4j,org.apache.log4j.spi
Fragment-Host: org.ops4j.pax.logging.pax-logging-service

rm -v

leappender-1.1.5

.bar;

jar
-c

vfm

leappender-1.1.5.bar


leappender/META-INF/MANIFEST.MF

C

leappender
.

# Wrap it first
using

bnd
wget -O
bnd.jar
'http://search.maven.org/remotecontent?filepath=biz/aQute/bnd/1.50.0/bnd-1.50.0.jar'
java
-jar bnd.jar wrap leappender-1.1.5.jar

our appender bundle should be present in the system folder and defined in etc/startup.properties.

The system folder has a “Maven repo like” structure. So you have to copy with:


system/groupId/artifactId/version/artifactId-version.jar

In our example, it means:

mkdir -v

p
system/

com/logentries/leappender/1.1.5/cp

-v

leappender-1.1.5.b

ar
system/com/logentries/leappender/1.1.

5/leappender-1.1.5.jar

and in etc/startup.properties, we define the appender bundle just before the pax-logging-service bundle:

...
org/ops4j/pax/logging/pax-logging-api/1.

7.0/pax-logging-api-1.7.0.jar=8com/logentries/leappender/1.1.5/leappender-1.1.5.jar

=8
org/ops4j/pax/logging/pax-logging-service/1.

7.0/pax-logging-service-1.7.0

.jar=8
...

Edit Karaf's etc/org.ops4j.pax.logging.cfg :

log4j.rootLogger = INFO,
out,

le

,
osgi:*
...

# Logentries
appender


log4j.appender.

le

=com.logentries.log4j.LeAppender
log4j.appender.

le.Token=LOGENTRIES_TOKEN


log4j.appender.

le.Debug=true


log4j.appender.

le

.layout=org.apache.log4j.PatternLayout
log4j.appender.

le.layout.ConversionPattern

=%d{ISO8601} | %-5.5p | %-16.16t | %-32.32c{1} | %-32.32C %4L | %X{bundle.id} - %X{bundle.name} - %X{bundle.version} | %m%n

log4j.appender.le.layout.ConversionPattern=

%d{yyyy-MM-dd
HH:mm:ss ZZZ} %-5p: %F:%L  %m

Note: The LOGENTRIES_TOKEN parameter can be found beside the logfile which we created earlier.

I can't get this to work automatically, so on first Karaf launch you'll get ClassNotFoundException, then you'll need to install it:

install
mvn:com.logentries/leappender/1.1.5
bundle-level <id> 8

Now it should work.

~~At first launch you'll get a ClassNotFound exception. Shutdown Karaf and relaunch, it should work.~~ (this was due to the leappender-1.1.5.jar in deploy/ folder, the system one still doesn't work automatically)

Happy logging! :-)

References:

Using Javassist to Create a Karaf/GoGo Shell Command Dynamically

2012-07-15T14:14:00.001-07:00

Karaf OSGi runtime provides an excellent shell console functionality called Felix GoGo that can be extended easily using Blueprint XML :

<command-bundle xmlns="http://karaf.apache.org/xmlns/shell/v1.0.0">
    <command name="process/run">
        <action class="com.soluvas.process.shell.ProcessRunCommand">
            <argument ref="processContainer"/>
            <argument ref="ksession"/>
            <argument ref="dependencyLookup"/>
        </action>
    </command>
    <command name="process/ls">
        <action class="com.soluvas.process.shell.ProcessLsCommand">
            <argument ref="processContainer"/>
        </action>
    </command>
    <command name="process/class">
        <action class="com.soluvas.process.shell.MakeClassCommand">
            <argument ref="blueprintBundleContext"/>
        </action>
    </command>
</command-bundle>

A Karaf Shell Blueprint command element is equivalent to:

<bean id="processLsCommand" scope="prototype"

class="com.soluvas.process.shell.ProcessLsCommand">

</bean>

<service-properties>

</service-properties>

</bean>

</service>

Using the bytecode tooling library Javassist, it's possible (and almost quite practical) to create GoGo commands dynamically at runtime :

ClassPool pool = new ClassPool();
pool.appendClassPath(new LoaderClassPath(getClass().getClassLoader()));

CtClass helloClass = pool.makeClass("cc.HelloCommand");
helloClass.setSuperclass(pool.get("org.apache.karaf.shell.console.OsgiCommandSupport"));
helloClass.addInterface(pool.get("org.apache.karaf.shell.console.CompletableFunction"));
helloClass.addInterface(pool.get("org.apache.felix.service.command.Function"));

ClassFile cf = helloClass.getClassFile();
AnnotationsAttribute attr = new AnnotationsAttribute(cf.getConstPool(), AnnotationsAttribute.visibleTag);
Annotation annotation = new Annotation("org.apache.felix.gogo.commands.Command", cf.getConstPool());
annotation.addMemberValue("scope", new StringMemberValue("test", cf.getConstPool()));
annotation.addMemberValue("name", new StringMemberValue("hello", cf.getConstPool()));
annotation.addMemberValue("description", new StringMemberValue("Hello!", cf.getConstPool()));
attr.addAnnotation(annotation);
cf.addAttribute(attr);

CtMethod doExecuteMethod = CtMethod.make("protected Object doExecute() throws Exception { System.out.println(\"OMG!\"); return \"Hello!\"; }", helloClass);
helloClass.addMethod(doExecuteMethod);

System.out.println("Class: " + helloClass);
Class clazz = helloClass.toClass(getClass().getClassLoader(), getClass().getProtectionDomain());
System.out.println("Created " + clazz);
final Object obj = clazz.newInstance();

BlueprintCommand cmd = new BlueprintCommand() {
    @Override
    public Action createNewAction() {
        return (Action)obj;
    }
};
Hashtable<String, String> props = new Hashtable<String, String>();
props.put(CommandProcessor.COMMAND_SCOPE, "test");
props.put(CommandProcessor.COMMAND_FUNCTION, "hello");
bundleContext.registerService(new String[] { CompletableFunction.class.getName(),
                Function.class.getName() }, cmd, props);

return null;

Just found out @neo4j built-in webadmin graph visualization supports custom labels and icons (!!!) How come nobody told me before about this? ;-) AWESOME!

2012-04-14T03:06:00.001-07:00

Just found out @neo4j built-in webadmin graph visualization supports custom labels and *icons* (!!!) How come nobody told me before about this? ;-) AWESOME!

Workaround for Compilation Errors when Implementing Authenticator in Seam Security and PicketLink IDM

2012-03-29T17:57:00.001-07:00

Due to SEAMSECURITY-66 bug, compiling Authenticator implementation will result in compilation errors, as of Seam Security 3.1.0.Final and PicketLink IDM 1.5.0.Alpha2:

[INFO] Compiling 22 source files to /home/ceefour/git/aksimata-web/target/classes [INFO] ------------------------------------------------------------- [ERROR] COMPILATION ERROR : [INFO] ------------------------------------------------------------- [ERROR] LdapAuthenticator.java:[10,30] cannot find symbol symbol : class BaseAuthenticator location: package org.jboss.seam.security [ERROR] LdapAuthenticator.java:[12,34] package org.picketlink.idm.impl.api does not exist [ERROR] LdapAuthenticator.java:[13,40] package org.picketlink.idm.impl.api.model does not exist [ERROR] LdapAuthenticator.java:[23,39] cannot find symbol symbol: class BaseAuthenticator public class LdapAuthenticator extends BaseAuthenticator { [ERROR] LdapAuthenticator.java:[35,22] cannot find symbol symbol : class PasswordCredential location: class org.soluvas.ldap.LdapAuthenticator [ERROR] LdapAuthenticator.java:[46,4] cannot find symbol symbol : class SimpleUser location: class org.soluvas.ldap.LdapAuthenticator [ERROR] LdapAuthenticator.java:[46,26] cannot find symbol symbol : class SimpleUser location: class org.soluvas.ldap.LdapAuthenticator [ERROR] LdapAuthenticator.java:[48,14] cannot find symbol symbol : variable AuthenticationStatus location: class org.soluvas.ldap.LdapAuthenticator [ERROR] LdapAuthenticator.java:[51,14] cannot find symbol symbol : variable AuthenticationStatus location: class org.soluvas.ldap.LdapAuthenticator [ERROR] LdapAuthenticator.java:[52,4] cannot find symbol symbol : method setUser(<nulltype>) location: class org.soluvas.ldap.LdapAuthenticator [ERROR] LdapAuthenticator.java:[56,13] cannot find symbol symbol : variable AuthenticationStatus location: class org.soluvas.ldap.LdapAuthenticator [ERROR] LdapAuthenticator.java:[57,3] cannot find symbol symbol : method setUser(<nulltype>) location: class org.soluvas.ldap.LdapAuthenticator [ERROR] LdapAuthenticator.java:[30,1] method does not override or implement a method from a supertype

Workaround and the "proper" way to include Seam Security is as follows:

<properties>         <seam.version>3.1.0.Final</seam.version> </properties> <dependencyManagement> <dependencies>         <dependency>                 <groupId>org.jboss.seam</groupId>                 <artifactId>seam-bom</artifactId>                 <version>${seam.version}</version>                 <type>pom</type>                 <scope>import</scope>         </dependency>         <dependency>                 <groupId>org.jboss.seam.security</groupId>                 <artifactId>seam-security</artifactId>                 <version>${seam.version}</version>                 <scope>compile</scope>         </dependency>         <dependency>                 <groupId>org.picketlink.idm</groupId>                 <artifactId>picketlink-idm-core</artifactId>                 <version>1.5.0.Alpha02</version>                 <scope>compile</scope>         </dependency> </dependencies> </dependencyManagement>

In addition to the actual dependency:

<dependencies>
       <dependency>
            <groupId>org.jboss.seam.security</groupId>
            <artifactId>seam-security</artifactId>
        </dependency>
</dependencies>

To learn more about Java Web Development using Java EE 6, I highly recommend The Java EE 6 Tutorial: Basic Concepts (4th Edition) (Java Series) by Eric Jendrock, Ian Evans, Devika Gollapudi and Kim Haase.

How to Deploy Maven Artifacts to WebDAV Repository

2012-03-29T17:52:00.001-07:00

Either the DAV wagon is great or DreamHost's Svn+WebDAV integration is great, or both. POM Configuration is straightforward:

<distributionManagement>
<snapshotRepository>
<id>soluvas.org.snapshots.tmp</id>
<url>dav:http://maven.soluvas.org/snapshots</url>
</snapshotRepository>
</distributionManagement>

It "works" in Eclipse sometimes, but when the artifact has not yet been uploaded (huh?!?!) it fails with:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project soluvas-apacheds: Failed to deploy artifacts: Could not find artifact org.soluvas.apacheds:soluvas-apacheds:jar:1.0.0-20120329.222133-1 in soluvas.org.snapshots.tmp (dav:http://maven.soluvas.org/snapshots) -> [Help 1]

In mvn CLI, it simply fails: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.5:deploy (default-deploy) on project soluvas-apacheds: Failed to deploy artifacts/metadata: No connector available to access repository soluvas.org.snapshots.tmp (dav:http://maven.soluvas.org/snapshots) of type default using the available factories WagonRepositoryConnectorFactory -> [Help 1]

Anyway, to properly do this you need a wagon config, which works well with DreamHost's subversion+webDAV (haven't tried with plain Webdav repository yet, but should work):
<build>
<extensions>
<extension>
<artifactId>wagon-webdav-jackrabbit</artifactId>
<groupId>org.apache.maven.wagon</groupId>
<version>2.2</version>
</extension>
</extensions>
</build>

then you add your credentials in ~/.m2/settings.xml :

<settings xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">

<id>soluvas.org.snapshots.tmp</id>

<username>youruser</username>

<password>yourpass</password>

</server>

</servers>

...

</settings>

Now you can deploy your Maven project by:

mvn source:jar javadoc:jar install deploy

How to Enable Gzip HTTP Compression in JBoss AS 7.1.1

2012-03-29T17:44:00.001-07:00

JBoss AS 7.1.1 has finally returned the powerful Gzip HTTP Compression support (AS7-2991) that was missing since 7.0.0.

Edit standalone/configuration/standalone.xml and add <system-properties> after the </extensions> :

... <extension module="org.jboss.as.weld"/> </extensions> <system-properties> <property name="org.apache.coyote.http11.Http11Protocol.COMPRESSION" value="on"/> </system-properties>

Proof :

$ curl --head --compressed http://localhost:9080/
HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Accept-Ranges: bytes
ETag: W/"2432-1331360042000"
Last-Modified: Sat, 10 Mar 2012 06:14:02 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Content-Encoding: gzip
Vary: Accept-Encoding
Date: Fri, 30 Mar 2012 00:40:36 GMT

If you're running your app on OpenShift, it doesn't hurt to enable this switch now. That way, when OpenShift upgrades to JBoss AS 7.1.1 or later, your app will get HTTP Compression automatically. :-)

Alternative: You can also enable it by adding to the server launch params :

-Dorg.apache.coyote.http11.Http11Protocol.COMPRESSION=on

Enables HTTP compression on JBoss 7.1.1

Optimal Java EE Webapp Logging Configuration for JBoss AS7 Deployment

2012-03-29T07:48:00.001-07:00

I used to configure logging (via SLF4J) in my Java EE web applications like this:

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>commons-logging</groupId>
            <artifactId>commons-logging</artifactId>
            <version>1.1.1</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
            <version>${slf4j.version}</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>jcl-over-slf4j</artifactId>
            <version>${slf4j.version}</version>
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-jdk14</artifactId>
            <version>${slf4j.version}</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

Although in practice this works well, it's not efficient because I'm bundling my own SLF4J libraries with my webapp, and direct them to JDK Logging, which is handled properly by JBoss AS 7.1.

Note that there's nothing wrong with the above configuration, because makes the webapp very portable across Application Servers (even servlet containers like Tomcat).

Thanks to Joshua Davis, I got the perfect logging configuration for JBoss AS7:

<properties>        <slf4j.version>1.6.4</slf4j.version></properties>

<groupId>commons-logging</groupId>

<artifactId>commons-logging</artifactId>

<scope>provided</scope>

</dependency>

<version>${slf4j.version}</version>

<scope>provided</scope>

</dependency>

<version>${slf4j.version}</version>

<scope>provided</scope>

</dependency>

<version>${slf4j.version}</version>

<scope>provided</scope>

</dependency>

</dependencies>

</dependencyManagement>

Dependencies:

</dependency>

</dependency>

</dependency>

Since SLF4J is already defined as a JBoss 'module', then all that we need to do is to reference the module from the WAR file.¹ The simplest way is to get Maven to list the dependency in META-INF/MANIFEST.MF:

<plugin>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-war-plugin</artifactId>

<version>2.2</version>

<configuration>

<archive>

<manifestEntries>

<Dependencies>org.slf4j, org.apache.commons.logging</Dependencies>

</manifestEntries>

</archive>

</configuration>

</plugin>

This will generate a META-INF/MANIFEST.MF file that has this line in it:

Dependencies: org.slf4j, org.apache.commons.logging

This tweak saves space, RAM, and probably increases webapp performance a bit too. :-)

How to Develop an OpenShift Cloud App with Facebook OAuth Support [Tutorial]

2012-03-19T03:34:00.001-07:00

How to Develop a Facebook App with OAuth 2.0 authorization to publish activities to the social network. Technologies:

Java EE 6 standards including CDI (JSR-299 Dependency Injection) and JSF 2.0
Twitter's excellent CSS framework Bootstrap
Easily test and rapidly iterate your app in your local development computer with JBoss AS 7.1.1
Deploy to the cloud in seconds to RedHat OpenShift Express, for free!

What Will You Get?

This app's interface and purpose is actually simple :

Login with Facebook and allow the app. The app requires the publish_stream privilege.
Put a message, click Post and the app will update your Facebook status.

You check out the live app at fbstatus-soluvas.rhcloud.com.

Preparation

Before you start, you'll need to get some basics ready :

Get the latest JBoss Developer Studio 5.0.0.Beta1.
Simply the quickest way to get started. This contains Eclipse IDE, JBoss Tools, JBoss AS, JBoss Forge, OpenShift plug-in and several other handy tools at your command.
If you want, you can install these separately:
- Eclipse IDE, Java EE Developer edition (3.7.2 or later)
- JBoss Tools (get 3.3.0.Beta1 or later)
- JBoss AS 7.1.1 or later
- JBoss Forge 1.0.Final or later
While downloading the things above, signup for RedHat OpenShift Express.
Set up your SSH keys so you're good to go. You can try creating a test app yourself, but we'll create another app for this tutorial. (OpenShift allows multiple applications in one account).
You'll also need to have a Facebook app. Go to Facebook Developers and create an app. Any test app will do. We'll need to generate an access token for your Facebook profile (later on).

Prepare the Project: Some Boilerplate Stuff

Create a new jbossas-7 OpenShift application.
In JBoss Developer Studio / Eclipse IDE, create a new OpenShift application :
File > New > Other... > choose OpenShift Application.
Name it anything you want, in my case it's fbstatus.
Pick the jbossas-7 cartridge.
Other fancy options are not needed for this purpose.
Cleanup the OpenShift scaffold project.
Delete everything in src/main/webapp except WEB-INF.
Also delete src/main/webapp/WEB-INF/faces-config.xml first (JBoss Tools may automatically create it for you).
We delete this so Forge's faces setup (below) runs well.
Add SLF4J Logging dependency.
JDK Logging is okay, but SLF4J is much nicer. We'll configure SLF4J to log using JDK Logger, which is handled properly by JBoss AS.
Using Forge Console, run:
project add-dependency org.slf4j:slf4j-api:1.6.4
project add-dependency org.slf4j:slf4j-jdk14:1.6.4:runtime
Setup JSF and CDI.
Using Forge Console, run:
faces setup
When asked for CDI, enter "Y".
For Faces servlet and mapping, enter "N" because it's not required for Servlet 3.0 and beyond.
Make sure Maven project configuration is up-to-date.
Right click project > Maven > Update Project
Get Icons
Some people think is an "extraneous" step, but I think initial appearance is very important as it sets your mood. ;-)
Get a "normal" size icon (~64px) e.g. from IconFinder, and save it as src/main/webapp/resources/fbstatus/fbstatus_64p.png
Grab or resize the icon to 16x16 (for navbar, buttons, etc.), save it as src/main/webapp/resources/fbstatus/fbstatus_16p.png
Also save the 16x16 version as an ICO file at src/main/webapp/favicon.ico
Find your favorite "Login with Facebook" icon, and save it as src/mian/webapp/resources/fbstatus/facebook-login.png
Grab Twitter's Bootstrap HTML5 Framework
Like the icons above, this is not really "necessary" for the functionality of the apps, but it seems the mood since initially the app will look "acceptable" instead of "plain HTML".
Download Bootstrap dist and extract it as src/main/webapp/resources/bootstrap
Also get the jQuery plugins from Bootstrap sources, put the bootstrap-*.js plugins from js/ folder into src/main/webapp/resources/bootstrap/js
You also need jQuery library litself and put this file as src/main/webapp/resources/jquery.js
Create a JSF template in src/main/webapp/WEB-INF/templates/basic.xhtml :
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml"
    xmlns:ui="http://java.sun.com/jsf/facelets"
    xmlns:h="http://java.sun.com/jsf/html"
    xmlns:f="http://java.sun.com/jsf/core">
<f:view>
<h:head>
    <meta charset="utf-8" />
    <title><ui:insert name="pageTitle">Post status to Facebook</ui:insert> | FBStatus</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta name="description" content="Post status to Facebook." />
    <meta name="author" content="FBStatus" />
    
    
    <h:outputStylesheet name="bootstrap/css/bootstrap.css"/>
    <style type="text/css">
body {
    padding-top: 60px;
    padding-bottom: 40px;
}
.sidebar-nav {
    padding: 9px 0;
}
</style>
    <h:outputStylesheet name="bootstrap/css/bootstrap-responsive.css"/>
    
    
    
    <link rel="shortcut icon" href="#{request.contextPath}/favicon.ico" />
    
</h:head>
<h:body>
    <div class="navbar navbar-fixed-top">
        <div class="navbar-inner">
            <div class="container">
                <a class="btn btn-navbar" data-toggle="collapse"
                    data-target=".nav-collapse"> <span class="icon-bar"></span> <span
                    class="icon-bar"></span> <span class="icon-bar"></span>
                </a> FBStatus
                <div class="nav-collapse">
                    <ul class="nav">
                        <li>Home</li>
                        <li>Post Status</li>
                        <li>About</li>
                        <li>Contact</li>
                    </ul>
                    <p class="navbar-text pull-right">
                        Login
                    </p>
                </div>
                
            </div>
        </div>
    </div>
    <div class="container">
                <div class="row">
            <div class="span12">
                <h:messages/>
            </div>
        </div>
            <ui:insert name="content"/>
        <hr />
        <footer>
        <p>© Hendy Irawan 2012</p>
        </footer>
    </div>
    
    
    
    <h:outputScript name="jquery.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-transition.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-alert.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-modal.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-dropdown.js"/>
        <h:outputScript library="bootstrap" name="js/bootstrap-scrollspy.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-tab.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-tooltip.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-popover.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-button.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-collapse.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-carousel.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-typeahead.js"/>
</h:body>
</f:view>
</html>
Create a JSF page named src/main/webapp/front.xhtml :
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:ui="http://java.sun.com/jsf/facelets"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:h="http://java.sun.com/jsf/html">
<ui:composition template="/WEB-INF/templates/basic.xhtml">
<ui:define name="pageTitle">Post status to Facebook</ui:define>
<ui:define name="content">
    <p>Hello</p>
</ui:define>
</ui:composition>
</html>
Launch the web app using JBoss AS server, you should be able to access the front page using http://localhost:8080/fbstatus/faces/front.xhtml
You can also deploy to OpenShift by Git committing the entire project and Git push it to OpenShift. It should be accessible at http://yourapp-yourdomain.rhcloud.com/faces/front.xhtml
Add PrettyFaces
For more SEO-friendly URLs PrettyFaces is a must. Use Forge Console to run:
project add-dependency com.ocpsoft:prettyfaces-jsf2:3.3.3
Note: For automatic PrettyFaces configuration, Servlet version in web.xml must be at least 3.0.
Enable PrettyFaces development mode
This can be turned off in production setting but for now, addd in web.xml as follows :
<context-param>
<param-name>com.ocpsoft.pretty.DEVELOPMENT</param-name>
<param-value>true</param-value>
</context-param>
This will allow PrettyFaces mapping to be changed anytime without reloading the webapp.
Create PrettyFaces mapping
Create src/main/webapp/WEB-INF/pretty-config.xml :
<pretty-config xmlns="http://ocpsoft.com/prettyfaces/3.3.3"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://ocpsoft.com/prettyfaces/3.3.3
                        http://ocpsoft.com/xml/ns/prettyfaces/ocpsoft-pretty-faces-3.3.3.xsd">
    <url-mapping id="home">
        <pattern value="/" />
        <view-id value="/faces/front.xhtml" />
    </url-mapping>
</pretty-config>
The above maps the context root path to /faces/front.xhtml.
Deploy the webapp in JBoss AS or OpenShift and you should be able to access the front page at webapp root, e.g. in JBoss would be: http://localhost:8080/fbstatus/

Note that these steps that we've done above are all simply boilerplate.
You can save the project at this point and put it somewhere or on Git to get started with a new OpenShift-JSF-Bootstrap project rapidly.

A Cloud-Ready Facebook App in Java EE in 5 Minutes*

Add RestFB
Now let's get to business, I will use RestFB Facebook API library for Java. Using JBoss Forge Console :
project add-dependency com.restfb:restfb:1.6.9
There are other alternative libraries for accessing Facebook:
- Spring Social. It's easy to use and works well. However it drags quite some dependencies (especially the whole Spring Framework), which makes sense, but RestFB serves the purpose of this tutorial quite well.
- Seam Social. A CDI oriented Facebook client library.
- facebook-java-api. Actually I tried it before RestFB, but it throws an error regarding invalid session key. I'm using access tokens not session IDs so either it's using an outdated Facebook API version or I didn't read the manual correctly.
At this point I should have added Seam Faces and Seam International too, to make working with JSF and FacesMessages more convenient. Too bad, Seam artifacts aren't available yet in OpenShift Maven repository. So, plain JSF API for now.
But in case you're curious how to add Seam Faces and Seam International, here's the needed Maven POM dependencies :
<properties>
    <seam.version>3.1.0.Final</seam.version>
</properties>
   <dependencyManagement>
      <dependencies>
         <dependency>
            <groupId>org.jboss.seam</groupId>
            <artifactId>seam-bom</artifactId>
            <version>${seam.version}</version>
            <type>pom</type>
            <scope>import</scope>
         </dependency>
      </dependencies>
   </dependencyManagement>
...
        <dependency>
            <groupId>org.jboss.seam.international</groupId>
            <artifactId>seam-international</artifactId>
        </dependency>
        <dependency>
            <groupId>joda-time</groupId>
            <artifactId>joda-time</artifactId>
            <version>1.6.2</version>
        </dependency>
        <dependency>
            <groupId>org.jboss.seam.faces</groupId>
            <artifactId>seam-faces</artifactId>
        </dependency>
I'd love to use Seam Security as well, but due to the similar reason as above, well... let's stick to the raw basics. :-D
Add Apache Commons HttpClient
project add-dependency org.apache.httpcomponents:httpclient:4.1.3
We need it because we'll be creating HTTP requests soon.
Tip: You may also want to add Apache Commons IO because it's very useful in many situations: (but it's not required in this tutorial)
project add-dependency commons-io:commons-io:2.1
Create FacebookAuthenticator application-scoped bean
This class forms the bulk of the Facebook authentication logic, and here I implement the entire logic using HTTP operations. For some reason, RestFB does not provide a utility to get an access token (or probably I didn't read the docs well). You can also use an OAuth library. However, this shows actually how simple OAuth 2.0 is in practice.
Put in src/main/java/org/soluvas/fbstatus/FacebookAuthenticator.java
package org.soluvas.fbstatus;
import java.io.FileNotFoundException;
import java.io.FileReader;
import java.io.IOException;
import java.io.InputStream;
import java.net.URI;
import java.util.List;
import java.util.Properties;
import javax.annotation.PostConstruct;
import javax.enterprise.context.ApplicationScoped;
import javax.faces.context.ExternalContext;
import javax.faces.context.FacesContext;
import javax.inject.Named;
import javax.ws.rs.core.UriBuilder;
import org.apache.commons.io.IOUtils;
import org.apache.http.HttpResponse;
import org.apache.http.NameValuePair;
import org.apache.http.client.ClientProtocolException;
import org.apache.http.client.methods.HttpGet;
import org.apache.http.client.utils.URLEncodedUtils;
import org.apache.http.impl.client.DefaultHttpClient;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
/**
* @author ceefour
* Handles Facebook OAuth authentication.
*/
@Named @ApplicationScoped
public class FacebookAuthenticator {
    private transient Logger log = LoggerFactory.getLogger(FacebookAuthenticator.class);
    private String appId = "";
    private String appSecret = "";
    private URI redirectUri;
        @PostConstruct public void init() throws IOException {
        // Load Facebook App credentials from ${OPENSHIFT_DATA_DIR}/fbstatus.properties if exists,
        // otherwise load from WEB-INF/fbstatus.properties
        String dataDir = System.getenv("OPENSHIFT_DATA_DIR");
        Properties props = new Properties();
        if (dataDir != null) {
            String propsFile = dataDir + "/fbstatus.properties";
            log.info("Loading credentials from file: {}", propsFile);
            FileReader fileReader = new FileReader(propsFile);
            props.load(fileReader);
        } else {
            log.info("Loading credentials from resource: {}", "/WEB-INF/fbstatus.properties");
            InputStream stream = FacesContext.getCurrentInstance().getExternalContext().getResourceAsStream("/WEB-INF/fbstatus.properties");
            if (stream == null)
                throw new FileNotFoundException("Either ${OPENSHIFT_DATA_DIR}/fbstatus.properties or /WEB-INF/fbstatus.properties must exist.");
            props.load(stream);
        }
        appId = props.getProperty("facebook.app.id");
        appSecret = props.getProperty("facebook.app.secret");
        log.info("App ID: {}", appId);
                // Generate redirect URI
        final ExternalContext external = FacesContext.getCurrentInstance()
                .getExternalContext();
        redirectUri = UriBuilder.fromPath(external.encodeActionURL("/faces/fb_auth.xhtml"))
                .scheme(external.getRequestScheme())
                .host(external.getRequestServerName())
                .port(external.getRequestServerPort()).build();
    }
        public URI getRedirectUri() {
        return redirectUri;
    }
    public URI getAuthorizeUri() {
        return UriBuilder.fromUri("https://graph.facebook.com/oauth/authorize").queryParam("client_id", appId)
            .queryParam("redirect_uri", getRedirectUri())
            .queryParam("scope", "publish_stream").build();
    }
        public URI getAccessTokenUri(String authCode) {
        return UriBuilder
                .fromUri("https://graph.facebook.com/oauth/access_token")
                .queryParam("client_id", appId)
                .queryParam("redirect_uri", getRedirectUri())
                .queryParam("client_secret", appSecret)
                .queryParam("code", authCode).build();
    }
    /**
    * Sets the authCode received from Facebook and exchanges it with the access token.
    * @param authCode
    * @throws IOException
    * @throws ClientProtocolException
    */
    public String fetchAccessToken(String authCode) throws ClientProtocolException, IOException {
       log.info("Retrieving access token using authCode {}", authCode);
       URI accessTokenUri = getAccessTokenUri(authCode);
       DefaultHttpClient client = new DefaultHttpClient();
       HttpGet accessTokenReq = new HttpGet(accessTokenUri);
       HttpResponse response = client.execute(accessTokenReq);
       if (response.getStatusLine().getStatusCode() != 200)
           throw new IOException(String.format("GET %s throws HTTP Error %d: %s",
                   accessTokenUri, response.getStatusLine().getStatusCode(), response.getStatusLine().getReasonPhrase()));
       Scanner scanner = new Scanner(response.getEntity().getContent());
       ArrayList<NameValuePair> data = new ArrayList<NameValuePair>();
       URLEncodedUtils.parse(data, scanner, "UTF-8");
       // Probably due to non-existing Content-Encoding, this one is not working:
//       List<NameValuePair> data = URLEncodedUtils.parse(response.getEntity());
       // see: https://issues.apache.org/jira/browse/HTTPCLIENT-1175
       String accessToken = data.get(0).getValue();
       //log.debug("Access token = {}", fbAccessToken); // security risk?
       return accessToken;
    }
    }
Create the UserSession session-bean
This bean handles the OAuth code that provided by Facebook, asks the FacebookAuthenticator to exchange it with an access token, then stores the access token in the session.
Put in src/main/java/org/soluvas/fbstatus/UserSession.java :
package org.soluvas.fbstatus;
import java.io.IOException;
import java.io.Serializable;
import javax.enterprise.context.SessionScoped;
import javax.faces.context.ExternalContext;
import javax.faces.context.FacesContext;
import javax.inject.Inject;
import javax.inject.Named;
import org.apache.http.client.ClientProtocolException;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
@Named @SessionScoped
public class UserSession implements Serializable {
    private static final long serialVersionUID = 1L;
    private transient Logger log = LoggerFactory.getLogger(UserSession.class);
    @Inject FacebookAuthenticator facebookAuth;
    private String fbAccessToken;
        public String getFacebookAuthCode() {
        return null;
    }
        /**
    * Sets the authCode received from Facebook and exchanges it with the access token.
    * @param authCode
    * @throws IOException
    * @throws ClientProtocolException
    */
    public void setFacebookAuthCode(String authCode) throws ClientProtocolException, IOException {
        String accessToken = facebookAuth.fetchAccessToken(authCode);
        setFbAccessToken(accessToken);
                log.info("Access token received, redirecting to Post Status page");
        ExternalContext external = FacesContext.getCurrentInstance().getExternalContext();
        external.redirect(external.encodeActionURL("/faces/post.xhtml"));
    }
    public String getFbAccessToken() {
        return fbAccessToken;
    }
    public void setFbAccessToken(String fbAccessToken) {
        this.fbAccessToken = fbAccessToken;
    }
    }
Create the "login button"
The login "button" is actually a normal link to a Facebook URL with special parameters.
Edit the basic.xhtml template as follows:
<p class="navbar-text pull-right">

</p>
Also edit the contents of the ui:define name="content" in front.xhtml page as follows:
<div class="row">
    <div class="span12">
        <div class="hero-unit">
            <h:graphicImage library="fbstatus" name="fbstatus_64p.png"
                style="float: right;" alt="FBStatus" />
            <h1>FBStatus</h1>
            <p>Post status to Facebook...</p>
            <p>Easy!</p>
            <p>
                Login with Facebook »
            </p>
        </div>
    </div>
    </div>
The login button/link uses the URI given by "FacebookAuthenticator.authorizeUri" bean, which is implemented like this:
public URI getAuthorizeUri() {
    return UriBuilder.fromUri("https://graph.facebook.com/oauth/authorize").queryParam("client_id", appId)
        .queryParam("redirect_uri", getRedirectUri())
        .queryParam("scope", "publish_stream").build();
}
As you can see, the Facebook authorization URL has 3 query parameters:
- client_id: Your Facebook App ID
- redirect_uri: the destination URL after authorization complete
- scope: Requested permissions, hardcoded to "publish_stream" in this case. You can see the complete list of permissions in Facebook Graph API documentation.
Create the Facebook Authentication Receiver
We need a page that handles the OAuth verifier code given by Facebook.
Put in src/main/webapp/fb_auth.xhtml :
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:ui="http://java.sun.com/jsf/facelets"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:h="http://java.sun.com/jsf/html">
<f:metadata>
    <f:viewParam name="code" value="#{userSession.facebookAuthCode}"/>
</f:metadata>
<h:head>
    <title>Facebook Authentication</title>
</h:head>
<h:body>
</h:body>
</html>
Also add the mapping in pretty-config.xml :
<url-mapping id="fb_auth">
    <pattern value="/fb_auth" />
    <view-id value="/faces/fb_auth.xhtml" />
</url-mapping>
The page code is very simple because it simply calls UserSession.setFacebookAuthCode(), which in turn delegates the real work to FacebookAuthenticator bean.
Create the Post Status form
UserSession redirects to /faces/post.xhtml, however we haven't created this page.
Put this in /src/main/webapp/post.xhtml :
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:ui="http://java.sun.com/jsf/facelets"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:h="http://java.sun.com/jsf/html">
<ui:composition template="/WEB-INF/templates/basic.xhtml">
<ui:define name="pageTitle">Post status to Facebook</ui:define>
<ui:define name="content">
    <div class="row">
        <div class="span12">
                    <h:form>
                <h2>Post Status</h2>
                <p><h:inputTextarea value="#{postView.message}" style="width: 30em;" rows="4"/></p>
                <p><h:commandLink action="#{postView.manualPost}" value="Post" styleClass="btn"/></p>
                <h:panelGroup rendered="#{not empty postView.lastStatusId}">
                    <p>Last status ID: #{postView.lastStatusId}</p>
                </h:panelGroup>
                                <p><small>Access token: #{userSession.fbAccessToken}</small></p>
            </h:form>
        </div> 
    </div> 
</ui:define>
</ui:composition>
</html>
The JSF page above simply presents text boxes to input the desired message, and a button to call the PostView.manualPost() method.
Also displayed is the link to the last status so you can see it in Facebook website.
Create the bean which posts status to Facebook using RestFB
This is the backing bean that powers the post.xhtml form above.
Put in src/main/java/org/soluvas/fbstatus/PostView.java :
package org.soluvas.fbstatus;
import java.io.Serializable;
import java.util.regex.Matcher;
import java.util.regex.Pattern;
import javax.enterprise.context.SessionScoped;
import javax.faces.application.FacesMessage;
import javax.faces.context.FacesContext;
import javax.inject.Inject;
import javax.inject.Named;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.restfb.DefaultFacebookClient;
import com.restfb.Parameter;
import com.restfb.types.FacebookType;
@SessionScoped @Named
public class PostView implements Serializable {
    static final long serialVersionUID = 1L;
    private transient Logger log = LoggerFactory.getLogger(PostView.class);
//    @Inject Messages messages;
    @Inject UserSession userSession;
    String message;
    String lastStatusId;
    String lastStatusUrl;
        public void manualPost() {
        FacesContext faces = FacesContext.getCurrentInstance();
        DefaultFacebookClient client = new DefaultFacebookClient(userSession.getFbAccessToken());
        FacebookType response = client.publish("me/feed", FacebookType.class, Parameter.with("message", message));
        lastStatusId = response.getId();
        log.info("Got Post ID: {}", lastStatusId);
        Matcher matcher = Pattern.compile("(\\d+)_(\\d+)").matcher(lastStatusId);
        if (matcher.matches()) {
            String userId = matcher.group(1);
            String postId = matcher.group(2);
            lastStatusUrl = "http://www.facebook.com/" + userId + "/posts/" + postId;
            log.info("Post URL is {}", lastStatusUrl);
            faces.addMessage(null, new FacesMessage(
                    "Status posted to Facebook with ID: " + lastStatusId, ""));
//            messages.info("Status posted to Facebook with ID: {0}", lastStatusId);
            message = "";
        } else {
            log.error("Cannot parse Post ID: {}", lastStatusId);
            faces.addMessage(null, new FacesMessage(faces.getMaximumSeverity(),
                    "Cannot parse Post ID: " + lastStatusId, ""));
        }
    }
        public String getMessage() {
        return message;
    }
    public void setMessage(String message) {
        this.message = message;
    }
    public String getLastStatusUrl() {
        return lastStatusUrl;
    }
    public void setLastStatusUrl(String lastStatusUrl) {
        this.lastStatusUrl = lastStatusUrl;
    }
    public String getLastStatusId() {
        return lastStatusId;
    }
    public void setLastStatusId(String lastStatusId) {
        this.lastStatusId = lastStatusId;
    }
    }
This is the core meat of this tutorial. As you can see the real code is not very complicated. :-) In Java EE 6, you use managed beans and annotate it with @Named to make it accessible from JSF page (below). By annotating with @SessionScoped the bean's property values are preserved within the same browser session. Different visitors or different browsers will have its own instance of the session-scoped bean.
If you want to perform unit testing, you need to supply the (probably mock) UserSession object, set message property then call manualPost().

And that's it!

As you can see only a few steps are unique to this web application. Which highlights the necessity to create some form of project template or prototype where you can easily construct the basic JSF webapp necessities quickly.

Deploying to OpenShift

Deploying the app is easy, simply do a "git push".

The app requires a one-time setup. The Facebook App credentials are not stored in the application, but must be configured separately (typically by the sysadmin aka DevOps guy).

You need to create a file in your OpenShift data directory (environment value OPENSHIFT_DATA_DIR) named fbstatus.properties .

There are several ways to create this file, but here I'll show you how to do it with SSH.

Use the rhc app show command to find out the Git / SSH URL:

$ rhc app show -a fbstatus

Application Info
================
fbstatus
    Framework: jbossas-7
     Creation: 2012-03-15T00:22:35-04:00
         UUID: 7652c51ac0b84512b5edef59f00***
      Git URL: ssh://7652c51ac0b84512b5edef59f00***@fbstatus-soluvas.rhcloud.com/~/git/fbstatus.git/
   Public URL: http://fbstatus-soluvas.rhcloud.com/

Embedded:
mongodb-2.0 - Connection URL: mongodb://127.13.155.1:27017/

Now you should be able to connect via SSH by using the depicted username and hostname:

ssh 7652c51ac0b84512b5edef59f00***@fbstatus-soluvas.rhcloud.com

Once logged in, go to the fbstatus/data directory and create the fbstatus.properties file using cat :

cd fbstatus/data
cat > fbstatus.properties
facebook.app.id=YOUR_APP_ID
facebook.app.secret=YOUR_APP_SECRET
( press Ctrl+D )

Now it should look like this:

[fbstatus-soluvas.rhcloud.com data]\> ls -l
total 4
-rw-r--r--. 1 86 Mar 19 04:32 fbstatus.properties

Reload your app (using rhc app reload) and the app should work fine.

How to Use the App

This app's interface and purpose is actually simple. After deploying the app:

Click Login with Facebook button. The user will be shown a series of Facebook authorization screens before being redirected back to the site:
Put a message, click Post and the app will update your Facebook status.

You check out the live app at fbstatus-soluvas.rhcloud.com.

This is an example of the status generated by the app :

You can see the status update at http://www.facebook.com/ceefour/posts/10150732341781672 . Oh and by the way, you're welcome to add me on Facebook :-)

To make it even more convenient for you, the entire project for this tutorial is available as open source soluvas/fbstatus project at GitHub. It's directly deployable to OpenShift too!

How to Test the App Locally using JBoss AS

Testing the app locally very similar with OpenShift, but you need to use JBoss AS.

To provide the fbstatus.properties configuration file, you can either:

Set the OPENSHIFT_DATA_DIR environment yourself. This way mirrors how OpenShift environment works. Or:
Put the fbstatus.properties file in src/main/webapp/WEB-INF folder. This is an additional logic I provided to make it more in-line with "traditional" Java EE apps.

For application settings in Facebook developer site, you need to put "http://localhost/" as your website URL. So that Facebook will allow your app to redirect to "localhost" address (your development machine).

* (to be honest, no, I didn't write this article in 5 minutes. but you could ;-)

How to Create a Facebook App using Java EE 6 and Easily Deploy to RedHat OpenShift Cloud [Tutorial]

2012-03-16T10:04:00.001-07:00

UPDATE: Please see the updated Facebook App Tutorial with OAuth Support.

________________________________________________________

How to Develop a Facebook App using:

Java EE 6 standards including CDI (JSR-299 Dependency Injection) and JSF 2.0
Twitter's excellent CSS framework Bootstrap
Easily test and rapidly iterate your app in your local development computer with JBoss AS 7.1.1
Deploy to the cloud in seconds to RedHat OpenShift Express, for free!

What Will You Get?

This app's interface and purpose is actually simple :

Put your Facebook access token in it. You can use the Facebook Graph Explorer and your own app to generate an access token. You need to allow the publish_stream privilege.
Put a message, click Post and the app will update your Facebook status.

You check out the live app at fbstatus-soluvas.rhcloud.com.
Preparation
Before you start, you'll need to get some basics ready :

Get the latest JBoss Developer Studio 5.0.0.Beta1.
Simply the quickest way to get started. This contains Eclipse IDE, JBoss Tools, JBoss AS, JBoss Forge, OpenShift plug-in and several other handy tools at your command.
If you want, you can install these separately:
- Eclipse IDE, Java EE Developer edition (3.7.2 or later)
- JBoss Tools (get 3.3.0.Beta1 or later)
- JBoss AS 7.1.1 or later
- JBoss Forge 1.0.Final or later
While downloading the things above, signup for RedHat OpenShift Express.
Set up your SSH keys so you're good to go. You can try creating a test app yourself, but we'll create another app for this tutorial. (OpenShift allows multiple applications in one account).
You'll also need to have a Facebook app. Go to Facebook Developers and create an app. Any test app will do. We'll need to generate an access token for your Facebook profile (later on).

A Cloud-Ready Facebook App in Java EE in 5 Minutes*

Create a new jbossas-7 OpenShift application.
In JBoss Developer Studio / Eclipse IDE, create a new OpenShift application :
File > New > Other... > choose OpenShift Application.
Name it anything you want, in my case it's fbstatus.
Pick the jbossas-7 cartridge.
Other fancy options are not needed for this purpose.
Cleanup the OpenShift scaffold project.
Delete everything in src/main/webapp except WEB-INF.
Also delete src/main/webapp/WEB-INF/faces-config.xml first (JBoss Tools may automatically create it for you).
We delete this so Forge's faces setup (below) runs well.
Add SLF4J Logging dependency.
JDK Logging is okay, but SLF4J is much nicer. We'll configure SLF4J to log using JDK Logger, which is handled properly by JBoss AS.
Using Forge Console, run:project add-dependency org.slf4j:slf4j-api:1.6.4
project add-dependency org.slf4j:slf4j-jdk14:1.6.4:runtime
Setup JSF and CDI.
Using Forge Console, run:faces setup
When asked for CDI, enter "Y".
For Faces servlet and mapping, enter "N" because it's not required for Servlet 3.0 and beyond.
Make sure Maven project configuration is up-to-date.
Right click project > Maven > Update Project
Get Icons
Some people think is an "extraneous" step, but I think initial appearance is very important as it sets your mood. ;-)
Get a "normal" size icon (~64px) e.g. from IconFinder, and save it as src/main/webapp/resources/fbstatus/fbstatus_64p.png
Grab or resize the icon to 16x16 (for navbar, buttons, etc.), save it in src/main/webapp/resources/fbstatus/fbstatus_16p.png
Also save the 16x16 version as an ICO file at src/main/webapp/favicon.ico
Grab Twitter's Bootstrap HTML5 Framework
Like the icons above, this is not really "necessary" for the functionality of the apps, but it seems the mood since initially the app will look "acceptable" instead of "plain HTML".
Download Bootstrap dist and extract it as src/main/webapp/resources/bootstrap
Also get the jQuery plugins from Bootstrap sources, put the bootstrap-*.js plugins from js/ folder into src/main/webapp/resources/bootstrap/js
You also need jQuery library litself and put this file as src/main/webapp/resources/jquery.js
Create a JSF template in src/main/webapp/templates/basic.xhtml :<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml"
    xmlns:ui="http://java.sun.com/jsf/facelets"
    xmlns:h="http://java.sun.com/jsf/html"
    xmlns:f="http://java.sun.com/jsf/core">
<f:view>
<h:head>
    <meta charset="utf-8" />
    <title><ui:insert name="pageTitle">Post status to Facebook</ui:insert> | FBStatus</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta name="description" content="Post status to Facebook." />
    <meta name="author" content="FBStatus" />
    
    
    <h:outputStylesheet name="bootstrap/css/bootstrap.css"/>
    <style type="text/css">
body {
    padding-top: 60px;
    padding-bottom: 40px;
}
.sidebar-nav {
    padding: 9px 0;
}
</style>
    <h:outputStylesheet name="bootstrap/css/bootstrap-responsive.css"/>
    
    
    
    <link rel="shortcut icon" href="#{request.contextPath}/favicon.ico" />
    
</h:head>
<h:body>
    <div class="navbar navbar-fixed-top">
        <div class="navbar-inner">
            <div class="container">
                <a class="btn btn-navbar" data-toggle="collapse"
                    data-target=".nav-collapse"> <span class="icon-bar"></span> <span
                    class="icon-bar"></span> <span class="icon-bar"></span>
                </a> FBStatus
                <div class="nav-collapse">
                    <ul class="nav">
                        <li>Home</li>
                        <li>Post Status</li>
                        <li>About</li>
                        <li>Contact</li>
                    </ul>
                    <p class="navbar-text pull-right">
                        Login
                    </p>
                </div>
                
            </div>
        </div>
    </div>
    <div class="container">
                <div class="row">
            <div class="span12">
                <h:messages/>
            </div>
        </div>
            <ui:insert name="content"/>
        <hr />
        <footer>
        <p>© Hendy Irawan 2012</p>
        </footer>
    </div>
    
    
    
    <h:outputScript name="jquery.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-transition.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-alert.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-modal.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-dropdown.js"/>
        <h:outputScript library="bootstrap" name="js/bootstrap-scrollspy.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-tab.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-tooltip.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-popover.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-button.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-collapse.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-carousel.js"/>
    <h:outputScript library="bootstrap" name="js/bootstrap-typeahead.js"/>
</h:body>
</f:view>
</html>
Create a JSF page named src/main/webapp/front.xhtml :<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:ui="http://java.sun.com/jsf/facelets"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:h="http://java.sun.com/jsf/html">
<h:head>
    <title>FBStatus</title>
</h:head>
<h:body>
    <p>Hello</p>
</h:body>
</html>
Launch the web app using JBoss AS server, you should be able to access the front page using http://localhost:8080/fbstatus/faces/front.xhtml
You can also deploy to OpenShift by Git committing the entire project and Git push it to OpenShift. It should be accessible at http://yourapp-yourdomain.rhcloud.com/faces/front.xhtml
Add PrettyFaces
For more SEO-friendly URLs PrettyFaces is a must. Use Forge Console to run:project add-dependency com.ocpsoft:prettyfaces-jsf2:3.3.3
Note: For automatic PrettyFaces configuration, Servlet version in web.xml must be at least 3.0.
Enable PrettyFaces development mode
This can be turned off in production setting but for now, addd in web.xml as follows :<context-param>
<param-name>com.ocpsoft.pretty.DEVELOPMENT</param-name>
<param-value>true</param-value>
</context-param>
This will allow PrettyFaces mapping to be changed anytime without reloading the webapp.
Create PrettyFaces mapping
Create src/main/webapp/WEB-INF/pretty-config.xml :<pretty-config xmlns="http://ocpsoft.com/prettyfaces/3.3.3"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://ocpsoft.com/prettyfaces/3.3.3
                        http://ocpsoft.com/xml/ns/prettyfaces/ocpsoft-pretty-faces-3.3.3.xsd">
    <url-mapping id="home">
        <pattern value="/" />
        <view-id value="/faces/front.xhtml" />
    </url-mapping>
</pretty-config>
The above maps the context root path to /faces/front.xhtml.
Deploy the webapp in JBoss AS or OpenShift and you should be able to access the front page at webapp root, e.g. in JBoss would be: http://localhost:8080/fbstatus/
Note that these steps that we've done above are all simply boilerplate.
You can save the project at this point and put it somewhere or on Git to get started with a new OpenShift-JSF-Bootstrap project rapidly.
Add RestFB
Now let's get to business, I will use RestFB Facebook API library for Java. Using JBoss Forge Console :project add-dependency com.restfb:restfb:1.6.9
There are other alternative libraries for accessing Facebook:
- Spring Social. It's easy to use and works well. However it drags quite some dependencies (especially the whole Spring Framework), which makes sense, but RestFB serves the purpose of this tutorial quite well.
- Seam Social. A CDI oriented Facebook client library.
- facebook-java-api. Actually I tried it before RestFB, but it throws an error regarding invalid session key. I'm using access tokens not session IDs so either it's using an outdated Facebook API version or I didn't read the manual correctly.
At this point I should have added Seam Faces and Seam International too, to make working with JSF and FacesMessages more convenient. Too bad, Seam artifacts aren't available yet in OpenShift Maven repository. So, plain JSF API for now.
But in case you're curious how to add Seam Faces and Seam International, here's the needed Maven POM dependencies :
<properties>
    <seam.version>3.1.0.Final</seam.version>
</properties>
   <dependencyManagement>
      <dependencies>
         <dependency>
            <groupId>org.jboss.seam</groupId>
            <artifactId>seam-bom</artifactId>
            <version>${seam.version}</version>
            <type>pom</type>
            <scope>import</scope>
         </dependency>
      </dependencies>
   </dependencyManagement>
...
        <dependency>
            <groupId>org.jboss.seam.international</groupId>
            <artifactId>seam-international</artifactId>
        </dependency>
        <dependency>
            <groupId>joda-time</groupId>
            <artifactId>joda-time</artifactId>
            <version>1.6.2</version>
        </dependency>
        <dependency>
            <groupId>org.jboss.seam.faces</groupId>
            <artifactId>seam-faces</artifactId>
        </dependency>
Create the bean src/main/java/org/soluvas/fbstatus/PostView.java :Most of the things below, like always, is Java verbose cruft. (How I wish Scala would prevail over Java the language.) Anyway, here's the code:
package org.soluvas.fbstatus;
import java.io.Serializable;
import java.util.regex.Matcher;
import java.util.regex.Pattern;
import javax.enterprise.context.SessionScoped;
import javax.faces.application.FacesMessage;
import javax.faces.application.FacesMessage.Severity;
import javax.faces.context.FacesContext;
import javax.inject.Named;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import com.restfb.DefaultFacebookClient;
import com.restfb.Parameter;
import com.restfb.types.FacebookType;
@SessionScoped @Named
public class PostView implements Serializable {
    static final long serialVersionUID = 1L;
    private transient Logger log = LoggerFactory.getLogger(PostView.class);
//    @Inject Messages messages;
    String accessToken;
    String message;
    String lastStatusId;
    String lastStatusUrl;
        public void manualPost() {
        FacesContext faces = FacesContext.getCurrentInstance();
        DefaultFacebookClient client = new DefaultFacebookClient(accessToken);
        FacebookType response = client.publish("me/feed", FacebookType.class, Parameter.with("message", message));
        lastStatusId = response.getId();
        log.info("Got Post ID: {}", lastStatusId);
        Matcher matcher = Pattern.compile("(\\d+)_(\\d+)").matcher(lastStatusId);
        if (matcher.matches()) {
            String userId = matcher.group(1);
            String postId = matcher.group(2);
            lastStatusUrl = "http://www.facebook.com/" + userId + "/posts/" + postId;
            log.info("Post URL is {}", lastStatusUrl);
            faces.addMessage(null, new FacesMessage(
                    "Status posted to Facebook with ID: " + lastStatusId, ""));
//            messages.info("Status posted to Facebook with ID: {0}", lastStatusId);
            message = "";
        } else {
            log.error("Cannot parse Post ID: {}", lastStatusId);
            faces.addMessage(null, new FacesMessage(faces.getMaximumSeverity(),
                    "Cannot parse Post ID: " + lastStatusId, ""));
        }
    }
        public String getAccessToken() {
        return accessToken;
    }
    public void setAccessToken(String accessToken) {
        this.accessToken = accessToken;
    }
    public String getMessage() {
        return message;
    }
    public void setMessage(String message) {
        this.message = message;
    }
    public String getLastStatusUrl() {
        return lastStatusUrl;
    }
    public void setLastStatusUrl(String lastStatusUrl) {
        this.lastStatusUrl = lastStatusUrl;
    }
    public String getLastStatusId() {
        return lastStatusId;
    }
    public void setLastStatusId(String lastStatusId) {
        this.lastStatusId = lastStatusId;
    }
    }
This is the core meat of this tutorial. As you can see the real code is not very complicated. :-) In Java EE 6, you use managed beans and annotate it with @Named to make it accessible from JSF page (below). By annotating with @SessionScoped the bean's property values are preserved within the same browser session. Different visitors or different browsers will have its own instance of the session-scoped bean.
By setting accessToken and message properties then calling manualPost(), you should be able to perform some unit testing on the above code if you want.
Create JSF page for Post Status form
This page will display the form and call the postView.manualPost() method above.
Put in src/main/webapp/post.xhtml :<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xmlns:ui="http://java.sun.com/jsf/facelets"
      xmlns:f="http://java.sun.com/jsf/core"
      xmlns:h="http://java.sun.com/jsf/html">
<ui:composition template="/templates/basic.xhtml">
<ui:define name="pageTitle">Post status to Facebook via access token</ui:define>
<ui:define name="content">
    <div class="row">
            <div class="span12">
                    <div class="row">
                            <h:form>
                <div class="span12">
                    <h2>Post Status Manually</h2>
                    <p>Access token: <h:inputText value="#{postView.accessToken}"/></p>
                    <p>Message: <h:inputText value="#{postView.message}"/></p>
                    <p><h:commandLink action="#{postView.manualPost}" value="Post" styleClass="btn"/></p>
                    <h:panelGroup rendered="#{not empty postView.lastStatusId}">
                        <p>Last status ID: #{postView.lastStatusId}</p>
                    </h:panelGroup>
                </div>
                </h:form>

            </div>
            
        </div>
        
    </div>
    
</ui:define>
</ui:composition>
</html>
The JSF page above simply presents text boxes to input the Facebook access token and the desired message, and a button to call the PostView.manualPost() method.
Also displayed is the link to the last status so you can see it in Facebook.

And that's it!
Steps 1-12 are actually pure boilerplate for most JSF apps. Only steps 13, 14, 15 which is unique to this web application. Which highlights the necessity to create some form of project template or prototype where you can easily construct the basic JSF webapp necessities quickly.
How to Use the App
This app's interface and purpose is actually simple. Deploy the webapp to JBoss AS or to OpenShift (using git push) and :

Put your Facebook access token in it. You can use the Facebook Graph Explorer and your own app to generate an access token. You need to allow the publish_stream privilege.
Put a message, click Post and the app will update your Facebook status.

You check out the live app at fbstatus-soluvas.rhcloud.com.
This is an example of the status generated by the app :

You can check it out here: http://www.facebook.com/ceefour/posts/10150732341781672 . Oh and by the way, you're welcome to add me on Facebook :-)

JBoss Seam 3.1.0.Final Maven artifacts not available RedHat OpenShift Nexus repository?

2012-03-15T03:59:00.001-07:00

remote: [ERROR] The build could not read 1 project -> [Help 1]
remote: [ERROR]
remote: [ERROR]   The project fbstatus:fbstatus:1.0 (/var/lib/libra/7652c51ac0b84512b5edef5*****/fbstatus/runtime/repo/pom.xml) has 3 errors
remote: [ERROR]     Non-resolvable import POM: Could not find artifact org.jboss.seam:seam-bom:pom:3.1.0.Final in nexus (http://mirror1.prod.rhcloud.com:80/nexus/content/groups/public) @ line 18, column 19 -> [Help 2]
remote: [ERROR]     'dependencies.dependency.version' for org.jboss.seam.faces:seam-faces:jar is missing. @ line 40, column 17
remote: [ERROR]     'dependencies.dependency.version' for org.jboss.seam.international:seam-international:jar is missing. @ line 44, column 17

Please don't tell me this is actually what I think it is .... :-(

UPDATE:
Right now pretty much the only way to work around this problem is to add the library JARs manually in WEB-INF/lib.

I've started an OpenShift forum thread on this, please show your support: https://www.redhat.com/openshift/community/forums/express/please-add-jboss-public-maven-repositories

XMPP/GTalk Shell Connector for Apache Karaf / Felix GoGo

2012-02-25T14:28:00.001-08:00

Connecting Felix GoGo Shell through XMPP / Google Talk ?

I did a pretty interesting experiment (and will be useful at least to myself) connecting the Felix GoGo Shell in Apache Karaf/ServiceMix to XMPP/Google Talk Instant Messaging Protocol via Smack library. I spent almost 24 hours just for this. The results is pretty amazing though. :-)

I also spent quite some time to make ANSI colors sort of "working". It's not strictly correct, but at least it's not entirely boring.

What do you think ?

UPDATE: The OSGi Blueprint-compatible XMPP Shell connector is available as open source with Apache License 2.0 at https://github.com/soluvas/com.soluvas.shell.xmpp

Recommended Resources
For more in-depth explanation on OSGi, I highly recommend OSGi in Action: Creating Modular Applications in Java.

Puppet Module for JBoss AS 7.1 "Thunder"

2012-02-16T19:46:00.001-08:00

We at Bippo Indonesia and Soluvas love JBoss AS. Especially with the shiny new release 7.1.0.Final aka "Thunder".

And we love DevOps with Puppet too!

As the least contribution we could provide, our Puppet Module for JBoss AS on GitHub is available as an open source project.

It's currently a work in progress, but as time goes we hope to make it flexible with Puppet's parameterized class feature and hopefully able to do deploy/redeploy/undeploy operations, change logging features, user management, etc. Especially that JBoss has an excellent CLI tool, we hope the integration with Puppet will be relatively easy.

Thank you JBoss!

Reblogged from https://community.jboss.org/blogs/beyondjavaee/2012/02/16/puppet-module-for-jboss-as-71-thunder

UnproxyableResolutionException Workaround when using Scala Closures and javax.inject CDI Beans Together

2012-02-15T08:49:00.001-08:00

Some powerful Scala programming language features like closures, pattern matching, and lazy vals don't work well with dependency injection frameworks like javax.inject aka CDI. This is due to stricter class structure requirements to enable proxying.

For example, this "innocent" code will not work:

@Inject private var fbPhotoImporterFactory: Instance[FacebookPhotoImporter] = _
@Produces @Named("facebookPhotoImporter") private var fbPhotoImporter: ActorRef = _

@PostConstruct
def init() {
    logger.debug("Starting FacebookPhotoImporter actor")
    fbPhotoImporter = Actor.actorOf(fbPhotoImporterFactory.get())
    fbPhotoImporter.start()
}

It will throw:

Caused by: org.jboss.weld.exceptions.UnproxyableResolutionException: WELD-001437 Normal scoped bean class com.satukancinta.web.Persistence is not proxyable because the type is final or it contains a final method public final javax.enterprise.inject.Instance com.satukancinta.web.Persistence.com$satukancinta$web$Persistence$$fbPhotoImporterFactory() - Managed Bean [class com.satukancinta.web.Persistence] with qualifiers [@Any @Default].
    at org.jboss.weld.util.Proxies.getUnproxyableClassException(Proxies.java:225)
    at org.jboss.weld.util.Proxies.getUnproxyableTypeException(Proxies.java:178)
    at org.jboss.weld.util.Proxies.getUnproxyableTypesExceptionInt(Proxies.java:193)
    at org.jboss.weld.util.Proxies.getUnproxyableTypesException(Proxies.java:167)
    at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:110)
    at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:126)
    at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:345)
    at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:330)
    at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:366)
    at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:82)
    at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
    ... 5 more

As you can see, my use code isn't exactly "edge cases".

It's actually a pretty common use case: create a Akka actor and pass a factory function to it, as a closure.
The code above doesn't look like it's using a closure, but it actually is when written like this: (same functionality, but still breaks CDI)

fbPhotoImporter = Actor.actorOf { fbPhotoImporterFactory.get() }

I can see why CDI has a strict requirement, and I can also understand why Scala implements it the way it is (Scala developers definitely already has a lot of problems working around powerful Scala features into a very restrictive JVM bytecode requirements). This is the price we pay for having a somewhat inferior language (Java, please don't get offended) in the first place.

But I as an application developer want to have a quick fix for this issue. Re-coding the class in plain Java is one option, but it turns I don't need to. There is a workaround, by creating a helper method then using it:

@Inject private var fbPhotoImporterFactory: Instance[FacebookPhotoImporter] = _
@Produces @Named("facebookPhotoImporter") private var fbPhotoImporter: ActorRef = _

def createFbPhotoImporter() = fbPhotoImporterFactory.get()

@PostConstruct
def init() {
    logger.debug("Starting FacebookPhotoImporter actor")
    fbPhotoImporter = Actor.actorOf(createFbPhotoImporter)
    fbPhotoImporter.start()
}

Now Scala is happy and CDI is also happy. Yes it's a bit more verbose but not too bad. And I guess the code is now somewhat more understandable for Java guys. :)

Tip: To learn more about Scala programming, I recommend Programming in Scala: A Comprehensive Step-by-Step Guide, 2nd Edition.

Pentaho Data Integration Transformation and Step Architecture

2012-01-16T20:44:00.001-08:00

After doing some Pentaho Data Integration (Kettle) work especially with JSON Output Step in PDI-7195 bug, I guess it's a good thing to describe visually how I see the PDI transformations and steps architecture.

Hopefully this is helpful for you and also to remind me when I'm confused because which Kettle step framework classes/interfaces relate to which ones is sometimes easy to forget. :-)

Learn how to process and integrate enterprise databases & data warehouses easily with Pentaho Data Integration 4 Cookbook.

When do work in Enterprise Application Integration field...

2012-01-13T22:19:00.003-08:00

...be prepared to get ClassNotFoundException, ClassCastException,

and loads of other classpath and classloading problems often. :-)

(if you don't use OSGi, that is...)

When do work in Enterprise Application Integration field...

2012-01-13T22:19:00.001-08:00

...be prepared to get ClassNotFoundException, ClassCastException,

and loads of other classpath and classloading problems often. :-)

(if you don't use OSGi, that is...)

Making JSF 2.0 Composite Components Ajax render-capable

2012-01-11T08:55:00.001-08:00

If you for example have the following composite component in a JSF 2.0 Facelets XHTML template:

<sc:block title="Followers">

<h:panelGroup rendered="#{not empty userShow.user.followedByUsers}">

<ul>

<ui:repeat var="user" value="#{userShow.user.followedByUsers}">

</ui:repeat>

</ul>

</h:panelGroup>

<h:panelGroup rendered="#{empty usefollowedByUsers}">

#{userShow.user.name} has no followers.

</h:panelGroup>

</sc:block>

and try do ajax render:

<a4j:commandButton value="Follow" action="#{userBean.follow(currentUser, userShow.user)}"

render="followPanel followers"

rendered="#{not currentUser.isFollowing(userShow.user)}"/>

This won't work for some reason. Wrong workaround is using a h:panelGroup and moving the id for ajax render there:

<sc:block title="Followers">

<h:panelGroup id="followers">

<h:panelGroup rendered="#{not empty userShow.user.followedByUsers}">

<ul>

<ui:repeat var="user" value="#{userShow.user.followedByUsers}">

</ui:repeat>

</ul>

</h:panelGroup>

<h:panelGroup rendered="#{empty us.followedByUsers}">

#{userShow.user.name} has no followers.

</h:panelGroup>

</sc:block>

The correct solution is to put a #{cc.clientId} like below in the composite implementation:

<composite:implementation>

<h2 class="block-title">#{cc.attrs.title}</h2>

<composite:insertChildren/>

</div>

</section>

</composite:implementation>

Fix Jackson/JAXB JSON Serialization Problem with Spring Data Neo4j @NodeEntity Objects

2011-12-22T05:09:00.001-08:00

Spring Data Neo4j @NodeEntity-annotated objects are proxy-enriched by Spring Data Neo4j aspects using AspectJ. There are times we want to expose these objects via JAX-RS REST API or JAX-WS / SOAP web services and then (by default) we will have problems.

The error stacktrace messages (here using JBoss AS 7.0.2) are along the lines of:

HTTP Status 500 - org.codehaus.jackson.map.JsonMappingException: No serializer found for class org.neo4j.graphdb.DynamicRelationshipType and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationConfig.Feature.FAIL_ON_EMPTY_BEANS) ) (through reference chain: com.satukancinta.domain.User["enjoyActivities"]->org.springframework.data.neo4j.fieldaccess.ManagedFieldAccessorSet[0]->com.satukancinta.domain.Activity["persistentState"]->org.neo4j.rest.graphdb.entity.RestNode["relationships"]->org.neo4j.rest.graphdb.entity.RestRelationship["type"])

type Status report

message org.codehaus.jackson.map.JsonMappingException: No serializer found for class org.neo4j.graphdb.DynamicRelationshipType and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationConfig.Feature.FAIL_ON_EMPTY_BEANS) ) (through reference chain: com.satukancinta.domain.User["enjoyActivities"]->org.springframework.data.neo4j.fieldaccess.ManagedFieldAccessorSet[0]->com.satukancinta.domain.Activity["persistentState"]->org.neo4j.rest.graphdb.entity.RestNode["relationships"]->org.neo4j.rest.graphdb.entity.RestRelationship["type"])

description The server encountered an internal error (org.codehaus.jackson.map.JsonMappingException: No serializer found for class org.neo4j.graphdb.DynamicRelationshipType and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationConfig.Feature.FAIL_ON_EMPTY_BEANS) ) (through reference chain: com.satukancinta.domain.User["enjoyActivities"]->org.springframework.data.neo4j.fieldaccess.ManagedFieldAccessorSet[0]->com.satukancinta.domain.Activity["persistentState"]->org.neo4j.rest.graphdb.entity.RestNode["relationships"]->org.neo4j.rest.graphdb.entity.RestRelationship["type"])) that prevented it from fulfilling this request.

To solve this problem, annotate your entity class with @JsonAutoDetect(JsonMethod.NONE) :

import org.codehaus.jackson.annotate.JsonAutoDetect;

import org.codehaus.jackson.annotate.JsonMethod;

import org.codehaus.jackson.annotate.JsonProperty;

@NodeEntity @JsonAutoDetect(JsonMethod.NONE)

public class User implements NodeBacked {

then manually annotate each property you want to serialize with @JsonProperty :

@JsonProperty

public String getName() {

return name;

}

Now the JAX-RS Application works as intended and everybody is happy. :-) There's also a StackOverflow thread that discusses this problem.

How to Resolve Spring Data Neo4j / Jersey / Jackson Conflict with JBoss AS 7 RESTEasy

2011-12-22T03:26:00.001-08:00

I'm using Spring Data Neo4j REST Client which uses Jersey JAX-RS Client. Unfortunately when deployed to JBoss AS 7.0.2, it conflicts with the built-in RESTEasy deployer (bug DATAGRAPH-159).

In order to run the application, jersey-server must be excluded :

<dependency> <groupId>org.springframework.data</groupId> <artifactId>spring-data-neo4j-rest</artifactId> <version>${spring-data-neo4j.version}</version> <exclusions> ... <exclusion> <artifactId>jersey-server</artifactId> <groupId>com.sun.jersey</groupId> </exclusion> </exclusions> </dependency>

Another issue I came across is my web application is also a JAX-RS Service Application, therefore it requires JBoss RESTEasy. Unfortunately Jackson JSON Provider which is a dependency of Neo4j REST Client and Jersey JAX-RS Client conflicts with RESTEasy's Jackson Provider, with the following exception stacktrace message:

java.lang.RuntimeException: Unable to instantiate MessageBodyReader  org.jboss.resteasy.spi.ResteasyProviderFactory.registerProvider(ResteasyProviderFactory.java:760)  org.jboss.resteasy.spi.ResteasyProviderFactory.registerProvider(ResteasyProviderFactory.java:742)  org.jboss.resteasy.spi.ResteasyDeployment.registerProvider(ResteasyDeployment.java:505)  org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:305)  org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:225)  org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:67)  org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)  org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:139)  org.jboss.as.web.NamingValve.invoke(NamingValve.java:57)  org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)  org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362)  org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:897)  org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:626)  org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:2054)  java.lang.Thread.run(Thread.java:722)

root cause

java.lang.RuntimeException: Illegal to inject a message body into a singleton into public org.codehaus.jackson.jaxrs.JacksonJsonProvider(org.codehaus.jackson.map.ObjectMapper,org.codehaus.jackson.jaxrs.Annotations[])  org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:209)  org.jboss.resteasy.core.ConstructorInjectorImpl.injectableArguments(ConstructorInjectorImpl.java:63)  org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:129)  org.jboss.resteasy.spi.ResteasyProviderFactory.getProviderInstance(ResteasyProviderFactory.java:1038)

I thought this was issue RESTEASY-503, because JBoss AS 7.0.2 happened to use the somewhat buggy RESTEasy 2.2.1.GA. But it turns out there is an easy fix to this problem, thanks to Configuring Module Classloading in JBoss AS 7.

Edit src/main/webapp/WEB-INF/jboss-deployment-structure.xml as follows:

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.0">

</dependencies>

</deployment>

</jboss-deployment-structure>

Now Spring Data Neo4j, Jersey Client with JSON Jackson Provider, and my JAX-RS Application served by RESTEasy, all can coexist in the same web application WAR. :-)

I don't "get" JSON Output in Pentaho Data Integration (PDI) / Kettle

2011-12-07T02:23:00.001-08:00

I don't understand how to use the JSON Output step properly in Kettle aka Pentaho Data Integration (PDI).

With "Nr of rows in a bloc" set to 0 or 3, I got:

{
"categories": [
    {
      "code": "WORKAHOLIC-CHIC"
    },
    {
      "name": "Workaholic Chic"
    },
    {
      "description": "Move ! Move ! move...!!\nLight Up Your Day... with a perfect match, \nPadanan busana kerja Professsional look, Powerfull & Fashionable,\nwhich got several design for different mood, multifunction,\nMemorable style!\nLetâ€™s be and stay Tuneeca...\n"
    }
]
}

which is basically only the last record.

With "Nr of rows in a bloc" set to 1, I got:

{
"categories": [
    {
      "code": "AKSESORI-LIGHT-UP-YOUR-DAY"
    },
    {
      "name": "Aksesori Light Up Your Day"
    },
    {
      "description": "-"
    },
    {
      "code": "AKSESORIS-APRIL-2009"
    },
...

What I'm trying to get is:

{ "categories": [
{ "code": "AKSESORI-LIGHT-UP-YOUR-DAY",
"name": "Aksesori Light Up Your Day"
"description": "Very cool" },
{ "code": .........

Contrast this with the XML Output, which I get the following correct output right from first try:

<?xml version="1.0" encoding="UTF-8"?>
<categories>
<category>
    <code>AKSESORI-LIGHT-UP-YOUR-DAY</code>
    <name>Aksesori Light Up Your Day</name>
    <description>-</description>
</category>
<category>
    <code>AKSESORIS-APRIL-2009</code>
...

An additional plus is that XML Output already performs a bit of output pretty formatting, which I appreciate very much. (JSON Output outputs everything in a single line)

Those two Output steps gets the same input data.

Any ideas ?

Seam Framework Java EE Library version 3.1.0.Beta4 Released

2011-10-26T05:45:00.001-07:00

As per usual, let's get the links out of the way first:

Download Seam 3.1.0.Beta4

Reference Documentation

API Documentation

Report Issues

For Maven users, there is a new version of the Seam Bill of Materials:

<dependency> <groupId>org.jboss.seam</groupId> <artifactId>seam-bom</artifactId> <version>3.1.0.Beta4</version> <type>pom</type> <scope>import</scope> </dependency>

I know that we promised a CR1 release for Seam 3.1 at about this time, however the Seam QA team have done their jobs a little too well and identified a number of issues with the Beta3 release which we wanted to get fixed before we go to a candidate release. The great news for this release is that we've fixed 68 issues - you can view the issue list here:

https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12315988

Included in this release is a number of new features, improved documentation and a brand new Arquillian-based structure for our test suites to make it easier to test each module on multiple containers. We've also squashed a great deal of bugs, improved stability, plus made a number of other minor improvements.

As we still have quite a few open issues remaining for the Seam 3.1 release, we will likely release another beta in the next couple of weeks. We want this release to be rock solid, so please try out the beta and let us know if you find any problems.

(Article copied verbatim from in.relation.to)

m2e/m2eclipse-wtp 0.14.0 Released: Eclipse IDE Integration for Java EE 6 / Web Application Maven projects

2011-09-30T04:43:00.000-07:00

Maven Integration for Eclipse WTP 0.14.0, a.k.a m2eclipse-wtp, a.k.a m2e-wtp is out the door. This new release brings its share of new features and enhancements, as well as a bunch of bug fixes. The complete release notes are available here.

m2e-wtp 0.14.0 works with Eclipse Helios and Indigo, requires at least m2e 1.0 and mavenarchiver plugin > 0.14.0 (0.15.0 should be automatically installed). As usual, m2e-wtp can be installed from :

the Maven Discovery mechanism : Window > Preferences > Maven > Discovery > Open catalog
the Eclipse Marketplace : Help > Eclipse Marketplace
the update site : http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/

So what's new and noteworthy in 0.14.0? Let's see :

New support for Application Client projects

Application Client packaging has been introduced with the new maven-acr-plugin. Support for app-client type dependencies has been added in maven-ear-plugin 2.6. Since Application Client projects are natively supported in WTP, we added a new configurator for app-client projects. When an app-client project is imported / configured via m2e, the Application Client Facet will be automatically installed, its version inferred from the contents of META-INF/application-client.xml. Filtering of the deployment descriptor is supported.

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-acr-plugin</artifactId>
  <version>1.0</version>
  <extensions>true</extensions>
  <configuration>
    <archive>
      <manifest>
        <mainClass>foo.bar.appclient.Main</mainClass>
      </manifest>
    </archive>
    <filterDeploymentDescriptor>true</filterDeploymentDescriptor>
  </configuration>
</plugin>

New support for Web Fragment projects

If a project contains a META-INF/web-fragment.xml in it's compilation output folder, the Web Fragment Facet is automatically installed upon maven project configuration (the Utility Facet is removed if necessary). Note that, as per the Java EE6 spec - and WTP is very picky about it-, Web Fragment projects *must* use Java 1.6. Failure to comply will fail the configuration and an error marker will be displayed.

The use of target/m2e-wtp/web-resources is now optional

Remember, target/m2e-wtp/web-resources/ is used to allow the deployment of automatically generated web resources with WTP.

On some occasions however, having target/m2e-wtp/web-resources/ might cause some troubles (incompatibilities with WTP editors, IBM RAD, using Servlet.getRealPath(...) in your code).
As a workaround, you can choose to not use target/m2e-wtp/web-resources/ and generate the pom.properties and MANIFEST.MF files in your source directory instead (It'll be your responsibility to add these files to your SCM ignore list).
In order to remove target/m2e-wtp/web-resources/ from the list of deployed folders, you need to change some preferences :

on your project only : right-click on the project > Properties > Maven > WTP : check "Enable Project Specific Settings" and uncheck "Maven Archiver generates files under the build directory"
on the whole workspace : Window > Preferences > Maven > WTP : uncheck "Maven Archiver generates files under the build directory"

Please note that this setting will be overridden if web resource filtering is in use, that is if the maven-war-plugin configuration declares <webResources> or sets <filterDeploymentDescriptor> to true. The reason is simple : you don't want to see your source files overwritten by the filtering mechanism (and it would also lead to some not-so-funny build loops).

Custom file name mapping for web project dependencies

Since the maven-war-plugin allows file name customization for librairies and TLDs, based on patterns (http://maven.apache.org/plugins/maven-war-plugin/examples/file-name-mapping.html), we added the the same feature in m2e-wtp. That will allow you to use a version-less name mapping for dependencies, like :


<plugin>

  <groupId>org.apache.maven.plugins</groupId>

  <artifactId>maven-war-plugin</artifactId>

  <version>2.1.1</version>

  <configuration>

    <outputFileNameMapping>@{groupId}@-@{artifactId}@.@{extension}@</outputFileNameMapping>

  </configuration>

</plugin>

The trick here is, in order to support non default filename mappings of dependencies listed in the Maven Library, the artifact is copied to the build directory (the target/ folder by default) under its new name. So if you happen to run a clean build of your project, wiping out that directory, you will need to manually run "Maven > Update Project configuration" on your project.

Option to not publish overlay changes automatically

In order to support publishing of overlay changes automatically, m2e-wtp aggressively cleared the cache of the servers your application is deployed to. However, The overlay feature still being in an experimental state, we decided to be more conservative with regard to server publishing, so a new "Automatically republish servers on overlay modification" preference has been added to Window > Preferences > Server > Overlays.

Overlays support is not bound to Maven, that's why it's under the Server preferences.

Support for the new tag="defaultRootSource" introduced in WTP 3.3.1

When several source folders are declared in the .settings/org.eclipse.wst.common.component file, WTP prior to 3.3.1 (Indigo SR1) tended to generate files (web.xml, faces-config.xml, ...) in the first folder it found. Since web projects define target/m2e-wtp/web-resources as the first source folder (target/m2e-wtp/ear-resources/ for EAR projects), that would cause some issues. In WTP 3.3.1, a new tag has been introduced, designed to indicate which source folder should be used by default, when files need to be looked for / generated. m2e-wtp now adds this tag when WTP 3.3.1 is installed :

<project-modules id="moduleCoreId" project-version="1.5.0">
    <wb-module deploy-name="web-0.0.1-SNAPSHOT">
        <wb-resource deploy-path="/" source-path="/target/m2e-wtp/web-resources"/>
        <wb-resource deploy-path="/" source-path="/src/main/webapp" tag="defaultRootSource"/>
        <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/java"/>
         <property name="context-root" value="multi-web"/>
        <property name="java-output-path" value="/multi-web/target/classes"/>
    </wb-module>
</project-modules>

A bit of documentation

As many projects, unfortunately, m2e-wtp doesn't shine in the documentation area. I've been using the github Wiki (https://github.com/sonatype/m2eclipse-wtp/wiki) to start a relatively modest FAQ. I'm planning on adding more content in the near future, but I'm also hoping the community at large will want to contribute some docs of its own. You just need a github account to be able to edit the Wiki.

As always, if you find any issue, please open a bug report at https://issues.sonatype.org/browse/MECLIPSEWTP (and don't forget to attach some test projects).

Happy coding.

Fred.
https://twitter.com/#!/fbricon

(the article above is copied verbatim from Planet JBoss)

Hendy's personal note:
To learn more about Java Web Development using Eclipse IDE and Java EE 6, I highly recommend The Java EE 6 Tutorial: Basic Concepts (4th Edition) (Java Series) by Eric Jendrock, Ian Evans, Devika Gollapudi and Kim Haase.

JBoss Tools 3.3.0.M3 Released: Eclipse Plug-ins for Java EE 6 + JSF 2.0 Web Development

2011-09-19T09:15:00.001-07:00

It's time for a new fresh milestone update of JBoss Tools:

3.3 M3 (Greased Lightning)

[Download] [Update Site] [What's New] [Forums] [JIRA] [Twitter]

JBoss Tools is a set of plugins for Eclipse Java IDE that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution. For this release we continue to move Maven, CDI, Java EE 6 support forward and also add in a few new "surprise" features.

To know more about Java EE 6, I highly recommend The Java EE 6 Tutorial: Basic Concepts (4th Edition) (Java Series) by Eric Jendrock, Ian Evans, Devika Gollapudi and Kim Haase.

Installation

As always, get and install Eclipse 3.7 (Indigo) JEE bundle - with the JEE bundle you majority of the dependencies letting you save bandwidth:

Once you have installed Eclipse, you either find us on Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.

The updatesite URL to use from Help > Install New Software... is:

http://download.jboss.org/jbosstools/updates/development/indigo/

Maven Profile Selection

In this release we've therefore included an UI which allows you to easily set/change the profiles on single and multiple projects.

This is especially something that becomes useful when you use Arquillian where it is a common practice to use Maven profiles to toggle the various dependency sets for each server you wish to test against.

It works by you selecting the relevant project(s), press Ctrl+Alt+P or use Maven > Select Maven Profiles... and a dialog box appears allowing you to enable/disable the available profiles for the project(s):

Easier Remote Debugging

Ever been tired of having to manually configure ports, projects and source path lookups for debugging on Remote Applications in Eclipse ?

We are, especially after we learned that JVM's running on Hotspot provides API to discover such applications and allow for easy configuration of your debugger. In this release we've thus added a command available from Debug As... > Remote Java Application... in the context menu on any set of resources.

Once you select this command, we use the Hotspot API to discover the remote running applications, allows you to select which you application want to connect to and then we do the tedious work of configuring the ports, names and source code lookups (including maven dependencies if applicable) for your Remote debugging.

No need for manual tweaking anymore.

Thanks to Aslak Knutsen for bringing us the idea and initial code to make this happen!

Running Server Detection

The server adapters now attempt to detect if a server is already running to avoid port conflicts and UI inconcistencies. If a server is detected running you are shown a dialog allowing you to choose to either have the server adapter assume it is already running or force the launch anyway.

CDI & Seam Solder

The CDI tooling adds a bunch of quickfixes to have JBoss Tools fix common issues. To aid in searching and navigating your CDI application, Find References (Ctrl+Shift+G) will now show the full list of injection points and EL usage of your beans and Seam Solder and Config annotations and XML now have easy hyperlink navigation to it's declarations.

@ManagedBean's

The JSF tooling now detects @ManagedBean annotations. This avoids false warnings/errors when importing JSF 2 examples. Do consider using @Named instead for better integration into the JavaEE stack.

SAR Projects

For a long time we have been asked about providing support for SAR style projects for use on older versions of JBoss AS. This style of project packaging is now supported both in pure WTP style projects and via Maven.

GWT Tools are back

Since last time, Google released their GWT eclipse plugin in a version that supports Eclipse 3.7 allowing us to reenable the GWT Tools.

And more...

There are additional bugfixes and more features to browse over at What's New & Noteworthy

Like the new features ? Leave a comment to let us know!

And by all means,

Have fun!

To know more about Java EE 6, I highly recommend The Java EE 6 Tutorial: Basic Concepts (4th Edition) (Java Series) by Eric Jendrock, Ian Evans, Devika Gollapudi and Kim Haase.

(Article reblogged from JBoss Tools blog)

How to Fix Ant Build Error: "Could not load a dependent class com/jcraft/jsch/Logger. It is not enough to have Ant's optional JARs"

2011-08-03T20:08:00.001-07:00

If you get an error message like this while running a problematic Ant build script file :

remote.flush:

BUILD FAILED
/home/ceefour/git/magento-id/build.xml:13: The following error occurred while executing this line:
/home/ceefour/git/magento-id/build.xml:22: Problem: failed to create task or type sshexec
Cause: Could not load a dependent class com/jcraft/jsch/Logger
       It is not enough to have Ant's optional JARs
       you need the JAR files that the optional tasks depend upon.
       Ant's optional task dependencies are listed in the manual.
Action: Determine what extra JAR files are needed, and place them in one of:
        -/home/opt/eclipse_web/plugins/org.apache.ant_1.8.2.v20110505-1300/lib
        -/home/ceefour/.ant/lib
        -a directory added on the command line with the -lib argument

Do not panic, this is a common problem.
The commonest cause is a missing JAR.

This is not a bug; it is a configuration problem

It means your Ant build script file using optional Ant libraries and need to tell Ant where to find them.

In my case, it needs jsch.jar aka libjsch-java package in Debian/Ubuntu Linux.

First you need to install ant-optional package for Ant optional libraries support :
sudo apt-get install ant-optional

Then the libjsch-java Debian/Ubuntu package:
sudo apt-get install libjsch-java

Then put it in correct directories so that Ant can find them :

sudo ln -s /usr/share/java/jsch.jar /usr/share/ant/lib/
mkdir -vp ~/.ant/lib
ln -s /usr/share/java/jsch.jar ~/.ant/lib/

Ubuntu's Ant look for libraries in /usr/share/ant/lib folder, while Eclipse IDE's Ant look for optional Ant libraries in $HOME/.ant/lib folder.

Note that for Eclipse IDE, you may need to refresh Eclipse Ant Plug-in's Runtime Classpath, by going to Window > Preferences > Ant > Runtime, and clicking "Restore Defaults".
Make sure that the required libraries are now listed under "Global Entries".

Ant build system is frequently used in typical Java EE 6 enterprise application development. I highly recommend The Java EE 6 Tutorial: Basic Concepts (4th Edition) for a practical guide to the Java EE 6 technology.

JBoss AS 7.0 Final Version Released, Lighting Fast & Configurable Java EE 6 Web Application Server

2011-07-12T07:20:00.001-07:00

There have been many highs in my career and many of those have happened since I joined JBoss and took over from Sacha. But today has to be in my top 1 or 2 ever! Today we can officially announce the release of JBossAS 7.0 Final! And it's EE6 Web Profile compliant too, so check out the project pages. It's taken us a while to get here and we've taken some pretty drastic and innovative steps along the way. Sometimes those decisions haven't been ease to make and we've thought long and hard about them. For instance, I recall Jason Greene, Scott Stark and I discussing for ages the various ramifications of continuing with the then current micro container architecture versus radical changes. The decision to change wasn't easy, but even then well over a year ago, we believed it was the right one to make. And now, with the new micro services container, it's proven itself! Some risks are worth taking.

But not every problem on our path has been technical or come from within Red Hat. Without going into details, let's just say that at times it seemed that processes and red tape were being thrown in our way. However, we got past these and the results speak for themselves: the fastest, most configurable and adaptable EE6 implementation (Web Profile) out there. And full EE6 is next on the roadmap, with JBossAS 7.1 due out soon. So if you haven't already tried it I encourage you to download it and give it a try.

I want to take this opportunity to thank everyone who has been involved in the development of JBossAS 7.0. This includes a diverse group of people including the projects, our QE teams, docs, support, product management, program management, marketing and many others. It would be impossible to single out those individuals who have stood out during the last 18 months since everyone has been a rockstar. However, I do want to mention Jason Greene again: any team is influenced both negatively or positively by it's leader and Jason has lead most positively by example throughout. And of course Bruno Georges, the engineering manager, who took over the role just over a year ago and mustered his troops so well! See what I mean? It's really hard to call out one person without immediately thinking of all of the others involved! A great team effort.

To know more about Java EE 6, I highly recommend The Java EE 6 Tutorial: Basic Concepts (4th Edition) (Java Series) by Eric Jendrock, Ian Evans, Devika Gollapudi and Kim Haase.

I also recommend Enterprise JavaBeans 3.1 by Andrew Lee Rubinger and Bill Burke for a thorough explanation on updated EJB 3.1 technology (including interceptors). You can find more Java EE 6 Resources here.

(Article copied mostly verbatim from Mark Little's announcement)