[
https://issues.apache.org/jira/browse/TUSCANY-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Edwards closed TUSCANY-3019.
---------------------------------
Closing resolved issues
> WSDL interface processing not correct
> -------------------------------------
>
> Key: TUSCANY-3019
> URL: https://issues.apache.org/jira/browse/TUSCANY-3019
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
> Affects Versions: Java-SCA-2.0
> Reporter: Mike Edwards
> Assignee: Mike Edwards
> Fix For: Java-SCA-2.0
>
>
> <interface.wsdl/> element processing is not correct with respect to the OASIS
> specification, plus the error reporting of faults with an <interface.wsdl/>
> element is inadequate and fails to report serious problems.
> 1) <interface.wsdl/> processing
> The form of <interface.wsdl/> is as follows:
> <interface.wsdl
> interface="http://www.stockquote.org/StockQuoteService#wsdl.porttype(StockQuote)"
>
> callbackInterface="http://www.stockquote.org/StockQuoteService#wsdl.porttype(StockQuoteCallback)"/>
> - current code does not process "wsdl.porttype" but instead expects
> "wsdl.interface" and fails silently and with unexpected consequences when
> presented with an <interface.wsdl/> in the form above. Even when the
> interface attribute has garbage for the fragment part of the URI, it is
> accepted silently.
> - #wsdl.interface is acceptable for the OSOA versions of the spec, but
> wsdl.porttype is the correct form
> 2) Error reporting
> The wrong format of the fragment part of the URI for a WSDL interface is not
> reported and the code tries to accept a section of the fragment as the
> porttype name even when garbage is presented. Also, if the WSDL fails to
> resolve, no errors are raised with the consequnce of unexpected runtime
> failures.
> Found with OASIS Assembly testcases, eg ASM_5032_TestCase
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
