Alex,
I've tested it with jBPM3 trunk: the bug is gone :-)
(there is however another bug (task list was null), but I'm sure it was because
I'm on trunk).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165310#4165310
Reply to the post :
http://www.jboss.co
Pete Muir of the Seam team also found this problem in the SOA branch.
anonymous wrote :
http://fisheye.jboss.com/browse/JBPM/jbpm.3/jpdl/jar/src/main/java/org/jbpm/JbpmConfiguration.java?r=1.8.2.1
| For Seam pageflows we don't require users to have a jbpm.cfg.xml and, with
this change, jbpm
Damn typo. Url should be http://jira.jboss.com/jira/browse/JBPM-1376
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164328#4164328
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164328
__
JIRA issue added: [url]http://jira.jboss.com/jira/browse/JBPM-1376]/url].
Don't hesitate if you really want to fix it ;-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164326#4164326
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
it surely is a regression in behaviour. Might be that the default.cfg.xml is
not looked up correctly or that passing a name of your own config file does not
work. Either way, file a jira issue. We can always add details later there.
View the original post :
http://www.jboss.com/index.html?modul
Ronald, thanks for taking a look! These are my remarks:
- Including jbpm.cfg.xml indeed fixed the test (I tried it before posting, I
speak stacktrace ;-). The problem however is that the configuration file in my
application isn't named 'jbpm.cfg.xml' ...
- Strangely I thought that it was bsh re
oh.. and there should have been a ;-) after the first line in my previous post
:-P
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164102#4164102
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164102
___
heck... just remembered I still had a clean 3.2.3 test project. It fails
also...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164100#4164100
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164100
I tried your test with the 3.2.3 jar from the distribution on sf (not the
suite). It runs fine then. So it might be something in the jbpm.cfg.xml that
causes this or some other lib that is involved (my own set, not the full 3.2.3
set)
I'll try with a complete jbpm 3.2.3 set of libs tonight
Vie
