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] Commented: (ODATA-103) 5.4.1 Representing Actions Bound to Multiple Entities: specify treatment of action overloads


    [ http://tools.oasis-open.org/issues/browse/ODATA-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31790#action_31790 ] 

Ralf Handl commented on ODATA-103:
----------------------------------

An important difference to property access is that derived types MUST NOT redefine properties that are already defined by one of their ancestor types.

Which might be a good restriction here, too. 

The behavior of SendEMail will probably depend on the binding parameter type anyway, so the only additional "feature" introduced by this extension is that the specialized action may have a different signature.

Do we really need this?

I could argue that a Customer entity may need a different Address complex type than a mere Person, requiring to give the Address property a different "signature".

> 5.4.1 Representing Actions Bound to Multiple Entities: specify treatment of action overloads
> --------------------------------------------------------------------------------------------
>
>                 Key: ODATA-103
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-103
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Mark Biamonte 
>            Assignee: Michael Pizzo
>             Fix For: WD01
>
>
> Actions can have overloads based on the binding parameter type and entity types allow inheritance, so multiple overloads can in principle apply to a given set of entities.
> If restrictions exist for action overloads in an inheritance hierarchy, they need to be documented in the OData-Core specification.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


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