Ashish Patel wrote: > I have been following kXML, kSOAP and subsequently EnhydraME that > enables the J2ME devices to act as not only consumer of Web Services but > also provider of Web Services i.e. microproxy and microserver concepts. > Around mid March JCP has launched JSR 172 to introduce Web Services > based API for CDC and CLDC configurations. To my knowledge this API is > covering definition of efficient XML parser and JAX-RPC interface based > Web Services support. Based on the JSR 172 API, different vendors should > provide the implementations to conform application portability. It is > true that at it this moment EnhydraME offers more than just kXML and > kSOAP, but is the EnhydraME group following this JSR 172? What are the > views of different contributors in EnhdraME project about this? Hi Ashish, till now, I was not aware of JSR 172. I have some doubts whether the combination of JSR 63 and JSR 101 is a good starting point for CLDC configurations, and I am not a big fan of transparent RPC (or JINI). Actually, I cannot imagine how transparent serialization will work without reflection. I tried to Join JSR 173 (streaming XML), and I hope this JSR will produce an XML API better suitable for J2ME than JSR 63. Personally, I would be more interested in a CLDC based profile that puts a subset of the Servlet API on top of CLDC; I think there would be many applications in small devices that do not have a screen but are attached to a network (routers, ...?) (so if France Telecom is going to initiate a corresponding JSR, please don't forget to invite me ;-). Best, Stefan -- Stefan Haustein Univ. Dortmund, FB 4, LS 8 tel: +49 231 755 2499 Baroper Str. 301 fax: +49 231 755 5105 D-44221 Dortmund (Germany) www-ai.cs.uni-dortmund.de |