You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Peter Danielsen (JIRA)" <ji...@apache.org> on 2007/08/23 17:10:31 UTC

[jira] Updated: (AXIS2-3148) Endpoint Extension handling bug in WSDL20ToAxisServiceBuilder

     [ https://issues.apache.org/jira/browse/AXIS2-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Danielsen updated AXIS2-3148:
-----------------------------------

    Attachment: patch.txt
                Reserve.wsdl

I'm attaching the WSDL2 file I used to produce the problem.  It's based on what's in the WSDL2 Primer.  I'm also attaching a patch file that modifies WSDL20ToAxisServiceBuilder's processEndpoint method to call a binding-specific method to handle the extensions, either processSOAPBindingEndpointExtensions(Endpoint, AxisEndpoint) or processHTTPBindingEndpointExtensions(Endpoint, AxisEndpoint).

Ideally, I think it would be more modular to move the binding-specific processing (for both Endpoint and Binding) out of this class to separate classes for SOAP and HTTP and have them implement a common interface with one method for endpoint extensions  and one for binding extensions.  This class might then look up the binding in a property file to determine which class to use and invoke the appropriate method via the interface.

> Endpoint Extension handling bug in WSDL20ToAxisServiceBuilder
> -------------------------------------------------------------
>
>                 Key: AXIS2-3148
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3148
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.3
>         Environment: XP, JDK 1.5
>            Reporter: Peter Danielsen
>         Attachments: patch.txt, Reserve.wsdl
>
>
> I encountered a NullPointerException when trying to run WSDL2Java on a WSDL2 file that uses the HTTP binding.  The cause of the exception is in WSDL20ToAxisServiceBuilder.processEndpoint where it's trying to use SOAP endpoint extensions regardless of which binding is in use.  It should first check to see which binding is being used and then use binding-specific code to deal with the endpoint extensions.

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