[jira] [Created] (OLINGO-1007) SystemQueryOptions Are Swallowed by RequestURLHierarchyVisitor

["Mitch Connors (JIRA)" <ji...@apache.org>]

Mitch Connors created OLINGO-1007:
-------------------------------------

             Summary: SystemQueryOptions Are Swallowed by RequestURLHierarchyVisitor
                 Key: OLINGO-1007
                 URL: https://issues.apache.org/jira/browse/OLINGO-1007
             Project: Olingo
          Issue Type: Bug
          Components: odata4-server
    Affects Versions: (Java) V4 4.2.0
            Reporter: Mitch Connors


RequestURLHierarchyVisitor, in server-core-ext, has visitor methods defined for the various system query options, however they are all empty methods (for instance, see [here|https://github.com/apache/olingo-odata4/blob/master/lib/server-core-ext/src/main/java/org/apache/olingo/server/core/RequestURLHierarchyVisitor.java#L270]).  This would lead me to believe that they were designed for overriding in Custom classes by the Service Implementor, however there appears to be no way to inject a new instance of RequestURLHierarchyVisitor (inherited by ServiceDispatcher) into the handler.  

What is the intended way for consumers of the server-core-ext library to implement system query option support?  Should injection of custom ServiceDispatchers be allowed?  Is an example in order?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)