Midlet app size and web services - most efficient way of connecting?!?

From: davout (davZZZYYYXXXout_at_dial.pipex.com)
Date: 10/28/04 

Date: Thu, 28 Oct 2004 21:46:05 +0100

I'm about to start a project to build a (fat client) Java midlet for a
mobile phone smart device. The midlet has to call a number of different
server side web services.

For a Java Swing client application I'd normally pass the web service WSDL
thru a utility to generate a set of client side classes that assume
responsbilty for generating the web service XML calls. However, this
approach does generate a lot of java client side code, and I'm wondering
whether these smart devices have the capacity to handle these volume of Java
code.

Should I think about a different approach - like using a command procesor
pattern web service? This would require the midlet to build a XML message
that included the real business tier service/method names and its
parameters. The command pattern web service at its end would decypher this
XML structure and pass on the instruction to the required business tier.

Does anybody have any thoughts on how best to proceed?

Relevant Pages

  • Re: Pushing data from the server to the client
    ... have data pushed from the Java webservice to your client? ... > information on the client machine, and it's never any older than ... So I mocked up a facade web service on my side in .NET ... > the remoting dll on each client machine and the stub on the server. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Pushing data from the server to the client
    ... have data pushed from the Java webservice to your client? ... > information on the client machine, and it's never any older than ... So I mocked up a facade web service on my side in .NET ... > the remoting dll on each client machine and the stub on the server. ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Pushing data from the server to the client
    ... have data pushed from the Java webservice to your client? ... > information on the client machine, and it's never any older than ... So I mocked up a facade web service on my side in .NET ... > the remoting dll on each client machine and the stub on the server. ...
    (microsoft.public.dotnet.framework.remoting)
  • Midlet app size and web services - most efficient way of connecting?!?
    ... The midlet has to call a number of different ... For a Java Swing client application I'd normally pass the web service WSDL ...
    (comp.lang.java.gui)
  • Midlet app size and web services - most efficient way of connecting?!?
    ... The midlet has to call a number of different ... For a Java Swing client application I'd normally pass the web service WSDL ...
    (comp.lang.java.help)