[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-3030) NullPointerException happens in versioning

Gail Badner (JIRA) noreply at atlassian.com
Tue Apr 27 17:25:34 EDT 2010


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

Gail Badner resolved HHH-3030.
------------------------------

      Assignee: Gail Badner
    Resolution: Rejected

This is expected behavior. If an entity is mapped as having a version property, then Hibernate assumes that existing entities will have a non-null version.

The database representation needs to be consistent with what is mapped.

Hibernate only allows unsaved entities to have a non-null version.

Please move further discussion to the user forum (https://forum.hibernate.org/).

Thanks,
Gail

> NullPointerException happens in versioning
> ------------------------------------------
>
>                 Key: HHH-3030
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.2.5
>         Environment: any
>            Reporter: John
>            Assignee: Gail Badner
>            Priority: Minor
>
> Here is the stack trace:
> java.lang.NullPointerException
> 	at org.hibernate.type.IntegerType.next(IntegerType.java:59)
> 	at org.hibernate.engine.Versioning.increment(Versioning.java:25)
> 	at org.hibernate.event.def.DefaultFlushEntityEventListener.getNextVersion(DefaultFlushEntityEventListener.java:358)
> 	at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:250)
> 	at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:121)
> 	at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196)
> 	at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76)
> 	at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35)
> 	at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969)
> 	at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114)
> 	at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
>         ......
> The code is:
> 	public Object next(Object current, SessionImplementor session) {
> 		return new Integer( ( (Integer) current ).intValue() + 1 );
> 	}
> Should there be a null checking for the object "current"?

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

        


More information about the hibernate-issues mailing list