You may want to try the Jt Design Pattern Framework for your
application:

For additional information please refer to the following URLs:

a) Java Pattern Oriented Framework, An application of the Messaging
Design Pattern
IBM Technical Library
http://www.ibm.com/developerworks/webservices/library/ws-designpattern/index.html

b) Messaging Design Pattern (MDP) and pattern implementation -
Published in the 17th conference on Pattern Languages of Programs
(PLoP 2010).
https://jt.dev.java.net/files/documents/5553/150311/designPatterns.pdf

c) MDP and a distributed Component/Service Model
https://jt.dev.java.net/files/documents/5553/149793/MDPdistributedModel.pdf

You could use REST services. BTW it also supports AXIS but I wouldn't
recommended because of the reasons/limitations presented above. Jt
works fine
on Tomcat.

Jt also have many component that can be useful to you (AXIS adapter,
HTTP adapter, components for Struts, XML components. Tomcat is fully
supported.

As you probable know Struts is for GUI (server side). It is an
implementation
MVP.


On Oct 28, 4:34 pm, mastermind <[email protected]> wrote:
> I'm developing client-server application with android client and now
> I'm working on architecture trying to find proper technologies. Spent
> a lot of hours googling and testing and what I have:
> 1) Server: Tomcat + AXIS + WebServices. The best way on first sight,
> but as far as I know SOAP isn't maintained by android developers.
> Release date of kSOAP2 is 2007-03-15, may be there other libraries for
> SOAP services?
> 2) Server: Tomcat + Struts. I can use all power of J2EE, but struts
> designed mainly for web site development. Not exactly what I want.
> 3) Server: Tomcat + Servlets, using Google Protobuf for client server-
> interaction. Unfortunately, protobuf works hell slow on android. As
> far as know android use optimized version of this library inside but
> google doesn't officially support it. Please correct me if I
> mistaken.
> 4) Server: Tomcat + Servlets, using custom XML format for client-
> server interaction. At this time best solution. Just because first 3
> solution fails :( I can't use many useful J2EE features and I have to
> code a lot of stuff.
>
> Do you know any other ways? May be you can share your experience?
> I'm new in android development. Hope, you will help me with your
> advices :)

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to