topic There is no getter for property named 'limitBefore' in 'class org.activiti.engine.impl.ProcessInstanceQueryImpl' in Alfresco Archive

There is no getter for property named 'limitBefore' in 'class org.activiti.engine.impl.ProcessInstanceQueryImpl'

joao_p_silva — Wed, 07 Aug 2013 15:40:33 GMT

When using a ProcessInstanceQuery‍ to list all process instances that match a given process definition key, and contain a certain variable value, i.e.:List<ProcessInstance> procs = processEngine.getRuntimeService() .createProcessInstanceQuery().processDefinitionKey("key") .variableValueEqual

Re: There is no getter for property named 'limitBefore' in 'class org.activiti.engine.impl.ProcessInstanceQueryImpl'

frederikherema1 — Thu, 08 Aug 2013 09:10:54 GMT

Those properties should be provided to myBatis (and the DbSqlSessionFactory), when the process-engine is initialized:

if(databaseType != null) {
          properties.put("limitBefore" , DbSqlSessionFactory.databaseSpecificLimitBeforeStatements.get(databaseType));
          properties.put("limitAfter" , DbSqlSessionFactory.databaseSpecificLimitAfterStatements.get(databaseType));
          properties.put("limitBetween" , DbSqlSessionFactory.databaseSpecificLimitBetweenStatements.get(databaseType));
          properties.put("limitOuterJoinBetween" , DbSqlSessionFactory.databaseOuterJoinLimitBetweenStatements.get(databaseType));
          properties.put("orderBy" , DbSqlSessionFactory.databaseSpecificOrderByStatements.get(databaseType));
          properties.put("limitBeforeNativeQuery" , ObjectUtils.toString(DbSqlSessionFactory.databaseSpecificLimitBeforeNativeQueryStatements.get(databaseType)));
        }

So it's due to the lack of those "global" properties that myBatis looks at the actual query-object to retrieve them.

Double-check your process-engine configuration and make sure the "databaseType" is supplied.

Re: There is no getter for property named 'limitBefore' in 'class org.activiti.engine.impl.ProcessInstanceQueryImpl'

kary — Tue, 20 Aug 2013 10:11:26 GMT

Hi I am new to activiti. While configuring process engine, I am facing the same problem. Could you help me with this issue.


Error querying database.  Cause: org.apache.ibatis.reflection.ReflectionException: There is no getter for property named 'limitBefore' in 'class org.activiti.engine.impl.db.ListQueryParameterObject'
### Cause: org.apache.ibatis.reflection.ReflectionException: There is no getter for property named 'limitBefore' in 'class org.activiti.engine.impl.db.ListQueryParameterObject'

My understanding is that the "databaseType" should be picked up based on the driver configuration in the datasource while loading the processEngineConfiguration.
Below is the process engine bean configuration.


<bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
    <property name="dataSource" ref="dataSource" />
    <property name="transactionManager" ref="transactionManager" />
    <property name="history" value="audit" />
    <property name="databaseSchemaUpdate" value="false" />
    <property name="jobExecutorActivate" value="true" />
    <property name="processDefinitionCacheLimit" value="10" />
    <property name="processEngineName" value="default"></property>
    <property name="customSessionFactories">
      <list>
        <bean class="com.uprr.bpm.rest.services.ldap.LDAPUserManagerFactory">
          <constructor-arg ref="ldapConnectionParams" />
        </bean>
        <bean class="com.uprr.bpm.rest.services.ldap.LDAPGroupManagerFactory">
          <constructor-arg ref="ldapConnectionParams" />
        </bean>
      </list>
    </property>
  </bean>

Re: There is no getter for property named 'limitBefore' in 'class org.activiti.engine.impl.ProcessInstanceQueryImpl'

trademak — Wed, 21 Aug 2013 06:54:12 GMT

Hi,

No, you have to explicitly set the databaseType. That's why you get this limitBefore error message.

Best regards,

Re: There is no getter for property named 'limitBefore' in 'class org.activiti.engine.impl.ProcessInstanceQueryImpl'

kary — Tue, 27 Aug 2013 07:42:35 GMT

I did not set the dabaseType but the problem got solved when we actually increased the database processes. So I wonder if we really need to set the databaseType?

Regards,
Kary