finder throwing ArrayIndexOutOfBoundsException

[weliwarmer]

JBoss 3.2.0

I have a custom finder in a CMP Bean that is throwing a ArrayIndexOutOfBoundsException (see below for stack). Doe sanyone know why?

jaws.xml snip:

findByAttributeType
<![CDATA[attribute.attribute_type_id = attribute_type.id and attribute_type.type = {1}]]>



xdoclet snip
* @ejb.finder
* signature="java.util.Collection findByAttributeType(java.lang.String type)"
* unchecked="true"
* @jboss:finder-query name="findByAttributeType"
* query="attribute.attribute_type_id = attribute_type.id and attribute_type.type = {1}"

The query runs fine by hand through mysql console.

14:12:55,578 ERROR [JDBCFinderCommand] Failed to create finder results
java.lang.ArrayIndexOutOfBoundsException: 1
at org.jboss.ejb.plugins.jaws.jdbc.JDBCDefinedFinderCommand.setParameters(JDBCDefinedFinderCommand.java:271)
at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java:175)
at org.jboss.ejb.plugins.jaws.jdbc.JDBCFinderCommand.execute(JDBCFinderCommand.java:114)
at org.jboss.ejb.plugins.jaws.jdbc.JDBCFindEntitiesCommand.execute(JDBCFindEntitiesCommand.java:200)
at org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.findEntities(JAWSPersistenceManager.java:292)
at org.jboss.ejb.plugins.CMPPersistenceManager.findEntities(CMPPersistenceManager.java:324)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.findEntities(CachedConnectionInterceptor.java:323)

Thanks for you help,
Tim.

[petertje]

because the parameter index should be 0 instead of 1?

[weliwarmer]

Thanks, that fix SOME of the finders but others with custom finder like

upper(description) like upper({0}) or upper(key) like upper({0})

don't work because org.jboss.ejb.plugins.jaws.jdbc.JDBCDefinedFinderCommand gets confused when the same parameter is refered to more than once in the same statement.

JDBCDefinedFinderCommand counts the number of parameters by position, it does not take account of the parameter number.

Anyone know a way round this?

[weliwarmer]

Right got it....

In the actual deployment I had

upper(description) like upper({0}) or upper(_key) like upper{{0})

i.e. the last parameter has too many {{

Thanks again.