Seam CVS now on JBoss AS 4.2 CR1

[christian.bauer]

We migrated the Seam examples to JBoss AS 4.2 CR1 in the last two weeks. So all of you who are staying up-to-date with CVS, you should no longer deploy the examples on JBoss AS 4.0.5. Please report any issues you find on 4.2.

[christian.bauer]

Uh, can someone make this posting sticky, please :)

[shane.bryzak]

And make sure you copy jboss-el.jar into your jboss/server/default/deploy/jboss-web.deployer/jsf-libs directory.

[christian.bauer]

I thought that was fixed by Norman and the jboss-el.jar is now fine in the web classloader. From what I'm seeing with the examples this works and we have an AJAX4JSF/JSF RI incompatibility issue left:

http://jboss.com/index.html?module=bb&op=viewtopic&t=104351

[christian.bauer]

And if you try to drop the JSF RI 1.2_04 JARs into the 4.2 CR1 web deployer directory, replacing the old ones, you get:

10:31:38,559 ERROR [[/]] Error configuring application listener of class com.sun.faces.application.WebappLifecycleListener
java.lang.ClassNotFoundException: com.sun.faces.application.WebappLifecycleListener
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3797)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)

[avbentem]

The JBoss AS download pages claim "Important Note: If you want to use EJB3 or Seam, you MUST use the JEMS Installer." And at the time of writing this, the wiki also still tells people to use the installer. However, the latest JEMS installer, 1.2.0.GA holds AS 4.0.5.GA.

So:

Does anyone know of any special issues when setting up AS 4.2 CR1 without the JEMS installer?

[avbentem]

"avbentem" wrote:
The JBoss AS <a href="http://labs.jboss.com/portal/jbossas/download">download pages</a> claim "Important Note: If you want to use EJB3 or Seam, you MUST use the JEMS Installer."

I just read the AS 4.2 RC1 readme, which claims:

<a href="http://labs.jboss.org/portal/jbossejb3">JBoss EJB3</a> is now deployed *by default* in JBossAS 4.2.x The fact that we base on JDK5 makes our life easier in this regard, meaning we don't have to maintain jdk5 code retro-weaved for jdk1.4 runtimes, and we can include by default components that require jdk5 to run.

As the Seam installation always required one to select the EJB3 profile when using the JEMS installer, I guess the JEMS installer might no longer be needed now that JBoss AS deploys EJB3 it by default?

[pmuir]

Just download the zip for 4.2.CR1, unzip it, and deploy the app. No installer needed

[avbentem]

"petemuir" wrote:
Just download the zip for 4.2.CR1, unzip it, and deploy the app. No installer needed

You're right, thanks.

How can we assure the "Important Note: If you want to use EJB3 or Seam, you MUST use the JEMS Installer" will be removed when Seam 1.3 is released? Should I add an issue to JIRA? This will also apply to the Getting Started, which is already outdated anyhow. Of course, we can change the wiki ourselves.

Just for the archives, to use Seam 1.3.x from CVS:

- download JBoss AS 4.2 CR1 and unzip it
- check-out jboss-seam from :pserver:[e-mail]:/cvsroot/jboss
- edit build.properties to set jboss.home (ignore the Tomcat settings)
- run "ant antlr" to generate SeamTextParser and SeamTextLexer
- optionally edit build.xml to read something like the following (I guess this should be fixed in CVS):

<property name="version" value="1.3" />
 <property name="patchlevel" value="0.SNAPSHOT" />

- when getting compile errors in GWTRemoteService then optionally download the Google Web Toolkit (Beta), unzip, copy gwt-user.jar to jboss-seam/lib and add the JAR to Eclipse using Project, Properties, Java Build Path, Add JARs (this gets one com.google.gwt.user.client.*; I'm not sure if this is the right approach to get rid of the errors)

And then, for example:
- run "ant deploy" from examples/dvdstore
- browse to http://localhost:8080/seam-dvd

[pmuir]

"avbentem" wrote:
[How can we assure the "Important Note: If you want to use EJB3 or Seam, you MUST use the JEMS Installer" will be removed when Seam 1.3 is released? Should I add an issue to JIRA? This will also apply to the <a href="http://labs.jboss.com/portal/jbossseam/gettingstarted">Getting Started</a>, which is already outdated anyhow. Of course, we can change the <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamInstallation">wiki</a> ourselves.

Yeah, add a JIRA issue if you like...

- optionally edit build.xml to read something like the following (I guess this should be fixed in CVS):

<property name="version" value="1.3" />
 <property name="patchlevel" value="0.SNAPSHOT" />

We up the version number at release.

- when getting compile errors in <a href="http://fisheye.jboss.com/browse/JBoss/jboss-seam/src/remoting/org/jboss/seam/remoting/gwt/GWTRemoteService.java?r=1.1">GWTRemoteService</a>

CVS is compiling fine for me with the libraries in lib/

[robjellinghaus]

Does Seam CVS now deploy JSF 1.2 to Tomcat for the deploy.tomcat targets? That's the part of Seam 1.3 that I'm really waiting for, as a Tomcat user....

[christian.bauer]

Someone make this sticky please, I don't have the permissions.

[shane.bryzak]

"avbentem" wrote:

- when getting compile errors in <a href="http://fisheye.jboss.com/browse/JBoss/jboss-seam/src/remoting/org/jboss/seam/remoting/gwt/GWTRemoteService.java?r=1.1">GWTRemoteService</a> then optionally <a href="http://code.google.com/webtoolkit/versions.html">download</a> the Google Web Toolkit (Beta), unzip, copy gwt-user.jar to jboss-seam/lib and add the JAR to Eclipse using Project, Properties, Java Build Path, Add JARs (this gets one com.google.gwt.user.client.*; I'm not sure if this is the right approach to get rid of the errors)

Which compiler errors are you getting? I don't get any.

[avbentem]

"avbentem" wrote:

- when getting compile errors in <a href="http://fisheye.jboss.com/browse/JBoss/jboss-seam/src/remoting/org/jboss/seam/remoting/gwt/GWTRemoteService.java?r=1.1">GWTRemoteService</a> then [...]

Which compiler errors are you getting? I don't get any.

I did get errors in Eclipse (actually JBoss IDE 2.2.0.BETA2), all caused by a few

The import com.google cannot be resolved
/src/remoting/org/jboss/seam/remoting/gwt/GWTRemoteService.java line 31

But, as petemuir wrote that the libraries in /lib worked fine, I now tested with gwt-servlet.jar (as included in /lib with the Seam download). That solves the problem too, so indeed no need to download anything from Google.

Without adding gw-servlet.jar an Ant build runs fine too, so it just seems to be missing in the Eclipse classpath file.

Thanks,
Arjan.

[avbentem]

"petemuir" wrote:

"avbentem" wrote:
How can we assure the "Important Note: If you want to use EJB3 or Seam, you MUST use the JEMS Installer" will be removed when Seam 1.3 is released? [..]

Yeah, add a JIRA issue if you like...

Ok, JBSEAM-1193.

I also noticed that the JBoss version is not yet updated in the documentation (like "2.1. Before you start", "Make sure you have JDK 5 or JDK 6, JBoss AS 4.0.5 and Ant 1.6..."). Of course, I know this might be work in progress; do you want JIRA issues for these details as well...?

"petemuir" wrote:
We up the version number at release.

Ok, no problem, though (for example) I'd slightly prefer the generated documentation to show 1.3 instead of 1.2.1.GA...


Arjan.