-
1. Re: JBoss doesn't recognise jpdl file
mmusaji Aug 28, 2009 3:41 AM (in response to mmusaji)How does everyone else deploy their workflow on to JBoss?
-
2. Re: JBoss doesn't recognise jpdl file
kukeltje Aug 28, 2009 5:22 AM (in response to mmusaji)in 4? I use the ant task. Some use the jboss deployer but the file has to be a .bar!
-
3. Re: JBoss doesn't recognise jpdl file
mmusaji Aug 28, 2009 5:30 AM (in response to mmusaji)Yeah I'm using JBPM4 and Jboss 5.0.0.GA.
When using the ant task I get error saying that the resource for jbpm.cfg.xml can't be found... it's in my classpath. So I'm just using Eclipse to export my jpdl.xml and classes to a zip (.bar doesn't work either).
I was using Jboss 5.0.1 before so I got clean version of 5.0.0.GA and now I get this error:*** CONTEXTS IN ERROR: Name -> Error org.jbpm:service=ProcessEngine -> org.xml.sax.SAXParseException: Attribute name "idle-max" associate d with an element type "job-executor" must be followed by the ' = ' character. at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:665 ) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Scheduled ThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Schedule dThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadP oolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)
I know its seems self-explanatory but I've quadtruple checked the jobexecutor file and it definately has the "=" and is valid xml! -
4. Re: JBoss doesn't recognise jpdl file
kukeltje Aug 28, 2009 5:54 AM (in response to mmusaji)Can it be there is another version somewhere?
-
5. Re: JBoss doesn't recognise jpdl file
mmusaji Aug 28, 2009 6:39 AM (in response to mmusaji)I've done a search and I cannot work out where it is picking this duff file from. Baffled.
Anyhow, I think I should concentrate on getting it deployed using ant as this is the way it should be done I feel. I keep getting this "resource jbpm.cfg.xml does not exist" error.
I think I've messed up my build.xml and classpath entries! Thanks for your help again though. -
6. Re: JBoss doesn't recognise jpdl file
kukeltje Aug 28, 2009 7:27 AM (in response to mmusaji)look at the build.xml file in the examples dir. That one is correct.
-
7. Re: JBoss doesn't recognise jpdl file
mmusaji Aug 28, 2009 7:45 AM (in response to mmusaji)Thanks Ronald. I did and got as far as:
xml validation error: cvc-complex-type.3.2.2: Attribute 'exp' is not allowed to appear in element 'custom'. [line=8 column=116 ]: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'exp' is not allowed to appear in element 'custom'. This works in Eclipse and doesn't complain about the "exp" attribute.
-
8. Re: JBoss doesn't recognise jpdl file
mmusaji Sep 1, 2009 7:19 AM (in response to mmusaji)The problem was in the jbpm.jar. The job.jobexecutor.cfg.xml file was missing the "=". I'm not 100% sure if this was due to me messing around with the build file or not.
JBoss still does nothing when I put the .bar file in deploy folder. It only contains my one workflow but the .jar contains all the classes used by the workflow. Is this correct?