EJB-QL Bug?

[sniper]

There is a limitation on abstract-schema-name length considering finder methods.

If you declare a schema name longer than 16 characters and then try to declare a finder on that schema(e.g. SELECT OBJECT(c) FROM thisIsMyLongNamedTable c WHERE c.lastName = ?1) you will get an ejbql parse error saying that there is no terminal field lastName even if there is.

[ccsdev]

I think I'm having the same problem, I just posted a new topic regarding that. When I deploy my jar it gives me the following exception:

org.jboss.deployment.DeploymentException: Error compiling EJB-QL
statement 'SELECT DISTINCT OBJECT(o) FROM DemoService o WHERE o.cost = ?1'; - n
ested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "o
.cost" at line 1, column 54.
Was expecting one of:
"NOT" ...
"(" ...
<COLLECTION_VALUED_PATH> ...
<STRING_VALUED_PATH> ...
"CONCAT" ...
"SUBSTRING" ...
<BOOLEAN_VALUED_PATH> ...
<DATETIME_VALUED_PATH> ...
<ENTITY_VALUED_PATH> ...
<IDENTIFICATION_VARIABLE> ...
<NUMERIC_VALUED_PATH> ...
"LENGTH" ...
"LOCATE" ...
"ABS" ...
"SQRT" ...
"+" ...
"-" ...
<INTEGER_LITERAL> ...
<FLOATING_POINT_LITERAL> ...
<NUMERIC_VALUED_PARAMETER> ...
)]

The thing is that if you notice, my bean name is under 16 characters in length.

Does anybody know what could be going on?