Enterprise Client Community

Hello Forum,

does someone has any experience with an jboss deployment ?
Normaly jsf libraries should not be deployed within web applications, but without captainCasa isn't working at all. When including them and directing jboss to use these with:

<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
</context-param>

the app runs fine in the browser, but constantly throws errors in the background like:

Exception thrown by attributes event listener
java.lang.ClassCastException: com.sun.faces.application.ApplicationAssociate

Session attribute event listener threw exception
java.lang.ClassCastException: com.sun.faces.application.ApplicationAssociate

xception sending request destroyed lifecycle event to listener instance of class com.sun.faces.application.WebappLifecycleListener
java.lang.ClassCastException: com.sun.faces.application.ApplicationAssociate

Hi,

there are a couple of things to pay attention to when deploying with JBoss (the typical things: classloading issues) - and there is one bug fix to be installed prior to being able to succeed. Pls. wait for the next update - it will contain information about JBoss installation.

The next update will be available begin of next week.

Björn

Hi,

today's version is "JBoss-tested"...

Please do the folloing:

(1) Update your project (this is a step you have to do with each version update, so this is just to make you remember...). Info on updating existing installations is part of the Intallation Guide.

(2) Before you pass the .war file to JBoss, make sure:
(a) log4j*.jar need to be taken out
(b) jsf-api.jar and jsf-impl.jat need to be taken out
Background: JBoss is quite rigid in not allowing web applications to use non-Jboss JSF implementations...

See: http://lists.jboss.org/pipermail/jboss-user/2007-April/054580.html and many more discussions on this.

Anyway: now the CaptainCasa server part is running in the JSF implementation of JBoss. There is in principal no problem with this..., but: from our measuring this implementation is slower than the reference implementation provided by Sun. Seems to have to do with the fact that the component tree is saved and restored with every request cycle - and not kept in memory as the Sun implementation does it.

Maybe this is something, others can input experience as well...

Hope, it's working now on your side.

Björn

...one additional info, which is related to this thread as well: http://www.casabacdemo.com/forum/posts/list/173.page

JBoss catches the System.err stream and outputs it to the normal console (when using default configuration). Result: do not get confused about the ERRRO-messages which are produced - have a look into their content, in whcih the Java Logging output is done. And... switch off console loffingin /eclntjsfserver/config/logging.xml when working with JBoss.

Björn