[
https://issues.apache.org/jira/browse/GEODE-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16402025#comment-16402025
]
ASF subversion and git services commented on GEODE-4830:
--------------------------------------------------------
Commit 7f8eedcc5f495e6da2fb5e01d9855929d6df49fa in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7f8eedc ]
GEODE-4830: use CacheConfig to access the jndi list in ListJNDIBindingCommand
* updated the CacheConfig to hold only one JNDIBindingsType instead of a list
* make sure xml created by those POJOs can be used to start a server
* the service will keep a list of bind classes for clearer xml generation.
* the service will keep a reference to the marshaer/unmarsher for faster
operation
> Modify list jndi-binding gfsh command
> --------------------------------------
>
> Key: GEODE-4830
> URL: https://issues.apache.org/jira/browse/GEODE-4830
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
> Reporter: Barbara Pruijn
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> The list jndi-binding command currently displays jndi-bindings that are
> active.
> We need to modify the output of this command to list all jndi-bindings that
> are listed in the cluster config and indicate in the output of this command
> whether the binding is active or configured.
> We should update the help text to reflect this change. A suggested help text
> is:
> {code:java}
> List all jndi bindings, active and configured. An active binding is one that
> is bound to the server's jndi context (and also listed in the cluster
> config). A configured binding is one that is listed in the cluster config,
> but is not active.{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
