This looks like a myfaces compatibility problem. What is the AS version released together with Portal RC2? And what version of jBPM are you using?
I have the same problem: AS 4.0.3SP1 with jBPM3.1 and JBoss-Portal2.2.0 deployed on the same server
I thought that, since jbpm.war and jboss-portal are two distinct webapps, there should have not been any conflict issue...
How can we solve this problem?
thanks a lot
I managed to deploy the jbpm.war (jbpm3.1) on a server where jboss-portal2.2.0 was also deployed - the problem was due to two different versions of tomahawk.jar
just in case someone else needs to do it, this is what I suggest you to do:
1. take the tomahawk.jar file from jboss-portal\jboss-portal.sar\lib and copy it into jbpm-starters-kit-3.1\jbpm\lib\jsf
2. go under jbpm-starters-kit-3.1\jbpm and run "ant build.webapp"
3. copy the jbpm-webapp-3.1.jar file you just built from jbpm-starters-kit-3.1\jbpm\build
4. unzip jbpm.war and paste the jbpm-webapp-3.1.jar under WEB-INF\lib
5. under WEB-INF\lib paste as well the tomahawk.jar file taken from jboss-portal
6. zip jbpm.war and deploy it
I am successful as your confuguration, but your protal and JBoss AS version are not the latest version. What should I do that can also successe in the latest version? The latest Jboss AS version is 4.0.4 and the protal is 2.4.0. Thanks very much!
PLEASE do not crosspost in two completely different topics and at least in one of the posts, try adding ANY information on what goes wrong. A post like this, "it doesn't work, please help" is unlikely to get you any helpful responses.
I managed to get jBPM 3.1.2 running on JBoss AS jboss-4.0.5.GA (After a lot of googling and also searching here in this forum). However, when i deployed JBoss Portal jboss-portal-2.4.1 on the same AS, the problem discussed above did occur.
It seems the two tomahawk.jar files included in the deliveries are different and conflict. I tried to move either of them in the AS default/lib. Problem remains.
Has anyone ever succeeded in deploying the latest JBoss Portal and jBPM on one Jboss AS and what tricks should be done to get them working together?
Tks a lot!
i had the same problem and solved it by replacing the myfaces-api.jar and myfaces-impl.jar in jbossweb-tomcat55.sar/jsf-libs with the "same" jars from jbpm.war/WEB-INF/lib. The ones in jbpm.war need to be removed.
but i don't understand why i should have done that. it is somehow a strange behavior of jboss-as or the integrated web container. anyone can throw some light on this issue?
I went the other way and removed jsf-impl-14.jar and jsf-api-14.jar
from jbpm-console.war and put in the myfaces-impl.jar and myfaces-api.jar from
the jbossweb-tomcat location listed above.
This seemed to fix the bizzare
09:43:05,881 INFO [TomcatDeployer] deploy, ctxPath=/jbpm-console, warUrl=.../tmp/deploy/tmp53884jbpm-enterprise.ear-contents/jbpm-console-exp.war/ 09:43:06,794 ERROR [STDERR] Jan 28, 2007 9:43:06 AM com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b09-FCS) for context 'null' 09:43:08,220 ERROR [STDERR] Jan 28, 2007 9:43:08 AM com.sun.faces.spi.InjectionProviderFactory createInstance WARNING: JSF1033: Resource injection is DISABLED.
afaik, the 3.2 console does need some jsf 1.2 things, so myfaces (which is jsf 1.1 compliant) will probably not work for all things. But maybe David could elaborate on this.
Your right that was not needed.
See posting http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013125#4013125
for how I got it running by setting isTransactionEnabled to false and isCurrentSession enabled to false on jboss 4.0.5ga.
However, this does not solve the original issue.
Whats up with JTA vs. CMT transaction configuration?
Is this resolved? Has anyone figured out how to properly configure transactions for 4.0.5ga?
Please can anyone respond to this one, it is all that stands in the way of getting cvs trunk to run on 4.0.5ga
More on subject