Before You Begin
This blog assumes that you’re familiar with Oracle JET, its custom modules, and overriding the default path/suffix configuration for JET modules so that you can include them as assets in your WebCenter Sites implementation. Otherwise, you may want to begin by reading this blog: Creating Oracle JET Modules as Assets in Oracle WebCenter Sites.
WCS 11g’s Admin and Contributor UIs are built with a version of Dojo that does not support AMD modules out-of-the-box. This means if you’re customizing the UI with Oracle JET modules, you can include requireJS as you would normally for Oracle JET. However, 12c’s version of Dojo does support AMD modules, so you can no longer include requireJS for your Oracle JET modules. (If you try, both Dojo and requireJS declare the “define” and “require” functions, which then conflict with each other and your code breaks.) The solution for 12c is to use Dojo’s module loader instead of requireJS. You shouldn’t have to change your JET modules, you just need to update the Oracle JET and Dojo configurations.
Steps and Examples
In 11g, you used to be able to load an Oracle JET module like this: Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.