Last week, I talked about a couple of tuning opportunities for ADF application modules: Lazy loading and shared application module instances. This week and next, I’m going to talk about a way to tune your application modules that is, in my opinion, even more important: Knowing how and when to adjust your application module pool settings. This week, I’m going to write about what application module pooling is; it’s pretty vital that you understand it before you try to tune it. Next week, in the final post in the ADF BC Tuning series, I’ll provide the actual application module pool tuning tips.
It’s been a while since the last installment of ADF BC Tuning, but it’s time to start it up again. I’ve already posted tips for tuning entity objects, associations, view objects (in three parts), and view links, so now, let’s turn our attention to the last of the major business components: application modules.
As I said last week, we’re shipping to the printers by 8/24. That means pretty much 12-14 hours, 7 days a week until then. Intermittent (at best) blogging until then, I’m afraid. In particular, no post this week.
A bit of news about my next book:
- We finally have a fixed title: Oracle JDeveloper 11g Hanbook: A Guide to Oracle Fusion Web Development.
- We’re planning to ship to the printers by August 24th–less than a month from now!
- The (very serious) plan is that we’ll be on the shelves by October 12–in time for Oracle OpenWorld 2009!
- Although we started writing a long time ago, we’ve checked everything against the most recent (July) release of JDeveloper.
I’m really excited about this book; I think it will be a substantial step up from the last two handbooks in terms of scope and detail.
This week’s post is going to be late again, and it’s not going to be another ADF BC Tuning post. It will, however, be some news about the JDeveloper 11g Handbook.