[
https://issues.apache.org/jira/browse/GEODE-6941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918275#comment-16918275
]
ASF subversion and git services commented on GEODE-6941:
--------------------------------------------------------
Commit b6e7b077f86b63ccbb52c6e383006531932cfef6 in geode's branch
refs/heads/develop from Jinmei Liao
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b6e7b07 ]
GEODE-6941: move xml configuration objects to core (#3978)
* GEODE-6941: move xml configuration objects to core
Co-authored-by: Darrel Schneider <dschnei...@pivotal.io>
* CacheElement and other xml configuration should only exists in core
* use AbstractConfiguration in geode-management
* keep all xml domain objects in the same package as before and keep
CacheElement an abstract class.
> commands/code in goede-core should use the auto-generated configuration
> objects
> -------------------------------------------------------------------------------
>
> Key: GEODE-6941
> URL: https://issues.apache.org/jira/browse/GEODE-6941
> Project: Geode
> Issue Type: Sub-task
> Components: management
> Reporter: Jinmei Liao
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> some gfsh commands have started using these configuration objects for xml
> persistence, and they are using the modified classes, we should move these
> modified convenience methods into some utility methods and make sure these
> classes are using the auto-generated xml domain objects as it is.
> 1. regenerate the jaxb objects into an internal package in geode-core
> 2. modify the gfsh commands in core to use these objects instead of the
> objects in geode-management
> 3. leave the geode-management objects intact for now.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
