Thanks for the reply Amila. > What is the Axis2 version you use? - Axis2 1.5.3
> Can you run the code just commenting out the finally block? - I did the same, and printed exception before it reaches finally. I came to know that there was some problem with login credentials (security token, typical to sforce ws). So, I guess the login failure in turn spoiled the retrieval of transportOut. May I have the clear idea, if possible? Thanks. On Sat, Jan 8, 2011 at 7:10 PM, Amila Suriarachchi <[email protected]> wrote: > What is the Axis2 version you use? > > Can you please test with a nightly build? > > The actual problem is not the null pointer exception. it comes since there > is another problem which make > transportOut null. Can you run the code just commenting out the finally > block? > > thanks, > Amila. > > On Thu, Jan 6, 2011 at 11:05 PM, fire fox <[email protected]> wrote: >> >> Hi all, >> >> Details: partner.wsdl, Axis2., Salesforce API [I think problem is >> generic to Axis2] >> >> 1) Code used to login : >> >> - created stub by passing endpointurl >> >> - set HTTPConstants properties/options for stub, after creation >> >> - called stub.login by passing (Login, null, CallOptions (did set >> client Id)). [passed null for LoginScopeHeader] >> >> - then, NullPointerException thrown. >> >> 2) Exception origin: >> >> - SforceServiceStub.java : >> _messageContext.getTransportOut().getSender().cleanup(_messageContext); >> >> 3) Culprit: _messageContext.getTransportOut() returning NULL >> >> Any idea? >> >> Thanks in advance. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
