FLR!!
Fast Lane Reader pattern, "A fast lane reader component directly accesses persistent data using JDBC components, instead of using entity beans. The result is improved performance and less coding"...it really sounds cool, faaaast Lane eh. Using the JDBC driver directly results in better performance, WHAT really >:), big surprise!! But how many Java folks dare to do such a nasty thing, "I need my ejbHome" they all cry... or a better architecture perhaps >:). Ok they suggest that based on a boolean (that's the core pattern :0) they delegate the call to the ejb or directly to dao, using the jdbc driver directly. 'We' have been figthing this problem too when using certain resource's, once we have configured our component in COM+, you say 'I do' to DTC (ok you can tweak some attributes making it a raw configured component). I often just lowered the isolation level in my components(e.i SQL statement) when I needed to boost performance, but still I couldn't bybass the Dispman and his whereabouts. 'We' finally got blessed (ok had this last year, but now it's documented >:)).
What is it with these java zealots (or not), can't they function with out there design patterns ? !! It seems to me they dare not take 1 step without some proven pattern. I am not arguing against design patterns, oh no I enjoy reading about them, but sometimes common sense is perhaps a proven way too. But then again lack of common sense is always a sign of high intelligence, you know :}.
"Those who do not want to imitate anything, produce nothing."
-- Sun Microsystems
