Goodbye JBO might mean Goodbye 10g for us

Question

I'm greatly saddened that <jbo> support is being deprecated in JDev 10g...it was ideal for the sort of read-only Plumtree portal gadgets we've been writing for the past 18 months where we could easily pick up portal personal preferences etc and feed those into SetWhereClauseParam bind variables or DataSource whereclause etc...all within a single small JSP. We rarely needed to get involved in overriding Oracle methods etc...it was easily supportable.
I have poured through the ADF bindings documents and I can't understand how we're going to easily upgrade our existing <jbo> based applications. Even developing a new non-Struts ADF application looks like it's going to be a big change for us...much more Java coding, re-training etc.
Does anyone else feel this way?
As a result, I'm seriously looking at alternative technologies to ADF. XSQL and JSTL SQL spring to mind. However, my initial trials with JSTL SQL were disappointing from a performance perspective --- a BC4J VO tuned correctly (fetch size = 100) was almost 10x faster than the equivalent JSTL SQL query; is this also due to db connection times with JSTL?
So some questions:
Is it possible to alter fetch size in JSTL SQL?
Is it possible to retrieve a CLOB ising JSTL SQL?
Thanks
Paul

Answer 1

ADF provides the find mode that makes using view criteria as easy or easier than <jbo:ViewCriteria>.
See this online documentation topic, and its related links:
http://helponline.oracle.com/jdeveloper/help/state?navSetId=jdeveloper&navId=4&vtTopicId=&vtTopicFile=jdeveloper/developing_mvc_applications/adf_pfindmode.html
Declaratively, you can use the built-in "Find" action to toggle the binding container out of find mode. For more surgical control, with a line of code you can control find mode on an individual iterator binding level. Assuming "ctx" is the DataActionContext:
  ctx.getBindingContainer().findIteratorBinding("name").setFindMode(true);You can control whether a given iterator binding will allow find mode to be used on itself or not:
  ctx.getBindingContainer().findIteratorBinding("name").setAllowFindMode(false);You can create multiple iterator bindings over the same underlying view object, so for example one could remain in find mode (allowing the user to continue to see and modify /refine their search criteria) while via the other iterator binding the browse through a table of results produced by the current query-by-example critiera.
Now ADF web and Swing clients all use the same mechanism, as it's a built-in feature of the binding layer instead of being a set of web-specific tags.
I've got it in my queue of things to do to produce some addtional howto's on this topic.