JSF and Struts are the traditional component frameworks developers turn to for Web development. You have an alternative, however: Tapestry and Wicket are component-oriented Web frameworks designed to create Web applications. A simple example application implementing a to-do list workflow is developed here, using Tapestry and Wicket technologies.

This paper presents an overview of AJAX, what a black box tester should know before he leaps into AJAX testing, and the security risks that AJAX applications open up. Also discussed are the market trends are for AJAX adoption and its prospective growth potential. Finally the author looks at some of the black box test ideas and recommendations that test two main security concerns in AJAX implementation: data validation and session management.

Bad content, bad links, bad navigation, bad category pages... which is worst for business? In these examples, bad content takes the prize for costing the company the most money.

This article covers anti-patterns and pitfalls of day to day JSF development. Most of these issues have kept the author up at night; some of these are the same old challenges with a new face, pun intended. These challenges include performance, tight coupling, thread safety, security, interoperability and just plain ugliness.

I'd learned several best practices that I applied when working on my desktop apps. Two of them were:
* Separation of concerns: don't mix UI logic with underlying behavior.
* Automated unit testing: write automated tests that verify whether your code does what you think it does.

The underlying principles here apply regardless of technology. Separation of concerns is a fundamental principle that exists to help you deal with complexity. Mixing Different responsibilities within the same object—like calculating remaining work hours, formatting data, and drawing a graph—is just asking for maintenance problems. And automated testing is crucial to getting production-quality code while still maintaining your sanity, particularly when you're updating an existing project. ASP.NET Web Forms made it very easy to get started, but, in other ways, trying to apply my design principles to Web apps was a struggle. Web Forms are relentlessly UI focused; the fundamental atom is the page. You start by designing your UI and dragging controls. It's very seductive to just start slapping your application logic into the page's event handlers

In a perfect world, you'd create every Web site you were ever assigned to maintain, improve, and redesign. Unfortunately, in the real world, you're often forced to take on a site someone else designed or constructed.

New jobs, new projects, new assignments, and new responsibilities all carry with them risk. And while you may have a new boss or a new office or a new set of colleagues, nothing is quite so intimidating as being handed a Web site that is now yours to care and feed, having no idea how that Web site was put together. More often than not—especially if you're taking over for a less-experienced Web designer, or worse yet, someone who was just "filling in"—the sites you'll inherit are a tangled jumble of content, presentation, and even some activity. And, of course, the pages are ugly. If there aren't blink tags, there are jumbled styles, font tags mixed with CSS styles, unclosed and misused HTML tags... it can be a mess.

Thankfully, there's a logical approach to turning these sorts of pages into finely tuned, easily maintainable Web sites. This two-part series provides a road map for turning messy and unruly pages into well-structured, organized, maintainable code. In Part 1, you'll learn how to make a site maintainable. In Part 2, you'll organize your site's layout, increase its efficiency, and make sure you're in control.

It turns out that some tried-and-true techniques make a task like this manageable and put you in a position to not just succeed, but to excel. They'll also ensure that you spend the least amount of effort reworking a site, and the most amount of time improving it and keeping it working. Then, if you later get the opportunity to refresh or even redesign a site like this, you can start from well-segmented HTML and CSS, not a mess of convoluted and style-laden HTML.

When building Web applications with the Google Web Toolkit, using Berkeley DB Java Edition as a persistent data store can reduce project costs significantly.

Unless you've been stuck on a desert island for the past several months, you've undoubtedly heard about Silverlight™, the new cross-browser, cross-platform solution from Microsoft that helps you build rich Internet applications and rich, immersive media experiences in the browser. Version 1.0, which combines a XAML rendering engine with a JavaScript API, shipped in September 2007. Version 2.0, which will enter beta soon, will pair an enhanced XAML engine with a version of the CLR that runs in the browser, a Silverlight version of the Microsoft® .NET Framework Base Class Library (BCL), and a managed API. (That's right: C# in the browser!)

Silverlight 1.0 applications are proliferating on the Web, thanks in part to some of the high-profile companies that adopted it early and helped spread the love. The programming model is simple enough for an experienced developer to begin building Silverlight applications in a matter of hours. What's missing for this still very young platform, however, is that wealth of knowledge and resources that accompanies more mature platforms. I've been developing Silverlight apps for more than a year now and have put together a list of best practices that I and other developers on my team use to build better applications.

A mashup is a technique for building applications that combine data from multiple sources to create an integrated experience. Many mashups available today are hosted as sites on the Internet, providing visual representations of publically available data. This article describes the history and architecture of mashups, and explores how you can create mashups for use in your enterprise. We also impart some wisdom gained from projects with customers and systems integrators who have implemented mashups for the enterprise.

In their article, Porting From Web 1.0 To Rich Internet Applications (RIA), James Ward and Shashank Tiwari walk through replacing a Web 1.0 interface with a rich Adobe Flex user interface.