oracle.apps.fnd.applcore.dt
Class ApplcoreDTAddin

java.lang.Object
  oracle.apps.fnd.applcore.dt.ApplcoreDTAddin

All Implemented Interfaces:

Addin

public class ApplcoreDTAddin
extends java.lang.Object
implements Addin

The ApplcoreDTAddin implements a Jdeveloper Addin that can be used to extend the BC4J grammer by a third party. A grammer is nothing but the schema that describes how a BC4J object is represented in XML and some metadata that is provided for that schema that annotates how the object will be described by tooling capabilities an IDE like the Jdeveloper, to edit the Business object.

This addin shows how the base schema published for Property sets by BC4J can be extended and integrated with the XML EF tooling capabilites to be manipualated at design time. All BC4J schemas are defined in the standard BC4J namespace i.e http://xmlns.oracle.com/bc4j. Schema that are intended to be extended provide hooks to allow extension, these hooks are basically in the form of abstract element defintions. So the base schema defines So an extension of the base schema would provide concrete definitions for these abstract elements and substitute this base abstract property element. Since the AbstractProperty is unbounded Any number of concrete definitions can be substituted for this abstract property. See AppsProperties.xsd on how the base abstract property can be substituted. The flexibility of using these substitution elements is they can be defined in any other namespace

So that XML EF tooling capabilities can be able to show the extended properties on the PI, the language extension must be supplmeneted with XML EF metadata. There are 2 ways to provide the metadata

• Annotated Metadata
• Standalone Metadata

Annotated metadata is provided as annotations within the schema. As each element is defined, it can be annotated as to how the XML EF has to interpret the metadata. This is useful if metadata to be defined is fairly small and can be managed within the schema definition itself.

If the metadata is fairly large, standalone metadata files can be registered. So metadata is defined in standalone XML file and registered with BC4J, when the IDE is launched, BC4J ensures that all metadata available in different files is aggregated into a single metadata provider. One point to be aware of here is that you can register only ONE Single metadata file per namespace.

More information on XML EF can be found at XML Editing Framework .

Author:

gordon.hooker

Constructor Summary

ApplcoreDTAddin()

Method Summary

void	initialize() Initialize the addin, when the addin is intialized, the URL's for the schema and metadata are registered with BC4J.
static boolean	isApplcoreRoleEnabled() Is the applications role, or any sub-role loaded? The role is selected by the user at jdev startup.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ApplcoreDTAddin

public ApplcoreDTAddin()

Method Detail

initialize

public void initialize()

Initialize the addin, when the addin is intialized, the URL's for the schema and metadata are registered with BC4J. The standalone metadata file should be registered, only if metadata is to be made available as a separate file. In this case, any annotated metadata defined in the XSD should probably be removed. Should both forms of metadata are provided, it is unpredictable as to which one would be effected.

Specified by:

initialize in interface Addin

isApplcoreRoleEnabled

public static boolean isApplcoreRoleEnabled()

Is the applications role, or any sub-role loaded? The role is selected by the user at jdev startup.

Returns:

true if loaded, false otherwise.