[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-6119) NullPointerException in AbstractPathImpl without source path

[Hardy Ferentschik (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-6119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hardy Ferentschik updated HHH-6119:
-----------------------------------

    Affects Version/s: 4.0.0.Alpha3
        Fix Version/s: 3.6.5
              Summary: NullPointerException in AbstractPathImpl without source path   (was: NullPointerException in AbstractPathImpl without source path)

> NullPointerException in AbstractPathImpl without source path 
> -------------------------------------------------------------
>
>                 Key: HHH-6119
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6119
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: entity-manager
>    Affects Versions: 3.6.3, 4.0.0.Alpha3
>            Reporter: Michael Rudolf
>            Assignee: Hardy Ferentschik
>             Fix For: 3.6.5, 4.0.0.Beta1
>
>
> Whenever an instance of org.hibernate.ejb.criteria.paths.AbstractPathImpl does not have a source path (e.g., a criteria query root), missing null checks cause NullPointerExceptions. This is the case, when the get(String) method is used to navigate to a child path and an invalid attribute name is given. In this case, an IllegalArgumentException should be thrown indicating that the attribute with the given name was not found. However, due to missing null checks a NullPointerException is provoked when constructing the IllegalArgumentException instance.

-- 
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