Ant, prototype, buffalo, and linen

Because of the needs of technology selection, I have learned a few small open-source things, and I feel I have received some inspiration. Let's talk about it :-)

Ant -- ant (another neat tool)

Is it more convenient to use ide to build a project. Why should ant be used? In general, IDE is designed to improveProgramStaff's personal productivity, rather than the continuous construction of the development team, even if some ides can well support team development and building, and even we can ensure that everyone uses the same type of IDE. However, programmers may still have different build paths and temporary directory structures, may still use different ide versions, and may still use different plug-ins on the IDE, it even runs or is deployed on different platforms. This will eventually lead to the situation where a runs wellCodeB.

Therefore, if we are creating a software product for developers, We need:

1-create a programmer to execute the ant Build File rules before submitting the new code to the version control system.

2-make sure that you can use standard ant to build a project, instead of executing a clean build through an IDE.

Use ant as a public baseline to ensure that the Code is always buildable and that programmers can freely choose any IDE tool, environment, or editor they are used.

Prototype

This is a mature and well-received Javascript development framework that encapsulates many common JavaScript and DHTML application functions and scenarios. Many domestic projects have already started to use it. I personally think the biggest selling point of prototype is that it encapsulates a set of mechanisms to create classes and use objects in Scripts like in Java, this allows developers to easily write scripts in an object-oriented style.

Buffalo-Buffalo

I'm glad to see a domestic open-source project that you can find in soureforge. I think it is a Ajax application framework similar to DWR. I personally think its biggest advantage is that it can return Java value objects to Ajax callback functions in the form of Script objects, through XML data transfer, Java server-side objects and script client/browser-side objects maintain the same data and operation, so that developers can hardly feel the transformation of data objects.

At the same time, I feel that buffalo is lighter than DWR. Of course, I personally prefer to use my own simple Ajax framework, I don't think Ajax is as important as encapsulation.

Burlap

An XML-based Data Exchange Protocol is generally used for remote calls by enterprise applications. HTTP invoke between heterogeneous systems is also supported to a certain extent, and its usage is much simpler than that of Web services. It is quite convenient to use without additional definition files such as WSDL, it has perfect integration with spring. In the spring configuration file, you can fully describe all the content of remote calls. It is said that the speed is faster than the soap-based Web service. If you confirm that your SOA architecture and enterprise applications are mainly based on Java technology, why not consider using burlap?

--------------------------------------------

The above are my personal opinions. You are welcome to add your own opinions and discuss them with me ......