[ 
https://issues.apache.org/jira/browse/WODEN-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468286
 ] 

John Kaputin commented on WODEN-87:
-----------------------------------

Added four new methods to org.apache.woden.wsdl20.Interface which traverse 
interface inheritance in the component model to retrieve components that are 
declared or inherited:

InterfaceFault[] getAllInterfaceFaults()
InterfaceFault getFromAllInterfaceFaults(QName faultName)

InterfaceOperation[] getAllInterfaceOperations()
InterfaceOperation getFromAllInterfaceOperations(QName operName)

> Need convenience methods in Interface API to flatten interface inheritence
> --------------------------------------------------------------------------
>
>                 Key: WODEN-87
>                 URL: https://issues.apache.org/jira/browse/WODEN-87
>             Project: Woden
>          Issue Type: New Feature
>          Components: Parser
>            Reporter: John Kaputin
>         Assigned To: John Kaputin
>             Fix For: M7
>
>
> We have a use case (from Axis2) for convenience methods on the 
> org.apache.woden.wsdl20.Interface API for additional convenience methods that 
> provide a flattened view on all interface child components - both those 
> directly declared and any inherited ones.  Existing methods like 
> Interface.getInterfaceOperations and getInterfaceFaults return only the 
> components declared directly within the Interface (this is correct per the 
> description of those properties in the WSDL 2.0 spec).   Currently the 
> getExtendedInterfaces method must be used to 'drill down' to get inherited 
> components.   Cases like diamond inheritance must also be handled by the user 
> to avoid duplicates. The proposed convenience methods make all this 
> transparent to the user.
> The proposed new methods on Interface are:
> getAllInterfaceOperations
> getAllIntefaceFaults
> Some further consideration may be required about whether  the existing 
> behaviour of getInterfaceOperations and getInterfaceFaults if actually useful 
> (ie. getting the declared components only). An alternative approach would be 
> to add methods like getDeclaredInterfaceOperations and change the behaviou of 
> getInterfaceOperations to return all operations - direclty declared and 
> inherited. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to