|
Difference Between Adding and Importing Business Components
The ADF design time only sees components in packages that are:
- Included in the current project for editing, or
- Imported read-only in the current project from a library.
The implication of adding a package of business components to your JDeveloper project (by adding the packagename.xml file for the package of components named packagename) is that you can edit any aspect if needed using the BC4J wizards, and you see the source code.
The implication of importing a package of business components from a library is that the components are available in the various ADF BC design time wizards to be referred to by editable components in your current project, but you cannot modify the imported components. In fact, the Java source code need not be present in the library JAR file at all (just *.class and *.xml files).
You create a JAR file of ADF BC components using our simple JAR file BC Deployment profile option. You can access that from the right-mouse menu of an application module component by selecting "Business Components Deployment...".
You import a package of ADF BC components by:
- Creating a library for your JAR file on the Libraries tab of your project properties. If you need access to the domains and configuration of those components, make sure to include in the library definition both the *CSMT.jar as well as the *CSCommon.jar files.
- Including that library in your project's library list
- File | Import... | Business Components
- Use the file open dialog to navigate into your library's JAR file and select the packagename.xml file for the package named "packagename" of components from that library that you want to import.
You'll see if you select one of the imported components that you can inspect its properties in the Business Components editors, but everything is greyed out since imported components are not editable in the importing project by design.
NOTE: If you are working in the importing project, and have made updates in the imported project by producing a new JAR file, be aware that those changes will not be "seen" by the importing project until you close it and re-open it.
|
