[Issue 589] New - WSDL parser confused by closing tag

[ritzmann]

https://jax-ws.dev.java.net/issues/show_bug.cgi?id=589
                 Issue #|589
                 Summary|WSDL parser confused by closing tag
               Component|jax-ws
                 Version|current
                Platform|Macintosh
              OS/Version|All
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|runtime
             Assigned to|issues@jax-ws
             Reported by|ritzmann






------- Additional comments from ritzmann@... Thu Jun 26 13:03:28 +0000 2008 -------
This bug report relates to: https://jax-ws.dev.java.net/issues/show_bug.cgi?
id=580

Issue 580 is about throwing a more meaningful exception than a
NullPointerException. This bug report here is about the reason why an exception
is wrongly created. The bug can be reproduced with the WSDL contained in the NB
project attached to issue 580. (Actually, the bug can be reproduced with WSDL
that JAX-WS generates automatically from Java, which makes this a likely
occurance.)

I found that the JAX-WS runtime parser cannot properly parse WSDL binding
sections that contain XML elements with closing tags. As an example, this
section will be parsed correctly:

    <binding name="TestServicePortBinding" type="tns:TestService">
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document"/>
        <operation name="echo">
            <soap:operation soapAction=""/>
            <input>
                <soap:body use="literal"/>
            </input>
            <output>
                <soap:body use="literal"/>
            </output>
        </operation>
    </binding>

Now change e.g. the soap:binding element into this:

        <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document">
        </soap:binding>

The parser will parse the <soap:binding element> and store the results. Then,
the while loop in RuntimeWSDLParser:421 will read the XML stream event, which
in this case is a number of CHARACTERS event because of the whitespace between
the opening soap:binding and the closing soap:binding tag. The parser ignores
the events until it receives an END_ELEMENT event. The while loop is
implemented such that it will always interpret the END_ELEMENT as belonging to
the encapsulating binding element.

Subsequently, the parser expects a service section but still receives XML
reader events for the binding section that it hasn't finished parsing properly.
Therefore it fails to parse the service and port of the WSDL, which leads to an
exception for a missing port in the end.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...

[jitu-4]

https://jax-ws.dev.java.net/issues/show_bug.cgi?id=589



User jitu changed the following:

                What    |Old value                 |New value
================================================================================
             Assigned to|issues@jax-ws             |ramapulavarthi
--------------------------------------------------------------------------------




------- Additional comments from jitu@... Thu Jun 26 14:57:06 +0000 2008 -------
assigning to Rama

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...

[bthelen]

https://jax-ws.dev.java.net/issues/show_bug.cgi?id=589



User bthelen changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|'bhaktimehta'             |'bhaktimehta,bthelen'
--------------------------------------------------------------------------------




------- Additional comments from bthelen@... Mon Aug 25 21:45:31 +0000 2008 -------
CC'ing myself.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...

[scm_issue_link]

https://jax-ws.dev.java.net/issues/show_bug.cgi?id=589






------- Additional comments from scm_issue_link@... Thu Sep 18 01:08:28 +0000 2008 -------
Code changed in jax-ws-sources
User: ramapulavarthi
Path:
 /jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/wsdl/parser/RuntimeWSDLParser.java (1.49)
 http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=MAIN:ramapulavarthi:20080918010721

Log:
JAX-WS-589: Fixing the RuntimeWSDLParser where it does nt' read until the end element which leaves in a state not processable by other procedures. This happens when there is a separate end element like
 <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document">
        </soap:binding>
instead of simple  <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
style="document"/>
Fixed.


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...

[ramapulavarthi]

https://jax-ws.dev.java.net/issues/show_bug.cgi?id=589



User ramapulavarthi changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |RESOLVED
--------------------------------------------------------------------------------
              Resolution|                          |FIXED
--------------------------------------------------------------------------------




------- Additional comments from ramapulavarthi@... Thu Sep 18 01:09:49 +0000 2008 -------
Fixed in jax-ws 2.1.5

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...

[jitu-4]

https://jax-ws.dev.java.net/issues/show_bug.cgi?id=589



User jitu changed the following:

                What    |Old value                 |New value
================================================================================
        Target milestone|not determined            |2.1.5
--------------------------------------------------------------------------------




------- Additional comments from jitu@... Mon Sep 29 21:10:48 +0000 2008 -------
Setting the target milestone to 2.1.5

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@...
For additional commands, e-mail: issues-help@...