Ok. I had to solve this now, as I ran into other classloading problems on the
way.
The cause of this problem is a simple jar version conflict. The JBoss which is
included in the jBPM Suite (3.2.1) comes with a javassist.jar which is too
old to work with JSF RI 1.2.
That is probably why a ja
Sorry, I overlooked your posting.
"kukeltje" wrote : persistencecontext: the default for the unit tests. Not sure
what it is.
Probably hsql in-memory?
anonymous wrote : Add my test above to the VariableInstanceDbTest.java.
Yes. That works - which makes things even more unclear. Tried it wit
Hi Ronald,
thanks for working on that.
I tried on JBoss 4.0.4, which comes with myfaces (1.1) in tomcat5.5.sar. I
removed the jars, but that didn't work either.
The only chance that this is "regular" class loading problem is that there are
some faces-jars somewhere else in jboss ("find" didn't
Hi Ronald,
I just found some time to try it out.
"kukeltje" wrote :
| I'm curious though what would happen if you changed
|
| System.out.println("first.node-enter: directly after setting variable:
instanceof selectitem:"+(test.get(0) instanceof javax.faces.model.SelectItem));
|
|
Hi Ronald,
"kukeltje" wrote :
| hmmm... I read your post and do not see where jBPM is involved in a way
that it is causing this problem. Everything you describe is JSF, the only thing
is that you put selectItems in a variable, but that is just like you would do
in in a bean.
|
I am pret
"kukeltje" wrote : please what is so difficult about my previous post
this is JSF stuff, not jBPM. So please ask in the correct forum and learn
JSF
I wouldn't say this is totally wrong, but it is pretty far away from the truth,
as jBPM is probably very well involved in this problem
"dajevu" wrote :
| I'm experiencing a similar problem -- but mine is:
org.jbpm.context.exe.VariableContainer; local class incompatible.
|
| Would you mind sharing what changes you made in Eclipse? I copied over the
jbpm-jpdl.jar file from the exploded EAR file under jboss AS, but I still
Mea culpa...that was a personal eclipse specific problem and was not
specifically jbpm-related.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073334#4073334
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4073334
_
Hello,
I am encountering problems accessing jbpm 3.2.1. on jboss, and I don't
understand what is going wrong.
I am using the following sample code:
| Properties props = new Properties();
| props.setProperty(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
| p
"dleerob" wrote :
|
| | activation.jar
| | antlr-2.7.6.jar
| | asm.jar
| | bsh.jar
| | cglib.jar
| | commons-collections.jar
| | commons-logging.jar
| | dom4j.jar
| | hibernate.cfg.xml
| | hibernate3.jar
| | hsqldb.jar
| | jboss-backport-concurren
"kukeltje" wrote : the latter, see my previous posts. If you take that into
account isn't the task-assign event very clear? ;-)
Yes, indeed. VERY clear ;-)
I am also in favour of the idea that the engine should have a seperate event
for group-assignment. However, the differentiation in "task-as
Sorry, didn't get it: What exactly is the bug? That the task-assign-event is
fired in case 1, or that it is not fired in case 2?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069815#4069815
Reply to the post :
http://www.jboss.com/index.html?module=bb&op
"cpob" wrote :
| If you do, I'll vote on it, because I support that something needs to be
done about it.
I would agree. The semantics of "task-assign" are not clear from my point of
view.
Case 1:
|
|
|
|
|
Case 2:
|
|
|
|
Both cases specify gro
Hello,
I think there might be a bug in the new facelets-based console which is
included in jpdl-3.2.1-suite.
After a fresh install and starting the already deployed sample "websale"-
process I see some weired behaviour:
Clicking "More Info Needed" in the "Evaluate Web Order"-Form does not take
14 matches
Mail list logo
