[JBoss Remoting] New message: "Trasporter Server/Client and clustering question"
by Gugo Martikyan
User development,
A new message was posted in the thread "Trasporter Server/Client and clustering question":
http://community.jboss.org/message/519923#519923
Author : Gugo Martikyan
Profile : http://community.jboss.org/people/gugo46
Message:
--------------------------------------------------------------
Hi all,
I read the remoting documentation, but it is still unclear to me if it is possible to lookup a specified list of URI's.
Can I specify a list of url's for remoting servers to the client?
Like
...TransporterClient.createTransporterClient("socket://server1:5400;socket://server2:5400", MyService, true);
or, More importantly, is lookup of transporters (multicast driven on server side) based on the targetClass or uri driven (like port)? My assumption is that it is targetClass driven, but I need confirmation.
Thanks.
Gugo
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519923#519923
16 years, 3 months
[jBPM] New message: "Exception Handling in node (v3.2)"
by Arnoud Wolfard
User development,
A new message was posted in the thread "Exception Handling in node (v3.2)":
http://community.jboss.org/message/519899#519899
Author : Arnoud Wolfard
Profile : http://community.jboss.org/people/awolfard
Message:
--------------------------------------------------------------
Hi all,
Playing around with some jbpm code and I have a question regarding exception handling in a node.
What I want is the following:
When an exception occurs in my actionhandler I want to startup a task so a user can correct the process(-step) manually and signal the process again.
I came with this:
Node actionhandlers all extend the BaseNodeHandler:
public abstract class BaseNodeHandler implements ActionHandler {
public void execute(ExecutionContext executionContext) throws Exception {
try {
String returnValue = this.doExecute(executionContext);
if (returnValue == null) {
executionContext.leaveNode();
} else {
executionContext.leaveNode(returnValue);
}
} catch (Exception e) {
// Start up another process with a task (async tasknode) to deal with this situation?
// After manual correction give signal to continue processing?
}
}
public abstract String doExecute(ExecutionContext executionContext) throws Exception;
}
When an exception occurs the node is not propagated (leaveNode is not called) and therefore the state of the process is persisted (right?)
. Then I want to start up another process which creates a task (async tasknode) so a user can make some corrections.
Is it okay to start another process in the exception block?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519899#519899
16 years, 3 months