Closed GoogleCodeExporter closed 9 years ago
Allow custom attributes to specified on externals in process definitions. <process-definition name="Graph I"> <node name="A"/> </process-definition> <process-definition name="Graph II"> <node name="B"> <arc external="G1" to="A"/> </node> <external name="G1" processDefinition="Graph I"> <custom> <foo>bar</foo> <hello>world</hello> </custom> </external> </process-definition> <process-definition name="Graph III"> <node name="C"> <arc external="G2" to="B"/> </node> <external name="G2" processDefinition="Graph II"> <custom> <foo>baz</foo> </custom> </external> </process-definition> If you get node A from graph III, you can observe the following: Node nodeA = ...; nodeA.getExternalEnv().getAttribute( "foo" ) // returns "baz" nodeA.getExternalEnv().getAttribute( "hello" ) // returns "world" nodeA.getExternal().getEnv().getAttribute( "foo" ) // returns "baz" nodeA.getExternal().getEnv().getAttribute( "hello" ) // returns null nodeA.getOriginatingExternalNode().getExternal().getEnv().getAttribute( "foo" ) // returns "bar" nodeA.getOriginatingExternalNode().getExternal().getEnv().getAttribute( "hello" ) // returns "world"
Original issue reported on code.google.com by plor...@gmail.com on 12 Jul 2009 at 2:37
plor...@gmail.com
Original comment by plor...@gmail.com on 29 Apr 2010 at 3:40
Released with version 1.0.0
Original comment by plor...@gmail.com on 29 Apr 2010 at 3:53
Original issue reported on code.google.com by
plor...@gmail.com
on 12 Jul 2009 at 2:37