[ https://jira.jboss.org/jira/browse/JBPM-2380?page=com.atlassian.jira.plug... ] kamalakannan sathya updated JBPM-2380: -------------------------------------- Attachment: error.txt I have the same issue when running with jboss 4.0.2 version. Attaching my stack trace -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2380?page=com.atlassian.jira.plug... ] Osvaldo Pina updated JBPM-2380: ------------------------------- Attachment: build.xml build.xml with jboss 4 specific tasks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2380?page=com.atlassian.jira.plug... ] Osvaldo Pina commented on JBPM-2380: ------------------------------------ I have a workaround for this issue: 1- Get the source svn co http://anonsvn.jboss.org/repos/jbpm/jbpm4/tags/jbpm-4.0/ jbpm-4.0-src 2-Get the attached patch 3- Apply the patch cd jbpm-4.0-src patch -p0 -i ../jbpm_Jboss-4.2.3_patch.diff 4-Build the sources mvn clean install 5-Go to the previous directory and unizp the Jbpm 4.0 installation 7-Copy artifacts generated by maven to the installation lib directory: cp jbpm-4.0-src/modules/integration/jboss4/target/jbpm-jboss4-4.0.jar jbpm-4.0/lib cp jbpm-4.0-src/modules/integration/spi/target/jbpm-spi-4.0.jar jbpm-4.0/lib 8-Copy the attached build.xml to the installation jboss directory cp build.xml jbpm-4.0/jboss 9-Copy the attached jboss-service.xml to the installation jboss 4 configuration directory: cp jboss-service.xml jbpm-4.0/jboss/config.jboss4/deploy/jbpm/jbpm-service.sar/META-INF 10-Go the the jboss directory and run installation script: ant demo.setup I testes only against jboss 4.2.3.GA, for other versions of jboss 4 you have to change the build.xml file by adding other <equals> with the other version numbers: <condition property="jboss.version.4"> <or> <equals arg1="${jboss.version}" arg2="4.2.3.GA" /> </or> </condition> I'm posting this as a workaround because I'm not a specialist on JBoss JMX Microkernel, so I'm not aware of all consequences of this solution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2380?page=com.atlassian.jira.plug... ] Ronald van Kuijk commented on JBPM-2380: ---------------------------------------- The jBPM deployer is also 'under development' on JBoss 5. It was a 'last minute' change, so that is not a 'bug' but a known issue that will be fixed in the not so distant future. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-2380?page=com.atlassian.jira.plug... ] Tom Baeyens resolved JBPM-2380. ------------------------------- Resolution: Rejected after we revisted the jboss integration in jbpm 4.2, if then a contribution is made to support jboss 4.x in sync with how we support jboss 5 at that point, then we can accept it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira