[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1714) Session.get() behavior

[Max R. A. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1714?page=comments#action_22973 ] 

Max Rydahl Andersen commented on HHH-1714:
------------------------------------------

yeah I know it wont *always* do a hit, but now I just don't see the big need for having the operation in the first place.

so now we just need to update the javadoc + the ejb3 spec to reflect this possible exception (at least to be friendly to the users ;)

> Session.get() behavior
> ----------------------
>
>          Key: HHH-1714
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1714
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Reporter: Steve Ebersole
>     Assignee: Steve Ebersole
>      Fix For: 3.2.1

>
>
> The behavior of Session.get() should be as follows:
> 1) if the entity to get is already associated with the session:
> a) as a proxy, return the proxy making sure it gets initialized (potentially resulting in a ONFE)
> b) as a naked entity, return that entity
> 2) if the entity to get is not already associated with the session, attempt to load it either returning null if not found or the "naked" loaded entity
> Currently (1.a) is messed up in that the proxy is returned but not forced to initialize

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira