Replace setRealm with setDomain.
-- dims
On 9/27/06, Satyajit Jha <[EMAIL PROTECTED]> wrote:
Hi Srinivas,
Thanks for all your help. I downloaded the nightly and tried to run my code.
Apparently, there has been some change in authentication class and I am
unable to do the NTLM authentication and hence unable to verify this fix.
Please tell me what I am doing wrong in the following code snippet. I am
unable to find any help from Google over this as this is a recent change.
HttpTransportProperties.Authenticator ntlmAuth
= new HttpTransportProperties.Authenticator();
ntlmAuth.setUsername(username);
ntlmAuth.setPassword(password);
ntlmAuth.setHost(serverName);
ntlmAuth.setRealm(DomainName);
stub._getServiceClient().getOptions().setProperty(HTTPConstants.AUTHENTICATE,
ntlmAuth);
Earlier I was using
HttpTransportProperties.NTLMAuthentication class and was
able to do it successfully. But now I am getting "HTTP Transport error :
'401' - 'Unauthorized' " exception. Do I need to provide the authentication
mechanism ("NTLM" here) explicitly here? if yes, please let me know how can
I do that.
Thanks,
Satyajit
On 9/25/06, Davanum Srinivas (JIRA) <[EMAIL PROTECTED]> wrote:
> [
http://issues.apache.org/jira/browse/AXIS2-1177?page=all ]
>
> Davanum Srinivas resolved AXIS2-1177.
> -------------------------------------
>
> Resolution: Fixed
>
> Fixed in latest SVN rev 449753. Please try a nightly in an hour or two. Oh
BTW, you need to fix your wsdl a bit. the parts are not correcly specified.
Here's the snippet for Render binding operation (specifically the
part="part1" instead of part="RenderServerInfoHeader")
>
> <wsdl:binding
name="ReportExecutionServiceSOAP11Binding"
type="tns:ReportExecutionServicePortType">
> <soap:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"/>
> <wsdl:operation name="Render">
> <wsdl:input>
> <soap12:body
use="literal" namespace="
http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices"/>
> <soap12:header
message="tns:RenderExecutionHeader" part="part1"
use="literal"/>
> </wsdl:input>
> <wsdl:output>
> <soap12:body
use="literal" namespace="
http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/reportingservices"/>
> <soap12:header
message="tns:RenderServerInfoHeader" part="part1"
use="literal"/>
> </wsdl:output>
> </wsdl:operation>
> </wsdl:binding>
>
> -- dims
>
> > 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.
> >
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> > Key: AXIS2-1177
> > URL:
http://issues.apache.org/jira/browse/AXIS2-1177
> > 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 " org.apache.axiom.om.OMException:
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="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Heade
> > r><ExecutionHeader
> > xmlns="
http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/repor
> >
tingservices"><ExecutionID>03lkco45n0p2nqzfl35c5g45</ExecutionID></Execu
> > tionHeader></soapenv:Header><soapenv:Body><ns1:Render
> >
xmlns:ns1="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/r
> >
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="http://schemas.xmlsoap.org/soap/envelope/ "
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema
"><soap:Header><ServerInfoHea
> > der
> >
xmlns="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/repor
> >
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="http://schemas.microsoft.com/sqlserver/2005/06/30/reporting/repor
> >
tingservices"><Result>77u/PD94bWwgdmVyc2lvbj0iMS4wIj8+PFJlcG9ydCB4bWxucz
> >
0icHJvdl9zdW0iIHhtbG5zOnhzaT0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbW
> >
EtaW5zdGFuY2UiIHhzaTpzY2hlbWFMb2NhdGlvbj0icHJvdl9zdW0gaHR0cDovL2xvY2FsaG
> >
9zdDo1MDMyL1JlcG9ydFNlcnZlcj8lMmZQT19SZXBvcnRzJTJmcHJvdl9zdW0mYW1wO3JzJT
> >
NhRm9ybWF0PVhNTCZhbXA7cmMlM2FTY2hlbWE9VHJ1ZSIgTmFtZT0icHJvdl9zdW0iIHRleH
> >
Rib3gxPSJTdW1tYXJ5IG9mIFByb3ZpZGVyICdETUUwMTk4N0cnIj48dGFibGUxIE5BTUU9Ik
> >
wgRSBDIEhPTUUgQ0FSRSBNRURJQ0FMIiBQUlZfUEg9IjcxNDgyMTQyOTgiIEFERFJfMT0iMT
> >
A3MzIgTE9TIFZBUVVFUk9TIENJUiI+PERldGFpbF9Db2xsZWN0aW9uPjxEZXRhaWwgU1BFQ1
> >
9DRF8xPSI5OSIgQ0lUWT0iTE9TIEFMQU1JVE9TIiBUWVBFX0NEPSIwMDIiIC8+PC9EZXRhaW
> >
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:
http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
http://www.atlassian.com/software/jira
>
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
