[
https://issues.apache.org/jira/browse/OLINGO-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Reddy resolved OLINGO-417.
---------------------------------
Resolution: Duplicate
Fix Version/s: (Java) V4 4.0.0-beta-03
Assignee: Ramesh Reddy
This was done as part of OLINGO-573
> 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
> Assignee: Ramesh Reddy
> Fix For: (Java) V4 4.0.0-beta-03
>
>
> 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.3.4#6332)
