Christian,
I am running the service and the client test program from the same eclipse
project. service is running on the tomcat (6.0) instance inside the eclipse
workspace. I don't know where the second request is coming from. I noticed
the behavior after i look at the logs that there is a second request also.
After reviewing your note, I decided to create another project in eclipse
and run the client from there. Without any changes the results are much
better and the client program is now working. Does this make sense?
In case i run into the issue again, I would like to explore the suggestion
of preemptive authorization that you are mentioning, assuming that i need to
run this on the client. Please correct me if i am wrong.
should the below be added to the client:
<http-conf:conduit name="*.http-conduit">
<http-conf:authorization>
<sec:UserName>tomcat</sec:UserName>
<sec:Password>tomcat</sec:Password>
</http-conf:authorization>
</http-conf:conduit>
or directly to the calling java code as below:
HTTPConduit conduit = (HTTPConduit) proxy.getConduit();
AuthorizationPolicy auth = conduit.getAuthorization();
if ( null == auth ) {
System.out.println (" auth policy is null");
auth = new AuthorizationPolicy();
}
auth.setUserName( "tomcat" );
auth.setPassword( "tomcat" );
thanks,
Prasad.
--
View this message in context:
http://cxf.547215.n5.nabble.com/BasicAuth-SoapHeaderInterceptor-Nullpointer-exception-issue-tp4885314p4895591.html
Sent from the cxf-user mailing list archive at Nabble.com.
