Skill application: How to improve the development speed of Java project

j2ee| Skills | speed | project

In the Java EE Technology system, it is often instilled in the concept of too many containers, what EJB containers, servlet containers, and so on, and the development process in the development, configuration, deployment between iterations and repeated; so often embarrassing situations occur: It takes a few minutes to change a bug, It takes two or more hours to deploy and test, and development engineers have to interrupt their thinking, watch the server start up like a snail, and switch back and forth between development tools and deployment tools.

In fact, configuration or deployment is an essential step in the development process. How to integrate these development phases organically through an integrated development environment is an urgent need for us. In this article, I'll explain the idea of a "lightweight" development and the Apusic platform platform for implementing the idea, which includes application servers and studio development platforms.

Technology Model Simplification

The development of Java EE today, a popular view is: The booming open source community to the official standard of EE has a big impact, and even some developers on the 5.0 of the Authority has been questioned, and Java EE 5.0 can occupy the mainstream development platform of concern.

In fact, I think that the open source community and the Java EE is more of a complementary relationship. Open source is often idealistic, while business companies represent often realism, where there is competition between them, but in the long run, more is a process of complementarity and mutual promotion.

In the implementation of Apusic platform, on the one hand, a variety of open source technology is very large support, including struts, Hibernate, spring, etc. not only provides a series of sample templates to demonstrate how to use these open source components on the Apusic application server, It even provides business support for these open source frameworks to better promote and use these open-source technologies at home.

The most notable of Java EE is EJB 3 and JSF, EJB 3 overcomes many deficiencies and drawbacks of EJB 2.x version, making EJB technology become the main computing model of enterprise application, which lays a theoretical foundation for the overall popularization of EJB. JSF is the main solution Java EE tries to solve for Web application development. Our upcoming Apusic JSF incorporates JSF and Ajax technologies, overcoming the drawbacks of the conventional JSF implementations and making JSF a lightweight web development model. At present, we are trying to apusic JSF as open source in the form of feedback to the vast number of web developers in the country, and look forward to the Apusic JSF to form a rich Web UI component market, so as to completely solve the current Web application development of the main deficiencies.

Development process Integration

For example, a simple Web application development, in Apusic Studio, can be provided by the JSP editor syntax highlighting, code assistance, breakpoint debugging and other functions, very convenient to assist developers to quickly complete the development of Web pages, but also through the visual configuration interface, to complete the tedious web/ Ejb/ear, etc. configuration information.

When you want to run a page, just click on the right mouse button "quot, debug on the Apusic application Server", Apusic Studio will automatically help us do this series of actions: first of all to determine whether the application server is running (if not run will automatically create a new startup configuration entry, Set the Classpath to start the application server, and then determine if the application is deployed (automatically deploy the application if no deployment is deployed), finally automatically open the browser, run the specified JSP page, and even Apusic studio can sense changes to the application, and deploy automatically when the application needs to be redeployed.

Business Component Utility

Looking back at the technology system of Java EE, and even many popular open source frameworks, it is easy to see that the problems they solve are all concentrated in the software model itself: for example, or Mapping, AOP, MVC, and so on. In reality, developers of application systems want to shield the underlying implementation technology from some sort of business start platform or some generic business component, so that they focus on the business itself.

However, because the business components lack the corresponding specification and standard, they are not high in practicality and usability. This is derived from the complexity and variability of the requirements of the business system itself and, on the other hand, the lack of a JCP-like organization to develop and develop the specifications and standards of these business components.

Apusic platform tries to offer another option: to create a more practical business component, such as organizational structure, permission model, report printing, and so on, through a pluggable and replaceable mechanism. These business components, integration of Kingdee company and its partners for many years of application development wisdom crystallization, to the business system developers to bring real convenience.

Lightweight two-tier meaning

What is lightweight? In my opinion, lightweight contains two layers of meaning. One is the lightweight of the runtime: it consumes the least amount of system resources under the same computing task; the second is the lightweight of the development period, which refers to the agile and fast response capability of the development process.

The lightweight of the runtime can be said to be in the microkernel system as the core, the code is only similar software 20% of the Apusic application server has been very good validation: whether it is the start-up speed, or the operating period of the system resources consumed, apusic are significantly ahead, Perhaps the only thing the industry can compare with is Tomcat. But Tomcat is just a web container, and the Apusic application server is an enterprise-class product that fully implements the Java EE 1.4 specification, which was fully implemented in May this year, as for the robustness and stability of the runtime, Apusic in various indicators and foreign similar software comparable.

The lightweight development phase, we can gain the agility of the development process Apusic studio with the development tools that are tightly integrated with the Apusic application server. Whether it's coding, configuration, deployment, testing, or late monitoring and performance tuning, we can get integrated support through Apusic studio.

Let Java ee develop more easily

Development process integration, so that developers do not have to consider the deployment, configuration and other trivial processes, and do not need to interrupt the idea of the pain of the server repeatedly started; The technology model simplifies, solves the complex problem in the reality through the excellent simple technology, the business component is practical, can get rid of some concrete implementation details, focus on the

The above concept, I call it a similar martial arts in Kungfu to a certain level of "triple cover Top", which largely liberated the Java EE, let us have the development process of agile and pleasure.

Agile fast, let the Java-ee development easier, why not?