[jboss-jira] [JBoss JIRA] Closed: (HIBERNATE-50) Embedded Objects get set to null if all its members are null
[
https://jira.jboss.org/jira/browse/HIBERNATE-50?page=com.atlassian.jira.p...
]
Steve Ebersole closed HIBERNATE-50.
-----------------------------------
Resolution: Won't Fix
Vladimir, you know if you are going to be vulgar the least you could do would be to
consult a dictionary. LOL
Again, as I stated nearly 2 years ago...
1) This is *not* the correct place to report issues with Hibernate. This is a JIRA for
tracking issues with integration between JBoss and Hibernate.
2) If this is soooo important to y'all, then produce a patch that corrects the
behavior and attach to the correct JIRA. This enhancement is very very very low on my
personal task list
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