Thank you for this very helpful tip! It’s obviously a much easier way to work with shared application modules than what I mention here or in part I.

The JDeveloper team should know, however, that the current doc contradicts it. From Section 10.2.3 of the Fusion Developer’s Guide:

“When viewing a data control usage from the DataBindings.cpx file in the Structure window, do not set the Configuration property to a shared application module configuration. By default, for an application module named AppModuleName, the Property Inspector will list the configurations named AppModuleNameShared and AppModuleNameLocal. At runtime, Oracle ADF uses the shared configuration automatically when you configure an application as a shared application module, but the configuration is not designed to be used by an application module data control usage.”

I take it this is a doc bug?

Edit: Steve has confirmed that this is indeed a mistake in the documentation. Go ahead and use a data control based on the shared configuration to display data and invoke operations for shared application module instances.