Server-Side Runtime Binding of Components

Server-side providers are more common, but if you don't need to access the server when you're creating a component, you can use a client-side provider instead.

Set the provider system attribute in the <aura:component> tag of an abstract component or interface to point to the server-side provider Java class.

The syntax of the provider system attribute is provider="java://package.class" where package.class is the fully qualified name for the class.

A Java provider must:

• Include the @Provider annotation above the class definition
• Implement either the ComponentDescriptorProvider or ComponentConfigProvider interface

At runtime, a provider has access to a shell of the abstract component or interface, including any attribute values that have been set. The model isn't constructed yet so you can't access it. The provide() method can examine the attribute values that are set on the component, and return a descriptor of the non-abstract component type that should be used.

1swfobject.registerObject("clippy.codeblock-0", "9");@Provider
2public class SampleDescProvider implements ComponentDescriptorProvider {
3
4    public DefDescriptor<ComponentDef> provide() {
5        DefDescriptor defDesc = null;
6
7        // logic to determine DefDescriptor to set and return.
8
9        return defDesc;
10    }
11}

1swfobject.registerObject("clippy.codeblock-1", "9");@Provider
2public class SampleConfigProvider implements ComponentConfigProvider {
3
4    public ComponentConfig<ComponentDef> provide() {
5        ComponentConfig cmpConfig = null;
6
7        // logic to determine DefDescriptor
8        // and attributes to set.
9
10        return cmpConfig;
11    }
12}