1 Reply Latest reply on Mar 11, 2003 3:27 PM by Evil Clown Chuck

    jdbc parser error

    Guillaume Newbie

      Hello and sorry for my bad english in this message, I don't speak this langage very well ;).

      I want to deploy an application which contains CMP
      EJBs with finders and no matter what I do I've the
      same error :

      ==>
      Depends On Me: org.jboss.deployment.DeploymentException: Error compiling ejbql; - nested throwable: (org.jboss.ejb.plugins.cmp.ejbql.ParseException: Encountered "2" at line 4, column 43.
      Was expecting one of:
      "ABS" ...
      "LENGTH" ...
      "LOCATE" ...
      "SQRT" ...
      "(" ...
      "+" ...
      "-" ...
      <INTEGER_LITERAL> ...
      <FLOATING_POINT_LITERAL> ...
      <NUMERIC_VALUED_PARAMETER> ...
      <NUMERIC_VALUED_PATH> ...
      )]
      <==

      In spite of that my request seems good in my ejb-jar.xml
      deployment descriptor file :

      ==>
      (...)

      <query-method>
      <method-name>findByOrganization</method-name>
      <method-params>
      <method-param>java.lang.String</method-param>
      <method-param>java.lang.String</method-param>
      </method-params>
      </query-method>
      <ejb-ql><![CDATA[
      SELECT OBJECT(j)
      FROM JBossUser j
      WHERE j.portalID = ?1
      AND j.organizationID = ?2
      ]]></ejb-ql>

      (...)
      <==

      I've tested also to put my request into the jbosscmp-jdbc.xml file between some <jboss-ql> marks but it seems conflicts with the ejb-jar declaration, and when my <ejb-ql> (in ejb-jar.xml file) is empty, my ejb-jar dtd is not respected. The other requests are correctly deployed but not this one and I don't know what can be the reason of this mistake.

      Thanks for your help if you have some ideas ;).

        • 1. Re: jdbc parser error
          Evil Clown Chuck Newbie

          I had a very similar error, which was caused by invalid SQL within an <ejb-ql> statement. However, it occurred somewhere else in the ejb-jar.xml file, *not* in the class that reported the error in the JBoss log.

          You might want to review every <ejb-ql> statement in your entire ejb-jar.xml file, and remove any invalid syntax that appears anywhere. This solved my problem.