You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "John Kaputin (JIRA)" <ji...@apache.org> on 2008/02/08 12:38:08 UTC

[jira] Commented: (WODEN-156) Parser does not properly handle component extensions for interfaces

    [ https://issues.apache.org/jira/browse/WODEN-156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566993#action_12566993 ] 

John Kaputin commented on WODEN-156:
------------------------------------

The existing ComponentModelBuider just sets up extension property interfaces (now subtypes of ComponentExtensionContext with WODEN-47) for the components that have extensions defined by the WSDL 2.0 spec (wsdlx, rpc, http, soap).  Woden needs to handle extension props for any WSDL components so that it can support other extension providers (e.g. SAWSDL, who define extension for several Interface subcomponents).  

Could do this by replacing ComponentModelBuilder behaviour with a new implementation of the WSDLComponent.getComponentExtensionContext(NSuri) method that retrieves extension property interfaces. This basically shifts the existing behaviour from ComponentModelBuilder to WSDLComponentImpl with the effect that it applies to ALL components, not just those currently supported by ComponentModelBuilder.

Possible implementation of the getComponentExtensionContext(NSuri) method:

1. check this WSDL object's instance var collection (i.e. local cache) of ComponentExtensionContext objects using specifiedNS. If found return it.

2. check if the WSDL object has ext elements or ext attributes for specified NS. If not return null (assumes that if there is no WSDL infoset content from that NS, there is no ext property context for that NS either. Alternative would be to return a ComponentExtensionContext object if one was registered, even though it's methods will just return null or empty arrays).

3. create a ComponentExtensionContext object of the type registered in the ExtensionRegistry. If not registered return null.

4. store the new ComponentExtensionContext object in the WSDL object's instance var collection (i.e. local cache), then return it. 


> Parser does not properly handle component extensions for interfaces
> -------------------------------------------------------------------
>
>                 Key: WODEN-156
>                 URL: https://issues.apache.org/jira/browse/WODEN-156
>             Project: Woden
>          Issue Type: Bug
>          Components: Parser
>         Environment: All
>            Reporter: Ajith Harshana Ranabahu
>            Assignee: John Kaputin
>             Fix For: M8
>
>         Attachments: woden-component.patch, woden-component1.patch
>
>
> The parser does not query the extension registry or add the relevant component extensions to the interface object

-- 
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: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org