[jbpm-dev] [Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

[cvl]

"alex.guizar at jboss.com" wrote : Won't caching make expression evaluation in delegation properties unfeasible?
  | 
  | <delegation class="org.example.Taco">
  |   |   <sauce>${actor.sauce.preference}</sauce>
  |   | </delegation>
  | 
  | If the above is not a requirement (I have wished for it more than once, and not just me, see JBPM-1752) then we can have a single object per process definition. Otherwise we need a pool.

Well, how we solved this, is that we added the layer for all handlers, which injects the properties:


  | <action class="com.xxx.jbpm.proxy.JbpmHandlerProxy"> 
  | 			<handlerName>myHandler</handlerName>
  | 			<propertyMap key-type='java.lang.String' value-type='java.lang.String'>
  | 			   	<entry><key>myProperty</key><value>#{myVar}</value></entry>
  | 			  	<entry><key>myProperty2</key><value>#{myVar2}</value></entry>
  | 			</propertyMap>
  | 		</action>
		
Not too nice, but usable.

cvl

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

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211622