ADF Application Naming Conventions for package structures

[luc bors]

Hi all,

I was reading the JHeadstart 11.1.1.3 developers Guide (http://
download.oracle.com/consulting/jhsdevguide1111.pdf) and more
specifically the part on "Packaging JHeadstart-Generated
ViewController Project as ADF Library" and "Defining Java Package
Structure and Other Naming Conventions". In this document there is a
reference to the ADF-EMG adf-coding-standards document "http://
groups.google.com/group/adf-methodology/web/adf-coding-standards".

Combining these three I think that there is something missing in the
naming standards, or at least something that is easily forgotten and
can cause a lot of refactoring headaches. This has been described but
it is not yet clear form the EMG adf coding standards.

As far as I'm concerned, all projects in an ADF application need their
own unique package structure.
If you do not implement this, you will get naming conflicts on for
instance DataBindings.cpx which per application can only exists once
in a package path. Consider the structure below.

nl.amis.technology.view.appone
nl.amis.technology.view.apptwo
nl.amis.technology.view.appthree

In this example, the DataBindings.cpx will be in the same location for
all three projects. When bringing these together in one app you'll
have conflicts.

So if you have two ADF ViewController Projects deployed as ADF Library
come together in a third ADF application make sure that you do as
follows.

nl.amis.technology.appone.view
nl.amis.technology.apptwo.view
nl.amis.technology.appthree.view

In other words, make sure that the path to your project package can be
uniquely identified.
The IDE makes it easy to forget this because you will accept the
defaults most of the time, and the default is the one you used the
last time you created a new Application or Project.

Regards Luc