anonymous wrote : *ping kukeltje*

64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=1 
ttl=116 time=1h20m10s
64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=2 
ttl=116 time=1h20m11s
64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=3 
ttl=116 time=1h20m12s
64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=4 
ttl=116 time=1h20m13s
64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=5 
ttl=116 time=1h20m14s
64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=6 
ttl=116 time=1h20m15s
64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=7 
ttl=116 time=1h20m16s
64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=8 
ttl=116 time=1h20m17s
64 bytes from kukeltje.lombox.customer.bit.nl (87.251.48.65): icmp_seq=9 
ttl=116 time=1h20m18s

"sebastian.s" wrote : 
  | I was reading the section about java activities and process variables in 
the userguide and wondering about some things.
  | 
  | In a java or a custom activity I could use
  | Object getVariable(String key);
  | to retrieve the values of process variables and then I could go use them as 
arguments for method calls.
  | 
First of all I'm not sure you can get to the executioncontext in the java task. 
You can in the custom tastk/node

"sebastian.s" wrote : 
  | But that means that if I changed the names of the process variables I would 
need to change the implementation of the java or custom activity, too. So 
wouldn't it be more convient to be able to specifiy process variables in the 
process definition which would be passed as arguments? So in case the process 
variable names changed just the process definition would need need changes but 
the java class wouldn't need to be touched?
  | 
  | I was also wondering why you can specify the method name for a java 
activity in the GPD but not the number of arguments.
  | 
  | 
For the java task you can pass arguments and use expressions for the value of 
the arguments. These can afaik be process variable names as well, so that 
solves one problem. The varying number of arguments is afaik dealt with by jBPM 
since it uses reflection to find the correct method signature. Not 100% 
completely sure though.

What you can also to in the java task is set member fields, put a list, xml 
document or whatever in there from the processdefinition and parse/use that in 
your java class. It's kind of what you mentioned in the dev forum when we 
talked about schema extensions. 

http://docs.jboss.com/jbpm/v4/userguide/html_single/#java

I was under the impression that something like the field thing for java tasks 
was possible as well for custom nodes, but that might be something left in my 
brain from jBPM 3 (or it might just be wishful thinking) as I do not seem to be 
able to find anything.

"sebastian.s" wrote : 
  | 
  | If I got it wrong I'd be happy for some clarifying words. If not this seems 
to turn out to be a discussion for the dev forum, right?
  | 

Regarding passing params to the custom node, yes.

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259739#4259739

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259739
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user

Reply via email to