[
https://issues.apache.org/jira/browse/METAMODEL-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252161#comment-15252161
]
ASF GitHub Bot commented on METAMODEL-242:
------------------------------------------
GitHub user kaspersorensen opened a pull request:
https://github.com/apache/metamodel/pull/93
METAMODEL-242: Fixed
Fix for METAMODEL-242 which seems like a simple oversight.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kaspersorensen/metamodel METAMODEL-242
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/metamodel/pull/93.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #93
----
commit eb0cd5bd8f828c41ddb2ed0c713f600a3a893acf
Author: kaspersorensen <[email protected]>
Date: 2016-04-21T16:27:12Z
METAMODEL-242: Fixed
----
> Deserialization will yield the wrong replacement-class for legacy
> OperatorType class
> ------------------------------------------------------------------------------------
>
> Key: METAMODEL-242
> URL: https://issues.apache.org/jira/browse/METAMODEL-242
> Project: Apache MetaModel
> Issue Type: Bug
> Reporter: Kasper Sørensen
> Assignee: Kasper Sørensen
>
> LegacyDeserializationObjectInputStream seems to have a copy-paste error in
> it's interception of old/legacy enum OperatorType instances which is supposed
> to be replaced by the LegacyOperatorType enum. Instead it seems to try and
> deserialize it as a LegacyFunctionType which isn't gonna work at all.
> I'll be submitting a fix shortly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
