Design a service-oriented J2EE Application Framework

In order to cope with the various course design and competition preparation projects at the end of the period, I haven't written a blog for some time. From 1.13, I had a holiday and went home on the 1949th day. During these ten-day periods, daily bubble lab, after various discussions and explorations, has identified the following things so far:

1. Determine the project to participate in the competition: implement a service-oriented (service-based search and execution) J2EE application system. The final goal is probably: The supported service consumer platforms, including mobile phones and browsers; Support for calls between heterogeneous platforms, currently Java platform calls. net, EJB, and PHP Web Services. 2. determined Development Environment: mobile client development: Using netbeans 5.5 + netbeans mobility pack for cldc/MIDP 5.5 browser client JSP page development: one of the core of myeclipse + Dreamweaver 8, development of J2EE applications: The Core Component of eclipse 3.2 + myeclipse 5.0, that is, calling customer APIs of various web services: using open-source soap framework axis under Apache. net and PHP Web Service Development: Use Visual Studio. net and PHP development tools Zend 3. the preliminary architecture of the system is determined: the overall architecture of the system uses the combination of spring and Struts. One of the reasons for using struts as Web MVC is that the project team members used struts to develop Web applications, it will be familiar, so use it instead of spring MVC. The system uses the hierarchical mode, the Sping IOC container to manage the relationship between pojo, And the DaO support of spring to implement the DAO mode of the persistent layer. The initial architecture diagram is as follows: 3. Problems Solved so far (I will mention how to solve these critical problems in my blog ):

 

L communication issues between mobile phone j2s and J2EE servlets.

L how to use the dynamic call basis of axis to implement communication between the Java platform and other heterogeneous platforms, such as. net.

L since I have been working on the Java platform, to communicate with Web Services on heterogeneous platforms, I must first be familiar with how to publish Web Services on other platforms.

 

This is just the beginning, and there are still many unsolved problems. Here, we just roughly use the log to record the beginning of the project, and there will be detailed documentation records in the future.