Extreme Reusability, Part I

As promised, I’m posting of the presentation I’d been hoping to give at the OOW Unconference Methodology Symposium last week, expanded slightly for the more forgiving medium of a blog. As it turns out, it’s expanded substantially more than I thought, so I’m going to divide it into two parts. This week, I’ll talk about the basics of the methodology, its goals, and the two techniques it relies heavily upon. Next week, I’ll talk about the actual development process it specifies.

“Extreme Reusability” (the name is not mine, but rather Chris Muir’s; however, I decided I like it) is an idea for an ADF development methodology for mid-sized teams (generally around 4-20 developers) that I’ve been recently expanding on. Continue reading Extreme Reusability, Part I

RTM, the ADF Edition

Over on the ADF Methodology group, in a thread called ADF Study, we recently talked about ways to get up to speed with ADF. If you’ve been following this blog at all, you’ve probably guessed (from my sheer number of links to them) that I’m a big fan of the various ADF Developer’s Guides. I want to point these guides up a bit, because they’re a massively underused resource, for beginning and even experienced ADF developers.

Continue reading RTM, the ADF Edition

Shared Application Module Instance Tricks, Part II: Displaying Data

This is the second part of a two-part series about undocumented tricks with shared application module instances. Last week, I talked about calling methods (at the application module, view object, or view row level) from shared application module instances. This week, I’m going to talk about displaying data (in a non-LOV context) out of them. If you want a general overview of what shared application module instances are and why I think using them is a good idea (particularly at the application scope), look here.

Continue reading Shared Application Module Instance Tricks, Part II: Displaying Data

From Backing Bean to Managed Bean

What is a backing bean? Getting a consistent answer can be harder than you might think. For example, the NetBeans JSF tutorial claims that the two terms are synonyms. And NetBeans had its origin at Sun, so they ought to know, right? On the other hand, the official Java EE 5 Tutorial says that a backing bean “is a JavaServer Faces managed bean that is associated with the UI components used in a particular page.” That suggests that backing beans are a proper subclass of managed beans. And that’s straight from the horse’s mouth, at java.sun.com.

I think that the distinction made by the Java EE tutorial–that a backing bean is a particular sort of managed bean distinguished by its association with a particular page’s components–is a very useful one. But the tutorial also states that “A typical JavaServer Faces application couples a backing bean with each page in the application.” And that is where we part company.

Continue reading From Backing Bean to Managed Bean

Business Components Without the Business: Part III

Over the last two weeks, I’ve been talking about model layer code to facilitate integration of database-level validation logic into an ADF application. This week, let’s finish off the project by writing the controller-layer code that will turn these custom exceptions into nice, user-friendly error messages. Continue reading Business Components Without the Business: Part III