You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Ramesh Reddy (JIRA)" <ji...@apache.org> on 2014/08/29 20:37:53 UTC
[jira] [Created] (OLINGO-417) Expression visitor class is not
flexibile
Ramesh Reddy created OLINGO-417:
-----------------------------------
Summary: Expression visitor class is not flexibile
Key: OLINGO-417
URL: https://issues.apache.org/jira/browse/OLINGO-417
Project: Olingo
Issue Type: Improvement
Components: odata4-server
Reporter: Ramesh Reddy
The current visitor frame work has couple drawbacks
1) The name of the methods should be "visitor" (just pet peeve)
2) It is not necessary that all the visitation methods can return same type of return value across the whole visitor class. In my scenario I am trying to build a SQL language object
3) The Expression object *must* not dictate the Expression navigation to visitor. The current way limits one way to walk the expression, not very flexible. It should be left out the visitor to walk the expression.
--
This message was sent by Atlassian JIRA
(v6.2#6252)