[ https://issues.apache.org/jira/browse/GEODE-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386610#comment-16386610 ]
Barbara Pruijn commented on GEODE-4385: --------------------------------------- The create jndi-binding command will save any jndi config string in the cluster config. But the parameters passed into the create jndi-binding command may not result into a jndi-binding that is valid and can be instantiated at run time on the server members. Therefore, the list jndi-binding command will only display jndi-bindings that have been successfully instantiated on the servers. The help text for the {code:java} help list jndi-binding{code} should have some text explaining that the list jndi-binding command will list valid and instantiated jndi-bindings. > gfsh command to list jndi binding > --------------------------------- > > Key: GEODE-4385 > URL: https://issues.apache.org/jira/browse/GEODE-4385 > Project: Geode > Issue Type: Sub-task > Reporter: Barbara Pruijn > Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > In cache.xml user can specify jndi binding like so: > {code:java} > <jndi-bindings> > <jndi-binding jndi-name="DemoDatasource" type="SimpleDataSource" > jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin" > password="changeme" > connection-url="jdbc:postgresql://localhost:5432/gemfire_db"> > </jndi-binding> > </jndi-bindings> > {code} > A user should be able to list a datasource using the gfsh command {{list > jndi-binding}} > Then all jndi-binding names will be displayed. > Please look at Geode's schema for a list of attributes that can be set: > [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331] -- This message was sent by Atlassian JIRA (v7.6.3#76005)