You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
If you get an error like:
00:16:23,061 WARN [ServletLifecycle] Error creating WebBeanDiscovery providerorg.jboss.webbeans.integration.jbossas.WebBeanDiscoveryImpl java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.jboss.webbeans.servlet.ServletLifecycle.getWebBeanDiscovery(ServletLifecycle.java:150) at org.jboss.webbeans.servlet.ServletLifecycle.beginApplication(ServletLifecycle.java:65) at org.jboss.webbeans.servlet.WebBeansListener.contextInitialized(WebBeansListener.java:48) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4393) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:367) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:460) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:96) ........ Caused by: java.lang.NullPointerException at org.jboss.webbeans.integration.jbossas.ejb3.EjbDiscoveryEnvironment.lookup(EjbDiscoveryEnvironment.java:123) at org.jboss.webbeans.integration.jbossas.ejb3.EjbDiscoveryEnvironment.<init>(EjbDiscoveryEnvironment.java:41) at org.jboss.webbeans.integration.jbossas.WebBeanDiscoveryImpl.<init>(WebBeanDiscoveryImpl.java:25) ... 65 more
then it's likely that the update to EJB3 in JBoss AS5 failed. Unfortunately, in Web Beans 1.0.0.ALPHA1, the update script isn't very clear if the EJB3 update fails, so check the log carefully.