[
https://issues.apache.org/jira/browse/LANG-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472222
]
Joerg Schaible commented on LANG-317:
-------------------------------------
This has less to do with the JDK, but more with the compiler you're using. E.g.
if you have compiled the class with Eclipse (it uses *always* the internal
compiler and not the selected JDK's one) it will have a different
serialVersionUID generated that the same class from the Sun compiler from the
identical JDK. The only way to get them compatible is to define an own
serialVersionUID.
> Enum Serialization - not backwards compatible
> ---------------------------------------------
>
> Key: LANG-317
> URL: https://issues.apache.org/jira/browse/LANG-317
> Project: Commons Lang
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: JDK 1.5 -> JDK 1.4
> Reporter: U. Klinkmüller
> Priority: Critical
>
> In our distributed application we have to deal with different environments.
> The server runs in a JDK 1.5 environment while some clients runs with JDK
> 1.4. In this scenario we get an error when we try to transfer the result
> object via RMI. The error message is:
> Exception:BusinessDelegatorComp.login() - connection error ocurred during
> loginCORBA MARSHAL 0x4942f89a No; nested exception is:
> org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge :
> Mismatched serialization UIDs : Source (Rep.
> IDRMI:de.fraport.biaf.apm.user.UserRoleEnum:CBEF51ADA936FFFE:D100D6F29BD50386)
> = D100D6F29BD50386 whereas Target (Rep. ID
> RMI:de.fraport.biaf.apm.user.UserRoleEnum:CBEF51ADA936FFFE:D041682DA5693C42)
> = D041682DA5693C42 vmcid: IBM minor code: 89A completed: No
> The class causing this problem is derived from
> org.apache.commons.lang.enums.ValuedEnum. Aftre some recherches we found on
> http://people.apache.org/~bayard/ that there is a upcoming new release 2.3 of
> Commons-Lang. We saw that in this release a bug [LANG-286] has been fixed
> which seemed to be exactly our problem. We downloaded this version hopening
> that we can forget this problem. But unfortunately the problem still exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
