How to Use ADF Client-Side Components: Kaleidoscope ’09 Report III

Two weeks ago, I compared a pair of talks I saw at ODTUG Kaleidoscope 2009, “That’s Rich! Putting a smile on ADF Faces,” by Lucas Jellema, and “Fusion Design Fundamentals,” by Duncan Mills. In particular, I contrasted the two opinions given of ADF Faces RC client-side (that is, Javascript) programming, and came down on Lucas’ side: Adding Javascript to ADF Faces RC applications, though it shouldn’t be overdone, can be very useful, and the usual risks attendant on Javascript programming are significantly mitigated if you develop exclusively to the ADF Faces RC Client-Side API (rather than attempting direct access to/manipulation of the DOM) and understand what validation in Javascript can and can’t do (provide convenience for the user and protection against honest user error and provide real enforcement of data integrity, respectively).

What I didn’t get a chance to do in that post was talk about the actual tips for client-side component manipulation that Lucas provided. I’m going to do this over the next couple of weeks. This week, I’m going to talk about the essentials for doing any client-side component manipulation. Next week, I’ll talk about some specific component manipulation use cases that Lucas went over in his talk.

Continue reading How to Use ADF Client-Side Components: Kaleidoscope ’09 Report III

To Javascript or not to Javascript: Kaleidoscope ’09 Report I

This is an (obviously) late post in a series of posts about ODTUG Kaleidoscope 2009. Monday was the least busy day for me at Kaleidoscope–I only attended two presentations, “That’s Rich! Putting a smile on ADF Faces,” by Lucas Jellema, and “Fusion Design Fundamentals,” by Duncan Mills. But it was perhaps the most thought-provoking of my days there. In fact, I have a full three posts worth of stuff to say about just these two talks. Today, I’m going to talk about a dramatic contrast: the two talks, among other things, represented opposite ends of a debate I consider quite important: the advisability, or lack thereof, of using ADF Faces RC client-side components.

Continue reading To Javascript or not to Javascript: Kaleidoscope ’09 Report I

Vote for my Oracle OpenWorld Presentation on Oracle Mix

So, I submitted a presentation, “The Rich Get Richer: Ultimate RIA with Oracle ADF Faces RC Client-Side Objects” to Oracle OpenWorld 2009, in San Francisco this October. The presentation is about performing tasks that usually require a partial round-trip, such as cascading dropdowns, conditionally visible content, etc., with no server round-trip at all. I talk a bit about this, on a very theoretical level, here (in the section, “Consider a Javascript-Only Solution,”) but I plan to go into considerably more detail, giving practical examples and advice, in the presentation.

The presentation did not make the cut of abstracts selected by Oracle. But if you want to see it at OOW, there’s still a chance! Just vote for the presentation on Oracle Mix (you’ll need to create an Oracle Mix account if you don’t already have one, but it’s free and a good way to meet people in the ADF community).

See you at ODTUG and/or OOW!

Extreme Reusability, Part II

Last week, I introduced the ADF development methodology I’m proposing, “Extreme Reusability,” articulated its goals, and discussed the techniques of “Generalize, Push up, and Customize” and “Think Globally, Deploy Locally” that are critical to the methodology. I didn’t, however, describe the actual…well, methodology, meaning the development cycle prescribed by Extreme Reusability.

Notice I didn’t say the application development lifecycle. That’s because developing under Extreme Reusability, like developing under SOA, isn’t primarily about the creation of standalone applications. You should think of the development cycle for extreme reusability as part of an enterprise-wide effort.

Development under Extreme Reusability involves developing along three separate but interacting (and communicating–communication is absolutely vital under this system) tracks: framework development, service development, and application development. These tracks are assigned to different individuals on the team, in (at a guess–remember this is a proposed methodology) somewhere around a 20-60-20 division for a typical organization’s needs.

Continue reading Extreme Reusability, Part II

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