Dive into Oracle ADF

Send me a mail
 Dive into Oracle ADF   Click to see the XML version of this web page.   (Updated: 2/3/2008; 8:11:46 PM.)
Tips and tricks from Steve Muench on Oracle ADF Framework and JDeveloper IDE

Search blog with Google:
 

Search BC4J JavaDoc:
 

January 2003
Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  
Dec   Feb

Get Firefox!

Wednesday, January 29, 2003

I'm taking a train tomorrow to Milan to hear a presentation from an Italian software house that's developed some additional custom application-building frameworks on top of BC4J and JClient to make assembling their databound JClient/Swing user interfaces more declarative. If they tell me I can talk about any of the details, I'll post something here.
6:37:41 PM    



Every network round-trip counts when trying to get the best performance out of your application.When you use view objects that you know will never return more than one row, it's best practice to visit the Tuning panel in the View Object editor and set that view object's Max Fetch Size to 1. This would be the case, for example, for a view object whose WHERE clause was restricting a primary or unique key by a bind variable value. This way, when you fetch your zero or one row, the framework will not attempt to fetch an extra row to see if there are "more rows" to fetch.

While you're on the tuning panel, notice that for View Objects that return a large number of rows, setting the Fetch Size to greater than 1 (the default) can reduce the number of roundtrips to the database by fetching the results in "buckets" of up to "FetchSize" rows at a time.


2:28:09 PM    


I sent a note today to Rod Johnson, author of Expert One-to-One: J2EE Design and Development, asking him permission to include a quote from a section of his book in my BC4J Pet Store whitepaper I'm writing. He graciously said yes. Thanks, Rod!

Rod's book breaks away from the typical books on J2EE and focuses instead on debunking myths and providing a great amount of pragmatic advice on when to use which J2EE technologies, and how to do it in a robust way. It's a book that I wish was published 3-4 years ago! It would have saved a lot of beginning J2EE developers a lot of grief. But it's the kind of book that you can only write after living the technology for years and writing "home" about it with that experience under your belt. Highly recommended.

Users of the BC4J framework will find that many of our design choices in the framework directly implement the pragmatic ideas that Rod so coherently describes in this book. Perhaps even more convincingly and thoroughly than our own documentation, Rod's book describes the underlying motivations for why we've done many of the things the way we have.


1:53:49 PM    


© Copyright 2008 Steve Muench.