[Design of JBoss jBPM] - [sim] Configuration of Experiment
by camunda
Hi, I decided to use this forum also for the simulation features, I currently develop, so here we go with a question, hopefully somebody has an opinion on it, at least Tom ;-))
How to configure simulation experiments?
An experminet contains different informations (a bit simplified here):
- Which processes should be started after what time distribution
- How much resources I have per resource pool
- maybe shift calendar
- work times for tasks
- ...
Some of them can be included in the existing ProcessDefinition XML structure, maybe even all of them. But this has one big disadvantage: I can not maintain scenarios, which would be a very valuable feature, enabling the comparision of different staffing strategies for example.
So the question is, where to put these information: In an additional XML? In Java-classes? In the <process-definition> (with some nested "scenario" elements)?
A second thought must be considered here: I maybe need more than one process for my simulation experiment (because same people maybe work not only in order, but also in service tasks). Maybe this is not a MUST for the simulation environment, but I think a restriction to one process is not nice.
So I tend to allow to include the information directly in the ProcessDefinition elements, for the easy case, where no scenarios are required. So the user can play with simulation easily at the beginning.
More complex stuff and scenarios have to be configured in a special XML file. The data there "overwrites" the simulation data in the process definitions.
But I am nwondering, if maybe a complex scenario configuration can be build more easy in Java code directly? At least for the moment, this may change as soon (but here is a big: WHEN) there is GUI support available...
Thanks for any (even rough) thoughts on it...
Cheers
Bernd
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092052#4092052
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092052
18 years, 6 months
[Design of POJO Server] - MainDeployerImpl process managed deployment
by alesj
Just something I noticed when looking how to get a hold of runtime component's name in true OO fashion. :-)
Is this done on purpose - that we are skipping process on 2nd level context.
Since we do do getChildren on top contexts, and then immediately getChildren on those child contexts:
| public ManagedDeployment getManagedDeployment(String name) throws DeploymentException
| {
| DeploymentContext context = getDeploymentContext(name);
| if (context == null)
| throw new IllegalArgumentException("Context not found: " + name);
|
| Map<String, ManagedObject> rootMOs = getManagedObjects(context);
| ManagedDeployment root = mgtDeploymentCreator.build(context.getDeploymentUnit(), rootMOs, null);
| for (DeploymentContext childContext : context.getChildren())
| {
| processManagedDeployment(childContext, root);
| }
| return root;
| }
|
| protected void processManagedDeployment(DeploymentContext context, ManagedDeployment parent)
| throws DeploymentException
| {
| for (DeploymentContext childContext : context.getChildren())
| {
| DeploymentUnit childUnit = childContext.getDeploymentUnit();
| Map<String, ManagedObject> childMOs = getManagedObjects(childContext);
| ManagedDeployment childMD = mgtDeploymentCreator.build(childUnit, childMOs, parent);
| processManagedDeployment(childContext, childMD);
| }
| }
|
There is no lookup on processManagedDeployment context param.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092051#4092051
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092051
18 years, 6 months