[JBoss jBPM] - Re: jBPM 4 ProcessFactory/ProcessBuilder not found
by sterjev.marjan
package impl;
import org.jbpm.api.activity.ActivityBehaviour;
import org.jbpm.api.activity.ActivityExecution;
import org.jbpm.jpdl.internal.activity.StartActivity;
import org.jbpm.pvm.internal.builder.ProcessDefinitionBuilder;
import org.jbpm.pvm.internal.model.ProcessDefinitionImpl;
/**
* @author Marjan Sterjev
*
*/
public class Display implements ActivityBehaviour {
private static final long serialVersionUID = 1L;
String message;
public Display(String message) {
this.message = message;
}
public void execute(ActivityExecution execution) {
System.out.println(message);
}
public static void main(String[] args) throws Throwable {
ProcessDefinitionBuilder builder = ProcessDefinitionBuilder
.startProcess("Hello World");
builder.startActivity(new StartActivity()).initial().transition(
"hello display").endActivity();
builder.startActivity("hello display", new Display("Hello"))
.transition("world display").endActivity();
builder.startActivity("world display", new Display("World"))
.endActivity();
ProcessDefinitionImpl processDefinition = builder.endProcess();
processDefinition.startProcessInstance();
}
}
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240933#4240933
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240933
16 years, 9 months
[JBoss Messaging] - Re: Clustering differences versus JBoss MQ
by kennardconsulting
gaohoward,
Awesome. You are a legend. Look forward to hearing how you go. If it helps:
1. I made the changes described in the Wiki, then copied the 'all' folder to a new folder (I called it 'cluster2') and started a second instance of JBoss using 'run -c cluster2 -Djboss.service.binding.set=ports-01'. You will see the second instance fails to start because 'DefaultJMSProvider not bound'
2. DefaultJMSProvider is defined in jms-ds.xml. The Wiki instructs you to move this into deploy-hasingleton, which I believe is a mistake. In JBoss 4.2.3 the jms-ds.xml stays in the deploy folder (in the 'all' config)
3. You can try moving jms-ds.xml back to deploy, and things go better. However the MDBs no longer seem to 'wake up' upon bouncing a cluster node
Regards,
Richard.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240930#4240930
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240930
16 years, 9 months