axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Commented: (AXIS2-3457) Incorrect Exception in WSDL11ToAxisServiceBuilder
Date Mon, 21 Jan 2008 03:34:33 GMT


Amila Chinthaka Suriarachchi commented on AXIS2-3457:

OK +1 to do this change.
Please make sure you change all the places referring to addQNameReference.

> Incorrect Exception in WSDL11ToAxisServiceBuilder
> -------------------------------------------------
>                 Key: AXIS2-3457
>                 URL:
>             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:
For additional commands, e-mail:

View raw message