my dog learned polymorphism*
The moose likes Java Micro Edition and the fly likes Server side implications of J2ME Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Mobile » Java Micro Edition
Bookmark "Server side implications of J2ME" Watch "Server side implications of J2ME" New topic
Author

Server side implications of J2ME

Pearlo Muthukumaran
Ranch Hand

Joined: Sep 17, 2002
Posts: 79
Hi,
I am implementing a serverside component to interact with the J2ME midlet.
Actually, a XML doc is posted by the Midlet through HTTP
The servlet handles the same...
At the server end I am using kXML for parsing as the performance is really good.What I want to know is that I have to pass this XML doc either in raw form or in kDOM form to a EJB Component.
Is it advisable to pass it as raw xml or as kDOM object ?
If second option is adopted, is kDOM serializable?
Rgds
Muthu
Parsuram panigrahi
Greenhorn

Joined: Feb 18, 2003
Posts: 17
I am not sure which form is better (RAW XML or KDOM Object), but kdom object is serializable.
http://kxml.org/api/overview-tree.html
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Server side implications of J2ME
 
Similar Threads
How to create a SSLSocket on midp ??
Anything like JTable for J2ME
new to J2ME. Please help !
J2ME Mobile application MIDLET Form
deloyping MIDLET on any server