This week's book giveaway is in the Design forum.
We're giving away four copies of Design for the Mind and have Victor S. Yocco on-line!
See this thread for details.
Win a copy of Design for the Mind this week in the Design forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

EJB_QL identification var problem

 
Binoj Viswanathan
Ranch Hand
Posts: 85
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
_____________________________________
EJB_QL identification variable problem
_____________________________________

hi,
As per ejb2.0 spec identification variables in EJB-QL r case insensitive. But ven i used following in ejb-jar.xml with weblogic8.1
***********
<ejb-ql><![CDATA[SELECT OBJECT(o) FROM DepartmentBean O]]></ejb-ql>
****************

i got follwing exc..n while deploying the jar file
&&&&&&&&&&&&&&&
SELECT OBJECT( =>> o <<= ) FROM DepartmentBean O

EJB QL compilation encountered error: [EJB:013057]
Problem, in EJB QL the argument of OBJECT(o) in SELECT OBJECT(o) must be either a range variable ide
ntifier or a collection member identifier, either of which are defined in the query FROM clause as i
n 'SELECT OBJECT(e) FROM EmployeeBean AS e' or 'SELECT OBJECT(f) FROM EmployeeBean AS e, IN(e.friend
s)f'. 'o' is neither a range variable nor a collection member identifier.

Action, review the EJB QL query and correct the SELECT clause.
&&&&&&&&&&&&&&&


cn anyone explain me reazon for this?
thanx
Binoj V

PS:Weblogic8.1 implements EJB2.1.
Has this restriction on the identification variables removed in 2.1?
 
Keerthi P
Ranch Hand
Posts: 203
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
EJB 2.1 is backward compatible with EJB 2.0. Could be a bug in Weblogic 8.1 ?
 
Nathaniel Stoddard
Ranch Hand
Posts: 1258
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Whereas most servers are backwards compatible to some extent, most will take the version of the DTD or your DD as an indicator of which version to treat it as. So, I would say, make sure you are deploying your app as 2.0 even though you're deploying into a server that does 2.1 and backwards 2.0. Make sense?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic