[ http://wso2.org/jira/browse/COMMONS-43?page=comments#action_13937 ] 
            
Jonathan Marsh commented on COMMONS-43:
---------------------------------------

What do you need the header structure for?  Are you exposing it in the sig or 
trying to populate it automatically (though I doubt that's really possible) in 
the binding?  What would internal structure, including attributes, look like in 
the signature?

Right now the stylesheet compiles schema structures into a parameter-list 
structure.  Is this sufficient for header structure?  E.g. the request for 
attributes seems incompatible with the parameter-list structure I can currently 
generate.

> Is it possible to have type information of the header elements in the sig 
> model
> -------------------------------------------------------------------------------
>
>                 Key: COMMONS-43
>                 URL: http://wso2.org/jira/browse/COMMONS-43
>             Project: WSO2 Commons
>          Issue Type: Improvement
>          Components: dynamic-codegen
>            Reporter: Buddhika Semasinghe
>         Assigned To: Jonathan Marsh
>            Priority: Minor
>
> If we have the type information of header element recursively as in params 
> and returns elements in sig model it would be useful.ex:
> <binding-details>
> <soapheader for="input" required="true" type="MetadataMessage" 
> type-namespace="http://www.w3.org/ns/wsdl"/>
> <! if we have information of MetadataMessage  here  I think  it would be more 
> consistent--->
> </binding-details>

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

        

_______________________________________________
Commons-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/commons-dev

Reply via email to