Comments on: ADF BC Tuning III: View Objects, Part 1

By: Avrom’s Java EE and Oracle ADF Blog :: ADF BC Tuning VIII: Application Modules, Part 2

Mon, 21 Sep 2009 01:39:00 +0000

[...] values of transient view attributes. I talked about turning those last two options on or off here (scroll down to “Controlling Passivation of View Objects”). That way, the state of the [...]

By: Avrom’s Java EE and Oracle ADF Blog :: ADF BC Tuning VII: Application Modules, Part 1

Mon, 14 Sep 2009 05:02:53 +0000

[...] 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 [...]

By: Mücahid Uslu

Mücahid Uslu — Fri, 27 Feb 2009 08:12:57 +0000

Also look at; http://adf.webloji.net

By: Simon Haslam

Simon Haslam — Thu, 11 Dec 2008 09:03:44 +0000

When read-only SQL-based View Objects were first introduced they struck me as being a bit of a workaround – especially since they can’t access the nice hints, renames etc that you create in an EO. Ideally for simplicity I’d prefer VOs to always be based on EOs, however as you say there is still a performance trade-off. The main exception is populating, say, an informational field on a form, where you typically have a single SQL statement (as per your MAX example above) – in that case I reckon it’s definitely better to have a read-only VO than to have a chunk of SQL buried somewhere in the java. Likewise LOVs are probably easier as separate RO VOs as they don’t usually have many columns. Anyway, I’ve been really enjoying these tuning posts Avrom – keep up the great work!

By: Mücahid Uslu

Mücahid Uslu — Fri, 14 Nov 2008 13:26:47 +0000

Thank you.