[jboss-user] [JBoss jBPM] - Re: Deploy Processdefinition via Ant
I'm using 3.2.6.SP1 too. Have you checked the content of the database after the deployment? Note that the target database of the deployment may be different from the one that is used by the jbpm-console. Make sure that both use the same connection/datasource. Volker View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4226019#4226019 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4226019 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: Deploy Processdefinition via Ant
thanks for snippet. it now successfully deploys according to the script. [deploypar] deploying process from archive myprocess.par | [deploypar] created process definition my business trip request | [deploypar] deployed process my business trip request successfully | BUILD SUCCESSFUL | Total time: 7 seconds | But the processdef does not show in the jbpm console... any ideas? I am using 3.2.6 SP1. what version are u using? many thanks -lp View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4225323#4225323 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4225323 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: Deploy Processdefinition via Ant
Hi, here are the relevant targets from my ant file: target name=par depends=compile | zip destfile=${parfile} filesonly=true | zipfileset dir=${bindir} includes=**/*.class prefix=classes / | zipfileset dir=${srcdir} includes=**/${processdir}/gpd.xml fullpath=gpd.xml / | zipfileset dir=${srcdir} includes=**/${processdir}/processdefinition.xml fullpath=processdefinition.xml / | zipfileset dir=${srcdir} includes=**/${processdir}/processimage.jpg fullpath=processimage.jpg / | /zip | /target | | target name=deploy.par depends=par | taskdef name=deploypar classname=org.jbpm.ant.DeployProcessTask | classpath | pathelement path=${configdir} / | pathelement path=${bindir} / | fileset dir=${jbpm.root} includes=**/*.jar / | fileset dir=${libdir} includes=**/*.jar / | /classpath | /taskdef | deploypar process=${parfile} / | /target The variables: configdir: hibernate.cfg.xml | bindir: compiled classes | jbpm.root: jbpm installation directory | libdir: further jar dependencies | | | Regards, | Volker View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4225041#4225041 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4225041 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: Deploy Processdefinition via Ant
mike please post your ant script as i am suffering pain with my ant deploy script. i am using jbpm3.2.1Sp1 my problems are as follows 1. despite the docs there is *NO* cfg attribute on org.jbpm.ant.DeployProcessTask 2. processdefintion.xml *MUST* be included in the par *NOT* in classpath or else the deployer produces error please share ur ant deploy script. thanks -lp View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4225012#4225012 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4225012 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: Deploy Processdefinition via Ant
It's your DB driver: java.util.zip.ZipException: error in opening zip file View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4217251#4217251 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4217251 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: Deploy Processdefinition via Ant
Including the hibernate config and jbpm config in the processarchive is never needed. I have no clue what that solves for you since you do not mention that Most likely cause is that when deploying via ant, a different hibernate config is picked up then the one you think is picked up. One which includes a reference to jndi instead of the one with the explicit connection properties View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4215387#4215387 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4215387 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user