How about a document on Anti Patterns?

[Jang Vijay Singh]

This recent discussion (http://groups.google.com/group/adf-methodology/
browse_thread/thread/85789753d19d1aeb)
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
other veterans and it would benefit the community to have a well
vetted ready reference list.
I didn't want to take the liberty of creating a new document without
running it by the group first and also because a lot of the content I
had in mind has a notice that says:
"© Copyright 2008 Steve Muench."

Warm Regards,
JV

[Chris Muir]

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.

Regards,

CM.

[Drikus Britz]

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.

[Michael Koniotiakis]

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
bad practice?

Since nothing is black or white, I feel we need to define in more
detail criteria that will evaluate one pattern against an other. I
could think of:

• Reduce of Quality.
• Reduce of Reusability
• Reduce performance
• Increase of development time
• Increase of complexity
• Generate bugs in combination with other practices or components

So I would suggest for every anti-pattern to define which criteria
make it an anti-pattern, and if possible to suggest a better practice
based on the same criteria.

[JV Singh]

Michael, 

Thanks for your  interest !

>>I am also interested in this and willing to participate.

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. 

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

Definitely not.  There are always multiple ways of achieving something. 

An anti-pattern, however is something that causes a lot of harm (e.g. it makes very hard or impossible to make enhancements with reasonable cost) in addition to the effects you mentioned. 

Effects I had in mind:

1. Reduce your ability to change code easily, add new functionality with minimal cost. etc. 

2. Actually neutralize and negate the benefits offered by the framework because either it is used incorrectly or contrary to how it's meant to be used. 

--
You received this message because you are subscribed to the ADF Enterprise Methodology Group (http://groups.google.com/group/adf-methodology). To unsubscribe send email to adf-methodolo...@googlegroups.com

[Andrejus Baranovskis]

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 - http://andrejusb.blogspot.com/
My JDev/ADF Samples list - http://andrejusb-samples.blogspot.com/

[Michael Koniotiakis]

I uploaded a document Anti-Patterns in ADF with some anti-patterns i
have gathered
Feel free to comment or use it as you wish.

[JV Singh]

Thank you .
My bad I didn't make progress on this till date (new job, new place, work etc. the usual lame excuses).
Your document should be a good start and I know others on this thread also have a great deal of material to share on this. I too will add my observations in this area.

Jang Vijay Singh

2009/12/23 Michael Koniotiakis <mko...@hotmail.com>

[Chris Muir]

Gang, Michael's file can be found under the "Files" section of the ADF
EMG Google Group, or this direct link:

http://adf-methodology.googlegroups.com/web/Anti-Patterns+in+ADF.doc?hl=en&gda=jFJsXEoAAAC5hFkl7zbMYCS-_Udy1Yn8tHu01WNzNywspKROfZH77Zy6oAVglq2U6QQx0N0MQWg1-MxpZvOJ6Oo8d0ccM0RF_e3Wg0GnqfdKOwDqUih1tA&gsc=JuQ_tAsAAAD_as7j0qegI-EID6qjOUzR

Please note Google Groups does not version files, so make sure to keep
backups.

Thanks to Michael for publishing his anti-patterns document.

Cheers,

CM.

[kee thang]

 you can download from the following link

https://sites.google.com/site/oracleemg/adf/files

On Sat, Jul 14, 2012 at 7:45 AM, vikceo <vik...@gmail.com> wrote:

hie

anyone know if this document stil exists somewhere?

--

You received this message because you are subscribed to the ADF Enterprise Methodology Group (http://groups.google.com/group/adf-methodology). To unsubscribe send email to adf-methodolo...@googlegroups.com
 

All content to the ADF EMG lies under the Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by/3.0/). Any content sourced must be attributed back to the ADF EMG with a link to the Google Group (http://groups.google.com/group/adf-methodology).