axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satyajit Jha (JIRA)" <>
Subject [jira] Updated: (AXIS2-1177) I am getting "OMException: Can't find datahandler" when I try to execute render operation on MSRS 2005. It seems that the axis2 generated stub client is not able to handle Base64 enocded data.
Date Mon, 25 Sep 2006 08:05:50 GMT
     [ ]

Satyajit Jha updated AXIS2-1177:

    Attachment: ReportExecutionService.wsdl

> I am getting "OMException: Can't find datahandler" when I try to execute render operation
on MSRS 2005. It seems that the axis2 generated stub client is not able to handle Base64 enocded
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>                 Key: AXIS2-1177
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: databinding
>    Affects Versions: 1.0
>         Environment: Eclipse IDE 3.1.1 on Windows XP
>            Reporter: Satyajit Jha
>         Assigned To: Thilina Gunarathne
>         Attachments: ReportExecutionService.wsdl
> I am facing this problem with response handling and Thilina advised me to report a bug
for that. I am using axis2 generated stub client to render reports from MSRS 2005. I am getting
this " Can't find datahandler" exception. I am first invoking
the LoadReport operation and passing the executionID from its response while invoking Render
operation. Please see the request and response message for render operation below. I am using
Axis2 SNAPSHOT build (September 10, 2006).  I dont know how to attach a file here, so I am
not able to attach the WSDL file. Please let me know how can I do that in case you need the
WSDL file. Let me know if you need anything else.
> I have not specfied any particular databinding mechanism to be used. But if I look at
the generated client code, it looks like it is using ADB.
> Request:
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope
> xmlns:soapenv=""><soapenv:Heade
> r><ExecutionHeader
> xmlns="
> tingservices"><ExecutionID>03lkco45n0p2nqzfl35c5g45</ExecutionID></Execu
> tionHeader></soapenv:Header><soapenv:Body><ns1:Render
> xmlns:ns1="
> eportingservices"><ns1:Format>XML</ns1:Format></ns1:Render></soapenv:Bod
> y></soapenv:Envelope>
> Response:
> <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap=""
> xmlns:xsi=""
> xmlns:xsd=""><soap:Header><ServerInfoHea
> der
> xmlns="
> tingservices"><ReportServerVersionNumber>2005.090.1399.00</ReportServerV
> ersionNumber><ReportServerEdition>Enterprise</ReportServerEdition><Repor
> tServerVersion>Microsoft SQL Server Reporting Services Version
> 9.00.1399.00</ReportServerVersion><ReportServerDateTime>2006-09-17T21:46
> :20</ReportServerDateTime></ServerInfoHeader></soap:Header><soap:Body><R
> enderResponse
> xmlns="
> tingservices"><Result>77u/PD94bWwgdmVyc2lvbj0iMS4wIj8+PFJlcG9ydCB4bWxucz
> 0icHJvdl9zdW0iIHhtbG5zOnhzaT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbW
> EtaW5zdGFuY2UiIHhzaTpzY2hlbWFMb2NhdGlvbj0icHJvdl9zdW0gaHR0cDovL2xvY2FsaG
> 9zdDo1MDMyL1JlcG9ydFNlcnZlcj8lMmZQT19SZXBvcnRzJTJmcHJvdl9zdW0mYW1wO3JzJT
> NhRm9ybWF0PVhNTCZhbXA7cmMlM2FTY2hlbWE9VHJ1ZSIgTmFtZT0icHJvdl9zdW0iIHRleH
> xfQ29sbGVjdGlvbj48L3RhYmxlMT48L1JlcG9ydD4=</Result><Extension>xml</Exten
> sion><MimeType>text/xml</MimeType><Encoding>Unicode
> (UTF-8)</Encoding><StreamIds
> /></RenderResponse></soap:Body></soap:Envelope>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message