[
https://issues.jboss.org/browse/AS7-4019?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-4019:
-----------------------------------
I'm not sure about the JPA part of this yet but looking at the second stack trace
[
here|https://community.jboss.org/message/721737#721737], it looks like
org.jboss.marshalling.reflect.ReflectiveCreator.create() is creating a new instance of the
target class which is different than what Java serialization happens to implement. My
quick look at [the serialization
specification|http://docs.oracle.com/javase/6/docs/platform/serialization...]
didn't find any requirements specified about whether transient fields are initialized
or not during deserialization.
Unless, I am missing something (in the Java language specification or serialization
specification), the handling of Java transient fields (during deserialization) is
implementation specific and should be documented, so users know what to expect.
Jboss Remoting and java transient fields.
------------------------------------------
Key: AS7-4019
URL:
https://issues.jboss.org/browse/AS7-4019
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.0.Final
Environment: Windows XP
Reporter: Sueleyman Vurucu
Assignee: Scott Marlow
Java transient field with default values restore the default value after deserialisation.
This behaviour is different from the old remoting and standard java serialisation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira