Hi Ravi,
I have solved the problem, but it wasn't how I expected. The main culprit in
this is Hibernate.
My first issue was trying to get Hibernate to recognize the mySQL JDBC driver.
I put that thing in nearly every possible location it could go within my JBoss
environment, with no luck.
Forgot to mention in the above post...
The configured mySQL datasource seems to be deployed correctly by JBoss during
startup, and has valid JMX entries in the JMX console.
This is the most perplexing part -- why can JBoss find the driver class, but my
jBPM deployment cannot?
View the original
I am seeing something similar to lappi's issue. I've also perused a number of
other topics re: DB driver issues, but none directly correspond to my problem,
or were able to help me fix it.
I've deployed jBPM 3.0.2 to JBoss 4.0.3 SP1. I'm testing a process definition
using a simple servlet in
I agree w/ lawless. You can't force a task node to have at least one
transition be available, as this does not translate well to the real world.
It would be up to the programmer to ensure that such a possibility is handled
correctly -- lawless mentioned periodic polling of the transition condit
Good day,
Wanted to know how synchronized the XSD and the API are (version 3.0). For
example, within the API for the "Join" node, you are offered the ability to set
the join properties to establish "discriminator" or "nOfm" behavior. However,
I don't see attributes for these within the XSD "j
