001/* 002 * Licensed to the Apache Software Foundation (ASF) under one or more 003 * contributor license agreements. See the NOTICE file distributed with 004 * this work for additional information regarding copyright ownership. 005 * The ASF licenses this file to You under the Apache License, Version 2.0 006 * (the "License"); you may not use this file except in compliance with 007 * the License. You may obtain a copy of the License at 008 * 009 * https://www.apache.org/licenses/LICENSE-2.0 010 * 011 * Unless required by applicable law or agreed to in writing, software 012 * distributed under the License is distributed on an "AS IS" BASIS, 013 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 014 * See the License for the specific language governing permissions and 015 * limitations under the License. 016 */ 017package org.apache.commons.configuration2.tree; 018 019import java.util.List; 020 021/** 022 * <p> 023 * Definition of an interface for evaluating keys for hierarchical configurations. 024 * </p> 025 * <p> 026 * An <em>expression engine</em> knows how to map a key for a configuration's property to a single or a set of 027 * configuration nodes. Thus it defines the way how properties are addressed in this configuration. Methods of a 028 * configuration that have to handle property keys (for example {@code getProperty()} or {@code addProperty()} do not interpret 029 * the passed in keys on their own, but delegate this task to an associated expression engine. This expression engine 030 * will then find out, which configuration nodes are addressed by the key. 031 * </p> 032 * <p> 033 * Separating the task of evaluating property keys from the configuration object has the advantage that multiple 034 * different expression languages (i.e. ways for querying or setting properties) can be supported. Just set a suitable 035 * implementation of this interface as the configuration's expression engine, and you can use the syntax provided by 036 * this implementation. 037 * </p> 038 * <p> 039 * An {@code ExpressionEngine} can deal with nodes of different types. To achieve this, a {@link NodeHandler} for the 040 * desired type must be passed to the methods. 041 * </p> 042 * 043 * @since 1.3 044 */ 045public interface ExpressionEngine { 046 047 /** 048 * Returns the key of an attribute. The passed in {@code parentKey} must reference the parent node of the attribute. A 049 * concrete implementation must concatenate this parent key with the attribute name to a valid key for this attribute. 050 * 051 * @param parentKey the key to the node owning this attribute 052 * @param attributeName the name of the attribute in question 053 * @return the resulting key referencing this attribute 054 */ 055 String attributeKey(String parentKey, String attributeName); 056 057 /** 058 * Determines a "canonical" key for the specified node in the expression language supported by this 059 * implementation. This means that always a unique key if generated pointing to this specific node. For most concrete 060 * implementations, this means that an index is added to the node name to ensure that there are no ambiguities with 061 * child nodes having the same names. 062 * 063 * @param <T> the type of the node to be processed 064 * @param node the node, for which the key must be constructed 065 * @param parentKey the key of this node's parent (can be <strong>null</strong> for the root node) 066 * @param handler the {@code NodeHandler} for accessing the node 067 * @return the canonical key of this node 068 */ 069 <T> String canonicalKey(T node, String parentKey, NodeHandler<T> handler); 070 071 /** 072 * Returns the key for the specified node in the expression language supported by an implementation. This method is 073 * called whenever a property key for a node has to be constructed, for example by the 074 * {@link org.apache.commons.configuration2.Configuration#getKeys() getKeys()} method. 075 * 076 * @param <T> the type of the node to be processed 077 * @param node the node, for which the key must be constructed 078 * @param parentKey the key of this node's parent (can be <strong>null</strong> for the root node) 079 * @param handler the {@code NodeHandler} for accessing the node 080 * @return this node's key 081 */ 082 <T> String nodeKey(T node, String parentKey, NodeHandler<T> handler); 083 084 /** 085 * Returns information needed for an add operation. This method gets called when new properties are to be added to a 086 * configuration. An implementation has to interpret the specified key, find the parent node for the new elements, and 087 * provide all information about new nodes to be added. 088 * 089 * @param <T> the type of the node to be processed 090 * @param root the root node 091 * @param key the key for the new property 092 * @param handler the {@code NodeHandler} for accessing the node 093 * @return an object with all information needed for the add operation 094 */ 095 <T> NodeAddData<T> prepareAdd(T root, String key, NodeHandler<T> handler); 096 097 /** 098 * Finds the nodes and/or attributes that are matched by the specified key. This is the main method for interpreting 099 * property keys. An implementation must traverse the given root node and its children to find all results that are 100 * matched by the given key. If the key is not correct in the syntax provided by that implementation, it is free to 101 * throw a (runtime) exception indicating this error condition. The passed in {@code NodeHandler} can be used to gather 102 * the required information from the node object. 103 * 104 * @param <T> the type of the node to be processed 105 * @param root the root node of a hierarchy of nodes 106 * @param key the key to be evaluated 107 * @param handler the {@code NodeHandler} for accessing the node 108 * @return a list with the results that are matched by the key (should never be <strong>null</strong>) 109 */ 110 <T> List<QueryResult<T>> query(T root, String key, NodeHandler<T> handler); 111}