Yes it does. That works!
Thanks,
Dan
Willem Jiang wrote:
>
> Hi,
>
> Do your TxPortType.class has the @WebService annotation?
> If so, please use the JaxWsClientFactoryBean which will take care of
> this annotation to create the proxy.
> Here is the code snippet.
>
> ClientProxyFactoryBean
Hi,
Do your TxPortType.class has the @WebService annotation?
If so, please use the JaxWsClientFactoryBean which will take care of
this annotation to create the proxy.
Here is the code snippet.
ClientProxyFactoryBean factory = new ClientProxyFactoryBean(new
JaxWsClientFactoryBean());
...
Ah, I should have though of that.
It's very informative.
The HTML I am getting back basically says it is a 401 error
with the message "This request requires HTTP authentication".
It appears the auth info in not getting transmitted.
I added logging interceptors for both IN and OUT.
On the outbound
You're getting HTML back for some reason instead of a soap message.
My only suggestion would be to do:
client.getInInterceptor().add(new
org.apache.cxf.interceptor.LoggingInInterceptor());
and see what it prints out. The HTML might give a clue.
Dan
On Friday 07 March 2008, Daniel Lipofsky
username/password are not wrong because I used the same
username/password for each method and the first one works.
I tried the change you suggested and now I get a different
error. Does this give you any more info?
ClientProxyFactoryBean factory = new ClientProxyFactoryBean();
factory.setSe
Your error is a bit strange. It looks like it could be one of:
1) The name/password might be wrong or something and the server is
re-asking you to authenticate
2) The server might be sending a redirect.
You might want to put a wireshark/tcpdump trace on it to see what the
server is sending
