[
https://issues.apache.org/jira/browse/GEODE-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768418#comment-15768418
]
Bruce Schuchardt commented on GEODE-2232:
-----------------------------------------
Wouldn't changing the names of these exceptions cause the serialized form of
their subclasses to change? GemFireConfigException is probably fine but there
are a lot of subclasses of other "GemFire" exception classes like
GemFireException.
I have it on my to-do list to merge my backward-compatibility unit testing
framework to develop. We could test to see what happens using it.
> Rename GemFireConfigException
> -----------------------------
>
> Key: GEODE-2232
> URL: https://issues.apache.org/jira/browse/GEODE-2232
> Project: Geode
> Issue Type: Improvement
> Components: docs, general
> Reporter: Dor
> Assignee: Bruce Schuchardt
> Fix For: 1.1.0
>
>
> All GemFire*Exception classes should be refactor renamed to have Geode as a
> prefix instead.
> For example:
> GemFireConfigException - Should be GeodeConfigException.
> GemFireException Should be GeodeException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
