[jboss-jira] [JBoss JIRA] Commented: (HIBERNATE-50) Embedded Objects get set to null if all its members are null
Vladimir Kovalyuk (JIRA)
jira-events at lists.jboss.org
Thu Jan 22 11:18:47 EST 2009
[ https://jira.jboss.org/jira/browse/HIBERNATE-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449238#action_12449238 ]
Vladimir Kovalyuk commented on HIBERNATE-50:
--------------------------------------------
Not, didn't have intentions to be vulgar. Sorry for posting here - I didn't realize that Hibernate has its own jira. Trying to find the appropriate issue there.
> Embedded Objects get set to null if all its members are null
> ------------------------------------------------------------
>
> Key: HIBERNATE-50
> URL: https://jira.jboss.org/jira/browse/HIBERNATE-50
> Project: Hibernate
> Issue Type: Bug
> Environment: WinXP SP2, JBoss 4.0.4 GA as well as JBoss 4.0.5 GA, installation profile ejb3
> Reporter: milan w?lke
> Assignee: Steve Ebersole
>
> When having an embedded object only containing members of non-simple-types (e.g. String) and fetching it with the entity manager the following happens:
> If all columns, the embedded objects values are based on, are null the embedded object itself is set to null even if a non-arg-constructor set it to a non-null value before. A valid workaround is to include a member of a simple-type (e.g. int) in the embedded object. Doing this not all the values can be set to null, which results in not setting the embedded object itself to null, too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list