I think I have solved some of the problems... library version conflicts are a constant problem anyway, with one webapp I ran into the problem that I was using spring and the spring-jsf binding lib and I ran into an internal el error once I had declared managed properties, where the calling order went from jsf-spring into jboss and there into commons-el
I guess the other problems have a similar nature. Frode Oldervoll wrote: > Try setting UseJBossWebLoader to true in > server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml. This > was changed from true to false from JBoss 4.0.1 to 4.0.2 due to J2EE > certification compatibility, but several applications have problems with not > using the JBoss WebLoader. > > -Frode Oldervoll > >
