[
https://issues.apache.org/jira/browse/AXIS2-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559946#action_12559946
]
Amila Chinthaka Suriarachchi commented on AXIS2-3457:
-----------------------------------------------------
I agree with you that this exception is misleading.
The problem I found when doing this was that wsdl specification does not define
the HTTP binding properly and there no details even in the WS-I basic profile.
the only sample given in the wsdl spec has a rpc type sample. message part
refers to an type.
what is the functionality wise feature you are going to add by doing this
change?
my understanding is that for HTTP binding it is better to use the wsdl2.0
instead of wsdl1.1.
> Incorrect Exception in WSDL11ToAxisServiceBuilder
> -------------------------------------------------
>
> Key: AXIS2-3457
> URL: https://issues.apache.org/jira/browse/AXIS2-3457
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
>
> Background
> WSDL11ToAxisServiceBuilder contains code to produce schema "wrapper" code
> for selected BindingOperations (i.e. RPC literal bindings).
>
> Problem:
> I have a WSDL with several bindings, one of them is an HTTP Binding. The
> current code determines that its BindingOperations require wrappering, but
> during the schema generation it throws the following error because it
> incorrectly assumes that the BindingOperation is RPC/literal.
> org.apache.axis2.description.WSDL11ToAxisServiceBuilder populateService
> RPC-literal type message part Body should have a type attribute
> Proposed Solution:
> I have just started working on this issue. My thought is to introduce a
> private inner class BindingOperationEntry. The BindingOperationEntry will
> contain the BindingOperation and information about the BindingOperation (i.e.
> isRPC()).
> The findWrappableBindingOperations(Binding binding) method will be changed to
> return a List of BindingOperationEntry instead of List of BindingOperation.
> Later processing can then easily distinguish between RPC and HTTP usage.
> In addition, I am going to upgrade the exception message (which confused the
> user) and add some additional trace.
> This solution has minimal impact on the existing structure of
> WSDL11ToAxisServiceBuilder, which is why I pursuing this approach.
> Comments ?
--
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]
