By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,686 Members | 1,510 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,686 IT Pros & Developers. It's quick & easy.

NET Client calling Axis web service

P: n/a
I have a Net 2.0 client (C# Winform) calling an Axis web service. I can
authenticate, and send a request that is accepted and responded to, but I
cannot see the response.

The return for the call to the webservice is an object. Looking at the SOAP
message that comes in, I can see the response. However when I assign the
response to instance of the object, the result is null. Example:

1. WorkRequestServiceImplService myRequest = new
WorkRequestServiceImplService();
2. WorkRequestTO workRequest = new WorkRequestTO();
3. WorkRequestStatusTO workRequestStatus = new WorkRequestStatusTO();
4. workRequest = createNewWorkRequest(); //create new work request
5. workRequestStatus = myRequest.createWorkRequest(workRequest);

workRequest is complete when sent in step 5, however workRequestStatus
contains all nulls after step 5. Again, the SOAP response contains the
object values it should contain. Net appears to be having trouble
deserializing response code. Any ideas?

Aug 14 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Should add that literal and not SOAP section-5 encoding is being used on the
Axis server.

"David R" wrote:
I have a Net 2.0 client (C# Winform) calling an Axis web service. I can
authenticate, and send a request that is accepted and responded to, but I
cannot see the response.

The return for the call to the webservice is an object. Looking at the SOAP
message that comes in, I can see the response. However when I assign the
response to instance of the object, the result is null. Example:

1. WorkRequestServiceImplService myRequest = new
WorkRequestServiceImplService();
2. WorkRequestTO workRequest = new WorkRequestTO();
3. WorkRequestStatusTO workRequestStatus = new WorkRequestStatusTO();
4. workRequest = createNewWorkRequest(); //create new work request
5. workRequestStatus = myRequest.createWorkRequest(workRequest);

workRequest is complete when sent in step 5, however workRequestStatus
contains all nulls after step 5. Again, the SOAP response contains the
object values it should contain. Net appears to be having trouble
deserializing response code. Any ideas?
Aug 14 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.