Naming conventions to consider when using ADF Libraries
By Frank Nimphius on Nov 23, 2010
You use ADF Libraries to reuse ADF artifacts like page templates,
bounded task flows, ADF Business Components and declarative components.
be cautious when developing reusable components to avoid name clashes in Java
classes and packages, as well as duplicate metadata file names.
Section 33.1.1 "Creating Reusable Components" of the "Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework" suggests development teams to agree on a naming convention
"You and your team should decide on the type of repository needed to store the library JARs, where to store them and how to access them. You should consider how to organize and group the library JARs in a structure that fits your organizational needs. You should also consider creating standardized naming conventions so that both creators and consumers of ADF Library JARs can readily identify the component functionality."
It then adds a note about what you can do if the problem of missing naming conventions shows in the middle of a development project.
"Note: If, in the midst of development, you and your team find a module that would be a good candidate for reuse, you can use the extensive refactoring capabilities of JDeveloper to help eliminate possible naming conflicts and adhere to reusable component naming conventions."
Though this note is correct and refactoring is an option. The note is very moderate as I would consider refactoring a worst case scenario. Better is to consider naming conventions up front, for which developers need a heads up: Done with this post.
See the link below for naming conventions proposed by Oracle