Hello.
Deploying jbpm-console.war on a JBoss 4.0.4 GA is working succesfully, and I'm
able to navigate through the console pages without problem.
But when I try to deploy jbpm.ear instead, some problem that seem related with
JavaServer Faces arise. The related log is:
2006-10-06 10:12:52,142 I
I've been looking at the build.xml ear file and as far as I understand, the
hibernate.cfg.xml file is copied from the jbom-console.war that is uncompressed
to extract their configuration files
|
|
|
and:
|
|
|
|
|
Furthermore, t
anonymous wrote : did you specify the dialect correctly ? do you know there is
a different dialect for oracle 9 ?
I thought I was using the Oracle9 dialect, but it seems that, in some way, that
is not what JBoss is thinking, as I'm seeing the log:
2006-09-13 14:38:56,698 DEBUG [org.hibernate.c
Hello.
I'm trying to setup jBPM inside JBoss 4.0.4 GA. Once I've deployed the jbpm.ear
(from CVS) I tried to deploy a process from the Graphic Designer. I'm getting
an oracle exception while trying to identify older versions of the process
trying to be deployed. What could be the cause? The sele
Hello.
I'm interested into implementing a clustered capable workflow system, and
started reading the user tutorial of jBPM and also some of the source code to
see how the thing works.
I need to support concurrent execution for the actions associated with
parallel tokens into process instances
Hello again.
I think that I've found the problem. It's how the variable is initialized in
the ActioHandler:
if (!ci.hasVariable(varName, executionContext.getToken())) {
| ci.setVariable(varName, new Integer(0), executionContext.getToken());
| }
ContextInstance.setVariable(String name, Obj
Hello. I'm just starting with jBPM and doing some JUnits to test if I
understand how the thing works. I'm confused about how execution contexts and
variables are bound.
For example, I'm trying to setup a simple task with a fork node, the two
branches of the fork are implementing a loop with tw
In different words, what I'm looking for is the way to apply a pessimistic
locking approach here.
I was googling and found some not clear enough signs that pessimistic locking
is not supported in JPA entities. Is this true?
The approach I was trying to use:
AEntity a = manager.find(AEntity.c
Thanks for the answer and excuses for the delay into replaying again.
So, when is the transaction supposed to be commited? On exiting the MDB
onMessage() embedding the entity creation?
What I want to get using the EntityManager.lock() method is to avoid other MDBs
handling the INCR messages to
Hello. I'm trying to build an scenario with the following behaviour:
Two kind of messages can be feeded into a JMS queue:
-NEW. Messages that triggers the creation of a new entity (ejb3.test.AEntity).
-INCR. Messages that triggers the modification of a persistent property
of a given en
10 matches
Mail list logo
