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; 9:14:22 PM.)
Tips and tricks from Steve Muench on Oracle ADF Framework and JDeveloper IDE

Search blog with Google:
 

Search BC4J JavaDoc:
 

August 2004
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        
Jul   Sep

Get Firefox!

Wednesday, August 18, 2004

When upgrading a JClient-based application from 9.0.3/9.0.4 to JDeveloper 10g, if your application has a custom error handler dialog that does not extend oracle.jbo.uicli.controls.JUErrorHandlerDlg, then you'll need to implement the new oracle.adf.model.binding.DCErrorHandler interface after migration. This new interface, like the existing oracle.jbo.uicli.binding.JUErrorHandler has just a single reportException() method, but it is passed the more generic ADF DCBindingContainer instead of the more specific JClient JUFormBinding. In JClient, since we create instances of JUPanelBindings (which extend JUFormBinding which extends DCBindingContainer), you can safely cast the incoming DCBindingContainer to a JUFormBinding and delegate to your existing reportException() implementation.

This change was required as part of generalizing the previous JClient-only binding objects to work for all types of UI clients in Oracle ADF in a generic way. I've filed a bug to make sure it gets a more prominent mention in the documentation for JDeveloper 10g, release 10.1.2.


8:42:17 AM    



© Copyright 2008 Steve Muench.