WebService Client and TTL

  • Thread starter Thread starter Mario Enriquez
  • Start date Start date
M

Mario Enriquez

Hi,

I've run into this problem, and I hope you could help me on this!

I've developed a webs service in java, which I use from a .netCF
application, but
every time I try to access it I get a "Could not find resource assembly"
exception.

Since I've have tested this server from my PC browser I can tell the
webservice it's working. which
has lead me to believe that this is something related to a timeout or a Time
to Life (ttl) issue on the client
side. Could you please tell me how do I increase the ttl value from and
Webservice in .netCF?

What else could I check out?

Thanks for your help!
Mario
 
I don't see how it could be a TTL problem. That's handled *way* below the
..NET CF in the network stack.

It sounds to me as though you haven't included the proper references in your
project. Does this happen no matter what method of the service you call
(you might even add a simple "hello, world" method that just returns a
string and try calling that).

Paul T.
 
Paul,

Thank you for your reply!

You are right, this might not be a TTL problem. However nothing else come to
my mind,
since the call to the webservice work fine, when the handheld in on the
cradle. This way
I'm sure the webreference it's properly set up. Any ideas?

Thanks in advance,
Mario
 
Have you tried adding a very simple method to your service and trying to
call that? Have you run your client program in the debugger and checked
where the problem is occurring?

Paul T.
 
From what you are describing it looks like an exception occurs but your
device does not have System.SR.Dll installed and thus the debug information
cannot be displayed. Have you tried doing this ina debug session? Also, one
of the most common errors around web services is attempting to invoke the
service using localhost address. It wiull work on PC but not on the device,
because there localhost is the device itself. All in all to eliminate
address lookup problems, try using the actual web service IP address instead
of a machine name
 
Back
Top