[
https://jira.jboss.org/jira/browse/HIBERNATE-50?page=com.atlassian.jira.p...
]
Vladimir Kovalyuk commented on HIBERNATE-50:
--------------------------------------------
I'm surprised with the fact that it hasn't been fixed within two+ years.
Could you please clarify what was the requirement because of which you implement so odd
"optimization"? I don't see any.
Having entity instantiated without an embedded mixin makes developer check any usage for
presence of embedded object. Was that requirement worth our haemorrhoids?
Please please fix this ASAP!
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