Packaging Business Domain Objects for Shared Use?

Question

Hi:
I am trying to figure out how best to package a number of ADF Entity Objects so that they are shared by multiple developers and applications. Reading the JDev documentation it looks like the appropriate method is to create a System Library and place these objects into JAR files in the library. Is this the right approach?
If so, other questions follow. It looks like 10.1.3 has replaced "system libraries" with "extension libraries". True? Regardless, when I go into Tool -> Manage Libraries and choose <New>, the only type of library that is available to create is a "User" one.
Any guidance appreciated.
Johnny Lee

Answer 1

Thanks, Shay. That was the perfect answer to the second part of my question. Michael's post really is awesome. One of the things we are most looking forward to with the production 10.1.3 release is the completion of the documentation. For future reference, I think it would be useful to separate the release schedule of the help text from the application. The value of clear information is much greater than minor bug fixes or feature enhancements, IMHO.
But to the first question, it would still be helpful to hear from folks how they are organizing their ADF components. The small version of this question is whether or not packaging entity objects into jar files in external libraries makes sense. Yes/no?
The larger question (and I admit to showing my inexperience here) has to do with organizing the hierarchical structure of a moderate sized ADF application (Faces & Business Components). We are using CVS as our repository and so far the two developers have been working on separate parts of the application, creating their pieces within JDev and then uploading them into CVS. So CVS has all of these modules that reflect individual JDev projects, but no overall structure of how the different pieces relate to one another. Now we're starting to look at sharing components and it's becoming clear that we need to get a little more organized.
So, some specific questions (for anyone who would like to respond):
1) How do you lay out your ADF application source hierarchies?
2) Do you reflect your package structure within your directory structure?
3) Where do you maintain your hierarchy? If you use version control, are your repository and working copies the only places you keep your source, or do you maintain an external central directory structure?
4) Are there things about structuring an ADF Faces/BC application that are different from standard J2EE applications?
5) Have you found particular posts, articles or examples helpful?
Thanks.
Johnny Lee