ADF Enterprise Methodology Group Google Group

Re: [ADF EMG] Re: How about a document on Anti Patterns?

2009-11-06T05:59:33Z

I'm willing to collaborate as well, anti patterns is interesting topic for
me.

Let us know, when started document will be ready.

Andrejus

2009/11/6 JV Singh <jvs...@gmail.com>

--
Oracle ACE Director

My Blog - [link]
My JDev/ADF Samples list - [link]

Re: [ADF EMG] Re: How about a document on Anti Patterns?

2009-11-05T22:28:52Z

Michael,

Thanks for your interest !

Absolutely, just give me some time to put together a starter document, run
it by people whose content I might have borrowed/referred to and then we'll
all get to collaborate and add on it.

bad practice?
Definitely not. There are always multiple ways of achieving something.

Re: How about a document on Anti Patterns?

2009-11-05T18:34:20Z

I am also interested in this and willing to participate.

Yet I feel like we need to define more what anti-patterns are.

The best definition that comes in mind is that:

• It’s a way to implement functionality that has a better way to
implement the same functionality.

But does that mean that if you have a best practice everything else is

Re: How about a document on Anti Patterns?

2009-11-05T12:53:27Z

Also saw on the slide show Andrejus Baronovskis presented he mentioned
quite a couple of things to avoid/stay away from when working with ADF
in a production environment.

Re: How about a document on Anti Patterns?

2009-11-03T23:52:20Z

Hi JV

Great idea. Given a number of members wont be familiar with the
concept of anti patterns nor how they apply to ADF, why don't you
start a discussion based, say, on one of Steve's examples. Drop Steve
an email at the usual Oracle email address to ask permission, I'm sure
he'd love discussion around some of his previous ideas.

How about a document on Anti Patterns?

2009-11-03T11:49:44Z

This recent discussion ([link]
browse_thread/thread/85789753d 19d1aeb)
prompted me to think of another document on common ADF anti-patterns/
bad practices parallel to the Coding Standards document.
I have read some good tips on what *not* to do by Steve Muench and the

Re: [ADF EMG] Re: A new way for post-query (description field) without using the EO or get accessor pls give me your feedback.

2009-11-02T09:30:19Z

I also recommend using a reference entity usage in your view object to
manage reference description data for lookup fields.

I've seen a number of anti-patterns in this area and I'm still trying to
understand what approach would be more efficient than the above one which is
handled automatically for you by the ADF framework but during query as well

Re: A new way for post-query (description field) without using the EO or get accessor pls give me your feedback.

2009-10-31T15:59:59Z

Another advantage to using associations between EOs is storage. This
isn't too bad with a single short description field, but it's
something seriously to consider in queries with a larger number/larger
size of reference columns.

Let's suppose that, instead of a 25-byte department name field, you

Re: DB API-based ADF Business Components

2009-10-31T15:43:46Z

Thanks for the replies. I agree that the ability to post table types
would be useful...but I think it would be pretty hard to do at the
entity object level, at least alone. You might get entity objects to
add themselves (during their DML operations) to some table-like
structure at the transaction level (as opposed to posting directly),

Re: [ADF EMG] Re: A new way for post-query (description field) without using the EO or get accessor pls give me your feedback.

2009-10-31T13:49:38Z

Hi Simon,

We are doing it same as JV Singh describes, through Associations between
EO's.

Regards,
Andrejus

2009/10/31 Simon Haslam <Sim...@veriton.co.uk>

--
Oracle ACE Director

My Blog - [link]
My JDev/ADF Samples list - [link]

Re: [ADF EMG] A new way for post-query (description field) without using the EO or get accessor pls give me your feedback.

2009-10-31T13:41:14Z

just injects into SQL >>statement. For me it works.
Maybe Amir used the wrong kind of 'expression' field.
He needs to check the 'mapped to column or sql' in the VO attribute
properties.
Also check 'selected in query'
Then specify that inline query in the box meant for 'SQL expression' (under
Query Column section)

Re: A new way for post-query (description field) without using the EO or get accessor pls give me your feedback.

2009-10-31T13:37:05Z

Andrejus

I noticed one of the screens in your presentation at OOW had exactly
this kind of behaviour - e.g. once you'd chosen an ID from an LOV on
Requester Provider there was a description field on the main page that
had been populated. How was that done? (if you don't mind me
asking ;-)

Re: [ADF EMG] A new way for post-query (description field) without using the EO or get accessor pls give me your feedback.

2009-10-31T13:35:48Z

It should work through expression, because at the end its the same - it just
injects into SQL statement. For me it works.

However, as JV says, its recommended to follow documented approach with
associations.

Andrejus

2009/10/31 JV Singh <jvs...@gmail.com>

--
Oracle ACE Director

Re: [ADF EMG] A new way for post-query (description field) without using the EO or get accessor pls give me your feedback.

2009-10-31T12:37:25Z

That is something we java people think is okay but the DBA's/performance
folks frown upon. Because your query would have a drastically different and
more expensive explain plan this way.
It might just save the network round trips to the DB but it's still an
inline query and to be avoided as far as possible IMHO.

Re: [ADF EMG] A new way for post-query (description field) without using the EO or get accessor pls give me your feedback.

2009-10-31T12:52:45Z

Hi Andrejus,

Thanks for your reply I was not able to handle the description via
Expression. it seems that is would not accept any sql query
such as
*
select descritption form example_table where example_table.id=
viewquerytable.id*

Thanks,
Amir

On Sat, Oct 31, 2009 at 4:04 PM, Andrejus Baranovskis <