Tuesday, February 16, 2010

Books I'm Reading

JavaServer Faces 2.0: the complete reference by Ed Burns, Chris Schalk


Oracle Fusion Developer Guide by Frank Nimphius and Lynn Munsinger

MetaObjectManager scope (I'm listening now...)

I recommend that people working with ADF on JDev 10.1.3 read the MetaObjectManager entry at the following URL: http://blogs.oracle.com/Didier/bc4j/

...especially if you are deploying applications to OC4J and have overridden the DatabaseTransactionFactory... you might have done this if you wanted to do a post-commit or pre-commit type move, as was laid out in the Oracle ADF Developer's Guide for 4GL Developers version

I first noticed when I added this override that, odd crap began to occur with my and others' deployed applications. Essentially they all began trying to use my SAME DatabaseTransactionFactory, which is not what I intended at all. The scope of this AM Module configuration property is something called MetaObjectManager. This means that every app deployed to that same OC4J instance will have the same setting...presuming I was the first one to deploy an app with this property defined in my bc4j.xcfg to that OC4J instance. This is not a smart way to identify a global setting...i.e., hidden in an app.

I am repeating this because, for me at any rate, the topic apparently bares repeating.

Tuesday, February 9, 2010

jdbc calling procedures and DBTransaction isDirty()

Did you know that even if you create a callableStatement from the DBTransaction in your ADF/BC layer and call a database stored procedure, function, package, etc...that; and if that stored program unit that you called does DML and dirty's the transaction, the DBTransaction's isDirty() method will not go to true (unless it was true before the call)?

I did not; but now I do. And now: so do you, dear reader.

Thursday, February 4, 2010


I just noticed that the first four bytes of every Java class file (magic number) that designates that file as a class file spells "cafebabe" in hexadecimal.

Who says geeks don't have a sense of humor.

Wednesday, February 3, 2010

Error Handling and the Binding layer


Jan has beat on the subject of error handling, and I believe Frank Nimphius and Steve Muench have both thrown in their two cents. But I still had some nagging questions, so I pressed him; he did amazing things, and I think I responded pretty well. It was not a bad day all in all.

Check this JDev thread out if you have been wondering about using operation bindings versus calling the app module methods directly.

Op binding/error handling thread on Oracle JDev Technet forum