Re: EJB-QL & porting from WLS 7.0 to WLS 8.1 - Weblogic

This is a discussion on Re: EJB-QL & porting from WLS 7.0 to WLS 8.1 - Weblogic ; "Sri Lakhanigam" wrote: > > >SELECT OBJECT(proj) FROM UserProjectRole a, IN(a.role) rl, IN(a.project) >proj >WHERE a.user = ?1 AND rl.globalYn = 'N' AND proj.templateYn = 'N' AND >a.objectStatus >= 'A' AND rl.objectStatus = 'A' AND proj.objectStatus = 'A' > >EJB ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Re: EJB-QL & porting from WLS 7.0 to WLS 8.1

  1. Re: EJB-QL & porting from WLS 7.0 to WLS 8.1


    "Sri Lakhanigam" wrote:

    >
    >

    >SELECT OBJECT(proj) FROM UserProjectRole a, IN(a.role) rl, IN(a.project)
    >proj
    >WHERE a.user = ?1 AND rl.globalYn = 'N' AND proj.templateYn = 'N' AND
    >a.objectStatus
    >= 'A' AND rl.objectStatus = 'A' AND proj.objectStatus = 'A'
    >
    >EJB QL compilation encountered error: [EJB:013080] Problem, the path
    >expression/Identifier
    >'proj' starts with an identifier: 'proj'. The identifier 'proj', which
    >can be
    >either a range variable identifier or a collection member identifier,
    >is required
    >to be declared in the FROM clause of its query or in the FROM clause
    >of a parent
    >query. 'proj' is not defined in the FROM clause of either its query or
    >in any
    >parent query.
    >

    >
    >Has anyone come across a solution for this ?
    >
    >TIA
    >
    >Sri
    >


    Hi

    This was an unfortunate bug in which the OBJECT() operator would not accept a
    collection member variable as an argument ('proj' in this case).
    This is our bug # CR107447 and has been fixed in WLS 8.1 SP02.

    -thorick

  2. Re: EJB-QL & porting from WLS 7.0 to WLS 8.1


    Hi,

    I can't answer delivery schedule Qs (because I don't know). I'd have to refer
    you to your tech support representative...

    -thorick



  3. RE: Re: EJB-QL & porting from WLS 7.0 to WLS 8.1

    is there any available patch to SP1 that fixes this bug? - since we cannot upgrade to SP2.

  4. RE: Re: EJB-QL & porting from WLS 7.0 to WLS 8.1


    What bug are you referring to ?

    In any event, I would contact technical support on this. They're up on availability
    of patches.

    -thorick




+ Reply to Thread