<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Access process payload in ELResolver in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105517#M73788</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;That works, thank you.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Jul 2012 08:40:47 GMT</pubDate>
    <dc:creator>kaech</dc:creator>
    <dc:date>2012-07-23T08:40:47Z</dc:date>
    <item>
      <title>Access process payload in ELResolver</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105515#M73786</link>
      <description>Hi,I would like to implement an ELResolver whose behavior depends on the process payload.Is there a way to access the process variables from within an ELResolver like it is possible in a JavaDelegate?Thanks in advance.</description>
      <pubDate>Fri, 20 Jul 2012 15:55:39 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105515#M73786</guid>
      <dc:creator>kaech</dc:creator>
      <dc:date>2012-07-20T15:55:39Z</dc:date>
    </item>
    <item>
      <title>Re: Access process payload in ELResolver</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105516#M73787</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;You should extend the org.activiti.engine.impl.el.ExpressionManager and use your custom version on your ProcessEngineConfiguration (property "expressionManager").&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You have some methods on there to create a new ELResolver to use in an execution. The variable-scope is passed in (= execution, task, …), which yiou can get variables from to do whatever magic you want in your EL-resolver.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;CODE&gt;protected ELResolver createElResolver(VariableScope variableScope) {&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; CompositeELResolver elResolver = new CompositeELResolver();&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; elResolver.add(new VariableScopeElResolver(variableScope));&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; elResolver.add(new ArrayELResolver());&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; elResolver.add(new ListELResolver());&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; elResolver.add(new MapELResolver());&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; elResolver.add(new DynamicBeanPropertyELResolver(ItemInstance.class, "getFieldValue", "setFieldValue")); //TODO: needs verification&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; elResolver.add(new BeanELResolver());&lt;BR /&gt;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; // CUSTOM MAGIC EL-RESOLVER&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; elResolver.add(new MagicResolver(variableScrope));&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; return elResolver;&lt;BR /&gt;&amp;nbsp; }&lt;/CODE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jul 2012 06:46:01 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105516#M73787</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2012-07-23T06:46:01Z</dc:date>
    </item>
    <item>
      <title>Re: Access process payload in ELResolver</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105517#M73788</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;That works, thank you.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jul 2012 08:40:47 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105517#M73788</guid>
      <dc:creator>kaech</dc:creator>
      <dc:date>2012-07-23T08:40:47Z</dc:date>
    </item>
    <item>
      <title>Re: Access process payload in ELResolver</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105518#M73789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;First: Thanks for this SourceCode.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But I've an other Problem now. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;If I use a ServiceTask with an "activiti:expression=${exampleBean.exampleMethode(exampleVariable)" in my *.bpmn20.xml-file and use an own ExpressionManager with an own ELResolver to find my properties (the exambleVariable), my own ExpressionManager won't get the "Beans" from the ProcessEngineConfigurationImpl. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Is it possible to get the Beans, that where define in the ProcessEngineConfigurationImpl, to my own ExpressionManager?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Casten&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Sep 2014 08:14:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105518#M73789</guid>
      <dc:creator>casten2809</dc:creator>
      <dc:date>2014-09-22T08:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: Access process payload in ELResolver</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105519#M73790</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Casten,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;answer is yes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;To answer how, I should understand your implementation. But you can access beans from process engine configuration.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl#beans)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Refgards,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Sep 2014 06:24:44 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105519#M73790</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2014-09-23T06:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: Access process payload in ELResolver</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105520#M73791</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi martin.grofcik,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks for your answer.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;First I've tried your solution with the following statement:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;code&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;bean id="activiti.wop.processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration"&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; …&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; &amp;lt;property name="beans"&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;map&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;entry key="exampleBean" value-ref="exampleBean"&amp;gt;&amp;lt;/entry&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/map&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; &amp;lt;/property&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;…&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; &amp;lt;property name="expressionManager" ref="express"/&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;…&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/bean&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;bean name="express" class="de.example.bpmactiviti.impl.BpmExpressionManager"&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; &amp;lt;constructor-arg name="beans" ref="beans"/&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/bean&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;bean name="beans" factory-bean="activiti.wop.processEngineConfiguration" factory-method="getBeans"/&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/code&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But this solution doesn't work. Have I interpret your solution wrong? &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And what were the right solution.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I've find another solution:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;code&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;bean id="activiti.wop.processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration"&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;…&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp; &amp;lt;property name="expressionManager"&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;bean class="de.example.bpmactiviti.impl.BpmExpressionManager"&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;constructor-arg name="beans"&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;map&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;entry key="initializeControlExpert" value-ref="initializeControlExpert"&amp;gt;&amp;lt;/entry&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/map&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/constructor-arg&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/bean&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/property&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;…&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/bean&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;/code&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;But I think this isn't a nice solution.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Sep 2014 07:00:46 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105520#M73791</guid>
      <dc:creator>casten2809</dc:creator>
      <dc:date>2014-09-26T07:00:46Z</dc:date>
    </item>
    <item>
      <title>Re: Access process payload in ELResolver</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105521#M73792</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Casten,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;From BpmExpressionManager point of view both solutions are the same. The difference is how beans are initialized and given to the BpmExpressionManager. &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Did you get list of beans to BpmExpressionManager in the 1. solution (Why not?)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2014 06:40:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105521#M73792</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2014-09-29T06:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Access process payload in ELResolver</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105522#M73793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi martin.grofcik,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;No. I don't get some Beans for the BpmExpressionManager in the first solution. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As I have debbuged the source code I have seen, that as first the ExpressionManager will be set (org.activiti.spring.ProcessEngineFactoryBean) and after this the Beans are initialized (e.g. org.activiti.spring.SpringProcessEngineConfiguration).&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I can't find out why this happened.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Casten&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2014 06:11:52 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/access-process-payload-in-elresolver/m-p/105522#M73793</guid>
      <dc:creator>casten2809</dc:creator>
      <dc:date>2014-09-30T06:11:52Z</dc:date>
    </item>
  </channel>
</rss>

