Thanks for the reply. I went back to current=false, which is the way we were
doing it with v4.1 but still get the same result:
Caused by: org.springframework.beans.factory.BeanCreationException: Error
creating bean with name 'jbpmProcessDeployer' defined in class path resource
[context/core/sp
Continuing log file from previous post:
2009-12-11 09:36:46,094 TRACE (Log4jLog.java:72) - beginning
StandardTransaction[80814]
| 2009-12-11 09:36:46,094 TRACE (Log4jLog.java:72) - found
org.jbpm.pvm.internal.session.RepositorySession in transaction
| 2009-12-11 09:36:46,095 TRACE (Log4jLog.j
We never really solved this. As best I can tell, trying to get tasks for an
execution or track what is going on by execution kind of goes against the
paradigm of jbpm. Instead, we created assignment handlers etc. that assigned
the tasks at the time they are created, then created methods like
In the previous post I pasted in an old jbpm.cfg.xml Here is the actual
current one:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks again for the reply. This is going to be a useful thread for others
someday, hopefully.
OK, the same problem still remains with Unknown Entity: PropertyImpl
Here are the relevant configuration files as they currently exist:
|
|
|
|
|
|
|
|
|
Santanu,
Thanks much for your continued support on this. I will not have time to
thoroughly investigate your latest suggestions since I am traveling today, but
I will do so over the weekend. I quick try of everything did not yet yield
positive results.
Putting this
|
|
We are embedding jbpm in our application and this error occurs when we try to
run the jUnit tests. I checked the libraries in my repository and looked for
the mapping, and it exists in the jbpm.repository.hbm.xml which is in turn
referenced from jbpm.hibernate.cfg.xml in our classpath.
Beca
Sooner or later I'll get this up. Thanks again for the help. Getting a new
exception now:
| org.hibernate.MappingException: Unknown entity:
org.jbpm.pvm.internal.id.PropertyImpl
| at
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiation
Thanks again for the suggestion. Each time I get a little further.
Now my config looks like this:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks for the reply. After changing the configuration as you suggest, I now
get the following stack trace:
org.jbpm.api.JbpmException: couldn't acquire block of ids
| at
org.jbpm.pvm.internal.id.DatabaseDbidGenerator.getNextId(DatabaseDbidGenerator.java:65)
| at
org.jbpm.pvm.intern
After updating to the 4.2 libraries, we began getting an NPE, the root cause of
which is that the userCommandService in ProcessEngineImpl is not getting
initialized. I tried to simplify the configuration as much as possible but
still get the error.
The error is
Caused by: java.lang.NullPointe
I get the same thing trying to run a ProcessDefinitionQuery:
| org.jbpm.jpdl.internal.model.JpdlProcessDefinition cannot be cast to
java.util.List
| at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:133
Yep, that is exactly what I am doing, and I swear it does not work. Possibly
there is something strange caused by the fact that we are using HSQLDB under
the test suite, but we have been using that for years on our project.
View the original post :
http://www.jboss.org/index.html?module=bb&
I've tried everything I can think of to query tasks by ProcessInstanceId but no
matter what, if you put a ProcessInstanceId on a TaskQuery, you get back zero
results. The test below runs fine until the last line, when the assertion
fails. I have tried substituting different ids in the query, i
14 matches
Mail list logo
