Obtaining null when trying to get a related entity mapped as @ManyToOne

[andre.botelho]

Hi everyone!

        I'm having a hard time doing a query in my audited entities on  jboss.envers-1.2.2.GA-hibernate-3.3.

        I have two entities, workers and teams. Each worker can be   associated  with just one team. In the entity worker I have a @ManyToOne    unidirectional relationship to the entity team, like this:

     @ManyToOne(fetch = FetchType.EAGER)
     @JoinColumn(name = "ID_TEAM", nullable = false)
     @ForeignKey(name = "RN_TEAM_FK1")
     @Cascade( { CascadeType.PERSIST, CascadeType.MERGE })
     private Team responsibleTeam;

       When I try to get the responsible team associated with the revision of worker, I'm obtaing null. Here is the code:

     AuditQuery query = getAuditReader().createQuery().forEntitiesAtRevision(Workers.class, revision);
     query.add(AuditEntity.id().eq(WorkerId));

     Worker workerRevision = (Worker) query.getSingleResult();

     String workerName = workerRevision.getName(); // This operation is returning the right name
     Team team = workerRevision.getResponsibleTeam(); // This operation is returning null 

       Is that the correct behavior?

       If I am doing something wrong, how could I retrieve the "responsibleTeam" associated with the revision of worker?

Thanks for your help.

[adamw]

If there was a team at that revision, then the query should find it.

Maybe you could try creating an Envers test case, to verify that this is indeed a bug?

Adam

[andre.botelho]

Adam,

   I finally understood what was going on. I wasn't paying attention on my DAOs mapping. When I execute "Worker workerRevision = (Worker) query.getSingleResult();" the query indeed find the responsibleTeam, however the object workerRevision was with his variables setted as null but with the right proxy on the trigger, throwing session closed exceptions when I tried to access these values in another layer. So I just added "Hibernate.initialize(regra.getResponsibleTeam)" and all worked well.

    This is not a bug but a innocent mistake that I made.Sorry for the trouble.

[adamw]

Great to hear that it's working

Adam