0 Replies Latest reply on Aug 14, 2004 9:16 AM by Zarni Worgl

    Load groups working in 3.2.3 but strange behavior in 3.2.6

    Zarni Worgl Newbie

      I moved my ejb app to jboss 3.2.6. Now my load groups aren't working properly.

      This are the load groups for my entity.

       <load-groups>
       <load-group>
       <load-group-name>basic</load-group-name>
       <field-name>gln</field-name>
       <field-name>name</field-name>
       <field-name>address</field-name>
       <field-name>partyImage</field-name>
       </load-group>
       <load-group>
       <load-group-name>therest</load-group-name>
       <field-name>city</field-name>
       <field-name>countryIsocode</field-name>
       <field-name>email</field-name>
       <field-name>language</field-name>
       <field-name>postalCode</field-name>
       <field-name>telephoneNumber</field-name>
       <field-name>webSite</field-name>
       </load-group>
       </load-groups>
       <eager-load-group>basic</eager-load-group>
       <lazy-load-groups>
       <load-group-name>therest</load-group-name>
       </lazy-load-groups>
      


      When I executed the following query :
       <query>
       <query-method>
       <method-name>findAll</method-name>
       <method-params />
       </query-method>
       <jboss-ql>SELECT OBJECT(p) FROM Party AS p ORDER BY p.name</jboss-ql>
       <read-ahead>
       <strategy>on-find</strategy>
       <page-size>10</page-size>
       <eager-load-group>basic</eager-load-group>
       </read-ahead>
       </query>
      


      The fields values in the entity get mixed up, or they are simply gone.

      But... when I change eager-load-group to
      <eager-load-group>*</eager-load-group>
      

      then it work fine.

      It worked well in 3.2.3 and I don't know whats the problem, I guess
      my dep. descriptors are not compatible with 3.2.5, something must have changed.

      regards