17th March 2008, 06:27 pm
Google Web Toolkit (GWT) is an open source Java development framework that permits you gets away the matrix of technologies which make writing of AJAX applications so complicated. Development and debugging of AJAX applications in the Java language becomes easy with GWT. The GWT compiler interprets your Java application to browser-compliant JavaScript and HTML while deployment of application to production.
Brief overview of GWT development cycle is as under:
- Choose your preferred Java IDE to write and debug an application in the Java language, using as many (or as few) GWT libraries as you find useful.
- For serving with any web server use GWT’s Java-to-JavaScript compiler to condense your application into a set of JavaScript and HTML files.
- Make sure that your application works in all browsers that you desire to support.
Continue reading ‘Google Web Toolkit’ »
17th March 2008, 06:26 pm
There were technical challenges faced by Java developers and organization while developing applications in Java platforms. Spring Framework provides solutions to many of their technical challenges. Reason of popularity of the Spring Framework is not particularly its linking to the Java Enterprise platform, despite the fact, its widely influential integration in this area.
The Spring Framework is well known for providing features which are required to create intricate business applications effectively outside of the programming models. It is also accredited for initiating earlier unfamiliar functionalities into today’s mainstream development practices.
Continue reading ‘Spring’ »
17th March 2008, 06:24 pm
Cocoon is a java framework used for making web applications. It is built on the theory of separation of concerns, pipelining and component based web development. Separation of concerns helps in consistent interaction and collaboration of people with the project. And component pipelining is used to implement these concepts.
Cocoon provides a mechanism for the description of structure and semantics of web information items termed as contents, the relationship between content items termed as logic and how they will be presented to the viewer that is style, so it will not be wrong to say that cocoon is an XML-based content management system. The basic purpose of cocoon is to separate the three layers, i.e. content layer, logic layer and style. All these layers are designed, created and managed independently.
Continue reading ‘Cocoon’ »
17th March 2008, 06:23 pm
WebWork is a java framework for developing web applications. WebWork have its own exciting concepts and constructs that make it different from other frameworks. It differentiates itself by providing a way to overcome the limitations of other frameworks. Its features include the model-view-controller design, J2EE font controller and the value stacks, used for assigning values to its custom JSP tags. The unique features of webworks are type conversion, interceptors and continuations.
The basic task of WebWork is to keep things simple that will help in maintaining flexibility. Webwork use the existing web APIs in java instead of hiding or replacing them completely. Nevertheless it does not completely depend on the existing APIs, it has central controller that create action objects. WebWork framework is currently available in version.
Continue reading ‘WebWork’ »
17th March 2008, 06:23 pm
Tapestry is a framework for creating dynamic and robust web applications in Java. Tapestry is built on the concept of standard Java Servlet API. It can work in any servlet container or application server. Tapestry is a real framework for building intricate applications by using simple and reusable components. It competes with other frameworks such as Struts, Web Work, and Turbine. Tapestry is developed by Howard Lewis Ship; it has emerged as the first choice for web developers as an application framework. Tapestry is also a part of Jakarta Project at Apache software foundation.
At present Tapestry is in release 5.0. The main focus of Tapestry is on creating dynamic HTML pages. With default implementations supplied, API of Tapestry is portrayed in terms of interfaces. By replacing new objects with the correct interfaces, the performance of the framework can be changed considerably. An ordinary example is to override where page and component specifications are stored.
Continue reading ‘Tapestry’ »
Loading …Maturity:
