BC4J "common" package

Question

Can someone explain what Java packages get generated automatically by BC4J and why?
I created a new business components package, added a domain to it, and was surprised to see that a new subpackage called "common" had been created containing the domain. Why did JDev create a subpackage instead of using the package I had specified? (I had thought there was a 1-to-1 correspondence between business component packages and Java packages.)
I can't find information about this in the documentation.
Thanks.

Answer 1

We put the following four artifacts in the ".common" subpackage of your BC4J package:
1. bc4j.xcfg configuration file for application modules in your package
2. custom interfaces for view objects, view object rows, or application modules for which you've published client-accessible methods.
3. message bundle classes that BC4J creates for your components
4. domain classes
These are precisely the things that end up getting packaged into the "Common" jar file when you deploy your BC4J application (everything else goes into the "MiddleTier" jar file.
BC4J encourages a logical three-tier design, and when you choose to deploy this logical three-tier application as a physical three tier application, the "Common" Jar file and all of your BC4J components implementations stay on the server.
It's just the "Common" jar file that is required on the remote client tier.
Actually, the things in the "Common" jar file are required on both tiers, thus that are common to both the middle tier and the client tier, hence the choice of the name "common".