Actually, same deal there, you shouldn't really be trying to use a
SOAP webservice (which I assume is what you mean, since you are
talking about RemoteException?) from a small embedded device either.
The reason "why is this" is that Android has a limited API, which is
designed for it's limited env
Ok. Now I'm trying to communicate with a webservice. The problem is
that I need to import java.rmi.RemoteException for something like:
String ret = (String) call.invoke(String method, Object[] o);
But the Android Eclipse plugin would not allow me to import
java.rmi.RemoteException, saying that it
Well, java.sql.NClob appears to be the problem. It looks like that
class is in rt.jar in a normal Java jre. Probably not part of Android
because I doubt they expect people to be doing this (I agree with
Charlie on why). I don't know why you don't have a choice, but I'll
say it looks like a bad des
Hi, thanks for your reply. But I really have no choice in this matter.
Using JDBC is my best bet here, and I would appreciate if somebody
could tell me what's going on.
On Apr 23, 2:56 pm, Charlie Collins <[EMAIL PROTECTED]> wrote:
> I don't have any insight to help in terms of answering your que
I don't have any insight to help in terms of answering your question
about using a JDBC driver from Android, but would offer one
suggestion: don't try it to begin with.
You would probably be a lot better off connecting to a server using
XML over HTTP (RESTy) or such, and then doing your JDBC stuf
5 matches
Mail list logo
