[wsas-java-dev] [jira] Closed: (WSAS-17) Dynamic client generates a blank response when WSDL schema attributes are qualified (attributeFormDefault="qualified", elementFormDefault="qualified")

Charitha Kankanamge (JIRA) jira at wso2.org
Sun Jun 24 20:53:15 PDT 2007


     [ http://www.wso2.org/jira/browse/WSAS-17?page=all ]

Charitha Kankanamge closed WSAS-17.
-----------------------------------

    Fix Version/s: Nightly
       Resolution: Fixed

This is fixed in the latest nightly builds. Verified and closed the bug.

> Dynamic client generates a blank response when WSDL schema attributes are qualified (attributeFormDefault="qualified", elementFormDefault="qualified") 
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WSAS-17
>                 URL: http://www.wso2.org/jira/browse/WSAS-17
>             Project: WSO2 WSAS-Java
>          Issue Type: Bug
>         Environment: Win XP, JDK1.5, wso2wsas-standalone-edition-java-SNAPSHOT
>            Reporter: Charitha Kankanamge
>         Assigned To: Afkham Azeez
>             Fix For: Nightly
>
>
> When attributeFormDefault="qualified" elementFormDefault="qualified" are specified in the wsdl, you can not invoke the service using dynamic client. 
> It displays a blank result and following exception can be seen in WSAS log.
> RROR [2006-11-15 10:43:20,437]  Unable to handle request
> org.wso2.tungsten.ServerException: org.apache.axis2.AxisFault: null; nested exception is: 
> 	com.ctc.wstx.exc.WstxIOException: null; nested exception is: 
> 	org.apache.axis2.AxisFault: null; nested exception is: 
> 	com.ctc.wstx.exc.WstxIOException: null
> 	at org.wso2.tungsten.transport.jetty.Axis2SOAPHandler.processPostRequest(Axis2SOAPHandler.java:47)
> 	at org.wso2.tungsten.transport.jetty.Axis2Handler.handle(Axis2Handler.java:157)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:627)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149)
> 	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:123)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:141)
> 	at org.mortbay.jetty.Server.handle(Server.java:269)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:430)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:701)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:617)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:193)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:339)
> 	at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:208)
> 	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
> Caused by: org.apache.axis2.AxisFault: null; nested exception is: 
> 	com.ctc.wstx.exc.WstxIOException: null; nested exception is: 
> 	org.apache.axis2.AxisFault: null; nested exception is: 
> 	com.ctc.wstx.exc.WstxIOException: null
> 	at org.apache.axis2.transport.http.util.SOAPUtil.processPostRequest(SOAPUtil.java:75)
> 	at org.wso2.tungsten.transport.jetty.Axis2SOAPHandler.processPostRequest(Axis2SOAPHandler.java:42)
> 	... 13 more
> Caused by: org.apache.axis2.AxisFault: null; nested exception is: 
> 	com.ctc.wstx.exc.WstxIOException: null
> 	at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:221)
> 	at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:675)
> 	at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:48)
> 	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:496)
> 	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:319)
> 	at org.apache.axis2.transport.http.util.SOAPUtil.processPostRequest(SOAPUtil.java:56)
> 	... 14 more
> Caused by: com.ctc.wstx.exc.WstxIOException: null
> 	at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:271)
> 	at org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:119)
> 	at org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:412)
> 	at org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:275)
> 	at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:209)
> 	... 19 more
> Caused by: org.mortbay.jetty.EofException
> 	at org.mortbay.jetty.HttpGenerator.flushBuffers(HttpGenerator.java:856)
> 	at org.mortbay.jetty.HttpGenerator$Output.flush(HttpGenerator.java:1069)
> 	at org.mortbay.jetty.HttpConnection$Output.flush(HttpConnection.java:764)
> 	at sun.nio.cs.StreamEncoder$CharsetSE.implFlush(StreamEncoder.java:410)
> 	at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:152)
> 	at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:213)
> 	at java.io.BufferedWriter.flush(BufferedWriter.java:236)
> 	at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:184)
> 	at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:269)
> 	... 23 more
> Caused by: java.net.SocketException: Software caused connection abort: socket write error
> 	at java.net.SocketOutputStream.socketWrite0(Native Method)
> 	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
> 	at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
> 	at com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer(OutputRecord.java:283)
> 	at com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:272)
> 	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:663)
> 	at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59)
> 	at org.mortbay.io.ByteArrayBuffer.writeTo(ByteArrayBuffer.java:158)
> 	at org.mortbay.io.bio.StreamEndPoint.flush(StreamEndPoint.java:113)
> 	at org.mortbay.io.bio.StreamEndPoint.flush(StreamEndPoint.java:146)
> 	at org.mortbay.jetty.HttpGenerator.flushBuffers(HttpGenerator.java:778)
> Steps to reproduce:
> ===================
> 1. Create a service archive
> 2. Upload new archive through WSAS 
> 3. Click on the deployed service
> 4. Select 'Try it' link in the 'Service Management' screen
> 5. Select a valid port (eg:- SOAP11port_https)
> 6. Click on the available operation and enter request values for parameters
> 7. Click on 'Try' button
> Expected Result:
> ===============
> Correct output should be displayed as 'Response'
> Actual Result:
> ==============
> Blank response is returned

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://www.wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        




More information about the Wsas-java-dev mailing list