on May 6, 2007 at 3:34 AM PDT
I'm looking into exposing various aspects of a service API on a J2ME client.
I am frustrated at the lack of options (thus far) and would like to know
what your experiences are. I have a already existing Spring / EJB 3 API on
the server side which in turn has entities with many-to-one Collections and
I cant modify the API but I can add to it, exposing it as an endpoint using
XFire, for example.
The first natural candidate would be SOAP, but I didn't find much in the way
of actual JSR 172 support. So then I started looking into kSOAP, which would
be fine if I could find more documentation on it and could somehow generate
stubs (there's far too many things in the API to make it worth "dynamically"
invoking. Even when I tried invoking it dynamically I couldnt seem to get
the kSOAP implementatino to play nicely with my new-ish SOAP 1.2 stack.
Then, it occurred to me I might have better luck with XMLRPC and just accept
passing xmlrpc structs back and forth as the API -- which would be ok if
there was somehow a way to do it reliably and consistantly.
I understand I might have better luck if i force open the original APIs and
somehow seperate the entities from their service layers, making them
implement kvmSerializable and impleenting all those ridiculous methods on
each entity (not desirable).
I am now looking at really just giving up the ghost and rewriting the
endpoint using RESTlets (which is a completely new API for me, but at least
it would be guaranteed to work with J2ME and the basic http connector, given
that i completely rework the way the APIs exposed.
What is the opinion of the list on service exposure like this? Any anecdotal
evidence for or against any of these ideas/solutions? Unfortunately, except
for JSR 172 , the trail on a lot of these technologies seems to gone cold
around 2003, so Im also a bit put off by the lack of continued support.
Any insight is appreciated, thanks.
Sun Certified Java Programmer
To unsubscribe, send email to firstname.lastname@example.org and include in the body
of the message "signoff KVM-INTEREST". For general help, send email to
email@example.com and include in the body of the message "help".