Dive into Oracle ADF

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

Search blog with Google:

Search BC4J JavaDoc:

October 2008
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  
Sep   Nov

Get Firefox!

Tuesday, October 07, 2008

The production release of JDeveloper / ADF 11g (release build 5156) is now available on OTN from the JDeveloper OTN Home Page, where you'll also find pointers to other resources like new demos, tutorials, the New Features List, and the production ADF 11g Documentation set.

You'll find important information in the Release Notes, so please don't skip reading them.

A new FAQ document anticipates key questions you might have about the new release.

I've updated the Migrating the SRDemo 10.1.3 Sample to ADF 11g migration whitepaper for the production release.

I've also produced a how-to document which explains a shortcut for Simplified ADF 11g Application Credential and Policy Migration to Standalone WebLogic Servers.

Enjoy the new release. Please report any feedback or issues in the JDeveloper discussion forum on OTN.

9:32:48 PM    

Today I was debugging a problem where I wanted to set an exception breakpoint for oracle.jbo.JboException to see what was the first ADFBC-related exception that was occurring. The only problem was that I did not want to stop for the oracle.jbo.NoXMLFileException (subtype of JboException) which the framework will throw when it can't find an optional file like the package XML file in the runtime classpath. Not knowing which subtype of JboException would be thrown, I didn't want to create a ton of different breakpoints for every possible subtype except for NoXMLFileException, so I tried to find a better way. Here's the solution I finally figured out.

I created an exception breakpoint for oracle.jbo.JboException, with a conditional breakpoint expression of:

!( _throw instanceof oracle.jbo.NoXMLFileException )

I got the idea about using the special _throw field because I noticed in the debugger "Data" window that an entry named _throw showed which exception had been thrown. Then I remembered something that a developer on the JDev IDE team told me once, which was "if you can see it in the Data window, you can reference it in a watch expression." So I tried it out, hoping that that maxim also held for the debugger's conditional breakpoint expressions. And it did!

In this way, the debugger avoids stopping if the exception happens to be of the NoXMLFileException subtype, but otherwise will stop for all other subtypes of JboException. I thought it was an interesting trick to share.

1:14:51 PM    

© Copyright 2008 Steve Muench.