"I updated my application module class to extend from a custom superclass, how come BC4J keeps changing the extends clause back to inherit from ApplicationModuleImpl?"
As I try to describe in the Customizing the Framework Behavior section of the BC4J Toy Store whitepaper, one of the biggest benefits of using a framework is that you can extend it. If you build framework extension classes to customize the base ApplicationModuleImpl, ViewObjectImpl, ViewRowImpl, and EntityImpl implementations, then you can tell JDeveloper that you want to use these customized base classes instead of the default ones. However, if you change the default base class of your BC4J components by just editing the extends clause in your Java file, you won't have properly saved this custom base class in the BC4J's component metadata. Instead of just hand-editing the file, visit the "Java" tab in the component editor and click on the (Extends) button. In the dialog that will appear, indicate your preferred base classes. Once saved as part of the components definition, then all BC4J code generation will properly remember your custom base class settings.
You can indicate a permanent change to the defaults BC4J will use by selecting Tools | Preferences... and visiting the Business Components | Base Classes panel. In JDev 9.0.4 and beyond, these preferences can also be set on a per-project level as well.
2:01:12 PM 
|
|
