[ https://issues.apache.org/jira/browse/GEODE-6990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juan José Ramos Cassella updated GEODE-6990: -------------------------------------------- Description: Create a new {{QueryServiceConfig}} element at the {{CacheConfig}} level to contain any configuration related to OQL, including the custom {{MethodInvocationAuthorizer}}. The resulting XML element should be as follows: {noformat} <query-service> <method-authorizer> <class-name>MyClass</class-name> <parameter name="myClassAttribute"> <string>stringValue</string> </parameter> </method-authorizer> </query-service> {noformat} Instead of modifying the core {{cache-1.0.xsd}}, add another independent {{xsd}} file as an extension of the cache’s configuration. An example of how to do this can be seen in [{{jdbc-1.0.xsd}}|https://github.com/apache/geode/blob/rel/v1.9.0/geode-connectors/src/main/resources/META-INF/schemas/geode.apache.org/schema/jdbc/jdbc-1.0.xsd]. This new configuration element and its properties should be stored and retrieved through the cluster configuration service. For more regarding the interactions with the cluster configuration service see [For extension developers: How to Add Elements Managed by Cluster Configuration Service|https://cwiki.apache.org/confluence/display/GEODE/For+extension+developers%3A+How+to+Add+Elements+Managed+by+Cluster+Configuration+Service]. was: Create a new {{QueryServiceConfig}} element at the {{CacheConfig}} level to contain any configuration related to OQL, including the custom {{MethodInvocationAuthorizer}}. The resulting XML element should look something like the following (*the properties are just examples for now, will need to refine this ticket once the section about how to add elements to the cluster configuration service has been added to the wiki*): {noformat} <query-service query-verbose="true"> <method-authorizer> <class-name>test.Authorizer</class-name> <parameter name="allowedMethodsDataBaseUrl"> <string>jdbc:mysql://myHost/allowedMethodsDatabase</string> </parameter> </method-authorizer> </query-service> {noformat} Instead of modifying the core {{cache-1.0.xsd}}, add another independent {{xsd}} file as an extension of the cache’s configuration. An example of how to do this is: [{{jdbc-1.0.xsd}}|https://github.com/apache/geode/blob/rel/v1.9.0/geode-connectors/src/main/resources/META-INF/schemas/geode.apache.org/schema/jdbc/jdbc-1.0.xsd] This new configuration element and its properties should be stored and retrieved through the cluster configuration service. > Implement Configuration Options for Method Authorizer > ----------------------------------------------------- > > Key: GEODE-6990 > URL: https://issues.apache.org/jira/browse/GEODE-6990 > Project: Geode > Issue Type: New Feature > Components: configuration > Reporter: Juan José Ramos Cassella > Priority: Major > > Create a new {{QueryServiceConfig}} element at the {{CacheConfig}} level to > contain any configuration related to OQL, including the custom > {{MethodInvocationAuthorizer}}. > The resulting XML element should be as follows: > {noformat} > <query-service> > <method-authorizer> > <class-name>MyClass</class-name> > <parameter name="myClassAttribute"> > <string>stringValue</string> > </parameter> > </method-authorizer> > </query-service> > {noformat} > Instead of modifying the core {{cache-1.0.xsd}}, add another independent > {{xsd}} file as an extension of the cache’s configuration. An example of how > to do this can be seen in > [{{jdbc-1.0.xsd}}|https://github.com/apache/geode/blob/rel/v1.9.0/geode-connectors/src/main/resources/META-INF/schemas/geode.apache.org/schema/jdbc/jdbc-1.0.xsd]. > This new configuration element and its properties should be stored and > retrieved through the cluster configuration service. For more regarding the > interactions with the cluster configuration service see [For extension > developers: How to Add Elements Managed by Cluster Configuration > Service|https://cwiki.apache.org/confluence/display/GEODE/For+extension+developers%3A+How+to+Add+Elements+Managed+by+Cluster+Configuration+Service]. -- This message was sent by Atlassian JIRA (v7.6.14#76016)