OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-1235) ActionImport and FunctionImport on EntityType


Ralf Handl created ODATA-1235:
---------------------------------

             Summary: ActionImport and FunctionImport on EntityType
                 Key: ODATA-1235
                 URL: https://issues.oasis-open.org/browse/ODATA-1235
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: New Feature
          Components: CSDL JSON , CSDL XML, URL Conventions
    Affects Versions: V4.01_CS01
            Reporter: Ralf Handl
             Fix For: V4.02_WD01


We allow calling bound actions/functions with qualified name, or with unqualified (short) name if the namespace defining the function is marked as the default namespace. In the latter case we need precedence rules if action/function names collide with property names.

This can be avoided if an entity type can actively declare which actions/functions it allows by "importing" the (still global) action/function into the type, similar to what we currently do in the entity container. 

This has several benefits:
* explicitly declare support for bound actions/functions
* provide clash-free short name for bound action/function
* harmonize entity container and entity type 



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]