Catálogo de publicaciones - libros

We’ve seen how Tapestry adheres to its goal of making the simplest choice the right choice along with its core principles of simplicity, efficiency, consistency, and feedback. Tapestry tackles web applications by breaking them into pages made up of components that are wired into Java classes. In web development with Tapestry the developer focuses on working with components, not dealing with session, URLs, or converting string values from the form into the appropriate Java paradigms. Building upon the standard servlet API, Tapestry will run on any application server or servlet container.

Along with Tapestry’s rich set of components, we have an evolving set of Ajax-enabled components from the Tacos library. Though still in beta, they provide robust functionality that allows us to “Ajaxify” a Tapestry application. Not only is Ajax development greatly simplified with Tacos, we even have built-in effects and complex widgets thanks to the high-quality Dojo library. Though we’ve only scratched the surface, it’s clear that Tacos and Tapestry are a great combination for creating robust, scalable web applications based on Java.

Although Ajax isn’t rocket science, there is a fair amount of tedious code, and creating truly helpful client-side effects can be a challenge. Lucky for us, there are a number of very strong libraries that can aid our effort. We’ve seen how using the right toolkit can, in just a few lines, give us wizard-like effects, ones that will improve the usability of our application while also being easy to add.

Believe it or not, but we’ve just scratched the surface of these libraries’ capabilities as well as the toolkit space in general. Hopefully, you have enough to go on to perform your own evaluation and decide which of these libraries will improve your application. These libraries are fairly dynamic, so you may want to stop by their home pages from time to time to see what they’re up to!

Although Ajax isn’t rocket science, there is a fair amount of tedious code, and creating truly helpful client-side effects can be a challenge. Lucky for us, there are a number of very strong libraries that can aid our effort. We’ve seen how using the right toolkit can, in just a few lines, give us wizard-like effects, ones that will improve the usability of our application while also being easy to add.

Believe it or not, but we’ve just scratched the surface of these libraries’ capabilities as well as the toolkit space in general. Hopefully, you have enough to go on to perform your own evaluation and decide which of these libraries will improve your application. These libraries are fairly dynamic, so you may want to stop by their home pages from time to time to see what they’re up to!

As the granddaddy of all Java web MVC frameworks, Struts has built up a loyal following of developers and has innumerable applications built on top of it. Struts frees the developer from having to write directly to the servlet API and constantly edit the web.xml file. Struts provides built-in support for validation, internationalization, and a set of JSP custom tags that ease the burden of building rich, web-enabled Java applications.

Ajax integrates very easily with Struts. An Ajax request can call any Struts action by simply sending the request to the correct URL. Once there, the Ajax request is handled the same as any other HTTP request. This, of course, means that the Ajax request has the same access to the Struts validation routines, form beans, and actions, and the benefits provided by each.

Struts and Ajax work very well together, and existing Struts applications can be easily extended by adding Ajax functionality. In many cases Ajax-style interactions can be added to an existing Struts application by adding an Action that reuses existing functionality.

As the granddaddy of all Java web MVC frameworks, Struts has built up a loyal following of developers and has innumerable applications built on top of it. Struts frees the developer from having to write directly to the servlet API and constantly edit the web.xml file. Struts provides built-in support for validation, internationalization, and a set of JSP custom tags that ease the burden of building rich, web-enabled Java applications.

Ajax integrates very easily with Struts. An Ajax request can call any Struts action by simply sending the request to the correct URL. Once there, the Ajax request is handled the same as any other HTTP request. This, of course, means that the Ajax request has the same access to the Struts validation routines, form beans, and actions, and the benefits provided by each.

Struts and Ajax work very well together, and existing Struts applications can be easily extended by adding Ajax functionality. In many cases Ajax-style interactions can be added to an existing Struts application by adding an Action that reuses existing functionality.

We’ve seen how Tapestry adheres to its goal of making the simplest choice the right choice along with its core principles of simplicity, efficiency, consistency, and feedback. Tapestry tackles web applications by breaking them into pages made up of components that are wired into Java classes. In web development with Tapestry the developer focuses on working with components, not dealing with session, URLs, or converting string values from the form into the appropriate Java paradigms. Building upon the standard servlet API, Tapestry will run on any application server or servlet container.

Along with Tapestry’s rich set of components, we have an evolving set of Ajax-enabled components from the Tacos library. Though still in beta, they provide robust functionality that allows us to “Ajaxify” a Tapestry application. Not only is Ajax development greatly simplified with Tacos, we even have built-in effects and complex widgets thanks to the high-quality Dojo library. Though we’ve only scratched the surface, it’s clear that Tacos and Tapestry are a great combination for creating robust, scalable web applications based on Java.

Although Ajax isn’t rocket science, there is a fair amount of tedious code, and creating truly helpful client-side effects can be a challenge. Lucky for us, there are a number of very strong libraries that can aid our effort. We’ve seen how using the right toolkit can, in just a few lines, give us wizard-like effects, ones that will improve the usability of our application while also being easy to add.

Believe it or not, but we’ve just scratched the surface of these libraries’ capabilities as well as the toolkit space in general. Hopefully, you have enough to go on to perform your own evaluation and decide which of these libraries will improve your application. These libraries are fairly dynamic, so you may want to stop by their home pages from time to time to see what they’re up to!

As the one web framework that’s actually a Sun specification, Java developers cannot simply ignore JSF. With new frameworks like Seam based upon its foundations, it’s clear that JSF has much to offer. Though it’s taken some time for JSF to take off, with the availability of books like Pro JSF and Ajax by John R. Fallows and Jonas Jacobi (Apress, 2006), it is clear that the momentum is there. Using existing components and leveraging integrated tools can slash implementation time and allow developers to focus on the business needs instead of the plumbing of a web application. While we’ve only scratched the surface of what can be done in JSF and Ajax, hopefully we’ve given you the tools to try it out for yourself.