TECHNOLOGIES
FORUMS
JOBS
BOOKS
EVENTS
INTERVIEWS
Live
MORE
LEARN
Training
CAREER
MEMBERS
VIDEOS
NEWS
BLOGS
Sign Up
Login
No unread comment.
View All Comments
No unread message.
View All Messages
No unread notification.
View All Notifications
Answers
Post
An Article
A Blog
A News
A Video
An EBook
An Interview Question
Ask Question
Forums
Monthly Leaders
Forum guidelines
andre.rodriguez
NA
1
0
Namespace prefixes are a problem for .NET Web Service
Oct 16 2003 2:15 PM
I have written a Web Service in .NET and it works when invoked through a browser. However, the parameter has a null value when accessing it from a Java RPC call. The method is GenerateComments and the (only) parameter is QARequestNumber. I have narrowed the problem down to the existance of a namespace prefix. The following SOAP snippet is from a request that *does not* work:
MyRequestNumber
The following manually modified SOAP snippet is from a request that *works*, no problem:
MyRequestNumber
As you can see the 'ns1' namespace prefix is what appears to be the problem. How can I get my Web Service to accept the ns1 prefix, or ignore it? (The other side of the coin is getting the JAX-RPC call to not put in the ns1 prefix, but that is a different challenge.) TIA
Reply
Answers (
0
)
Deployment of Web Service
Can't change Autolog Property