You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@olingo.apache.org by "Christian Amend (JIRA)" <ji...@apache.org> on 2014/04/07 10:36:14 UTC

[jira] [Updated] (OLINGO-202) Refactor getOperation methods

     [ https://issues.apache.org/jira/browse/OLINGO-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Amend updated OLINGO-202:
-----------------------------------

    Description: 
At the edm:
Seperate getAction into getBoundAction() and getUnboundAction()
Seperate getFunction into getBoundFunction() and getUnboundFunction()

to be more explicit and prevent confusion.

At the ActionImport and FunctionImport:
Delete the getBound... methods
Introduce the getActions and getFunctions method which will deliver all UNBOUND actions and functions with the specified name.

  was:
Seperate getAction into getBoundAction() and getUnboundAction()

Seperate getFunction into getBoundFunction() and getUnboundFunction()

to be more explicit and prvent confusion.


> Refactor getOperation methods
> -----------------------------
>
>                 Key: OLINGO-202
>                 URL: https://issues.apache.org/jira/browse/OLINGO-202
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata4-client, odata4-commons, odata4-server
>            Reporter: Christian Amend
>            Assignee: Christian Amend
>             Fix For: V4 0.1.0
>
>
> At the edm:
> Seperate getAction into getBoundAction() and getUnboundAction()
> Seperate getFunction into getBoundFunction() and getUnboundFunction()
> to be more explicit and prevent confusion.
> At the ActionImport and FunctionImport:
> Delete the getBound... methods
> Introduce the getActions and getFunctions method which will deliver all UNBOUND actions and functions with the specified name.



--
This message was sent by Atlassian JIRA
(v6.2#6252)