Hi all.
I've solved the same problem by adding to the generated wsdl the auth headers
(i failed to make java2wsdl tool to generate headers, so i've written a "header
adder"...) to be filled by C# client with login/password info and then parsed
with custom axis handler.
Further the credent
I created an issue in JBossWeb for it
http://jira.jboss.com/jira/browse/JBWEB-11
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862912#3862912
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862912
---
Yes we are implementing a C# app talking to J2EE web services. So it is
important to us. Cheers
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862668#3862668
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862668
---
Is anyone else using C# clients? This seems like a serious enough
interoperability issue that the JBoss team would want to address it. It's quite
simple to reproduce:
1. set up JBoss using Basic HTTP authentication.
2. create a .NET client (C# perhaps)
3. make request.
4. see 505 error.
5. chan
The big drawback we are currently facing is the pre-notification that has to be
done for all our .Net customers. Additionally from within the Visual Studio
framework, any updating of the web reference will cause this patch to go away
and it has to be re-added.
View the original post :
http://w
