EJB-QL compiler (parser) confused by "Order" abstract-schema
------------------------------------------------------------

         Key: JBAS-1665
         URL: http://jira.jboss.com/jira/browse/JBAS-1665
     Project: JBoss Application Server
        Type: Bug
  Components: CMP service  
    Versions:  JBossAS-4.0.2RC1    
 Environment: Intel, Linux 2.6
    Reporter: Mike Sowka


Follow this forum "monologue":
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872960

It seems that the JBoss EJB-QL parser/compiler gets confused by the use of 
"Order" as the abstract-schema. I would get the following error when trying 
query "SELECT COUNT(o) FROM Order o":
org.jboss.deployment.DeploymentException: Error compiling EJB-QL statement 
'SELECT COUNT(o) FROM Order o'; - nested throwable: 
(org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "Order" at line 1, 
column 22.

What I believe is happening is that JBoss mistankenly parses "Order" as the 
query keword ORDER. Initially I thought this was the fault of my query 
statement which I pulled out of the EJB2.1 Spec. I contacted the spec contact, 
and Linda DeMichiel replied to me noting that in fact "Order" should be OK for 
the abstract-schema and is only restriced in use as an identifier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to