Hello Koen

Thanks for replying about the jpdl alpha3 issues.

1. With respect to the presence of the jpeg (for monitoring),
I have to make sure that the jpeg is being included in the
deploy (of course) and what I had found is that unless I
carefully "clean" the eclipse project, there was (only sometimes)
some issue with this. So this is no longer an issue.

2. I will take your advice and try the jpdl alpha4. Which brings me
to the current issue. I am running jpdl alpha3 in the
jbpm-starters-kit-3.1.4 because I could not get the following
signalling servlet to work with the jbpm-jpdl-suite-3.2.GA release.

I am including the relevant code below. I looked at the 3.2.GA
jbpm runtime lib javadocs and see nothing particularly obvious
that would indicate that the code (which works fine in 3.1.4) is no
longer compliant with 3.2.GA.

 JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance();
 JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
 ProcessInstance processInstance = null;
 try {
 processInstance = jbpmContext.loadProcessInstance(processInstanceId);
 etc., etc., ...

Hello Keon

So I followed your suggestion, and am using
the jpdl-3.1.0.alpha4. I am using this with
the 3.1.4 runtime but everything seems to be
working.

I have an actionHandler question, for which I have
not found a documentation answer:

Question: In the actionHanderl Properties
dialog, is there a Config Type Field setter
dialog for setting "Fields" (which then are
represented in the processdefinition.xml with
something like the following:

<action class="org.test.MyAction">
 <city>Atlanta</city>
 <rounds>5</rounds>
</action>

Hello Koen and jBPM community

OK, so I answered my own question about
the delegation actionHandler Config-type Field
and getting it to prompt for field values in the
designer action properties dialog. The solution
was (after adding an appropriate instance variable
into the particular actionHandler in question) to
go into the Properties dialog for the action and
to place the cursor after the name of the
actionHandler class and to press "enter" on the
keyboard. This then (evidently) causes the
designer to re-evaluate the actionHandler class
for any code changes and then it recognizes the
presence of a new instance variable.

Maurice Yarrow
SplashNote Systems
Santa Clara, California