<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components>
	<component name="dataStoreFactory" class="org.codelibs.fess.ds.DataStoreFactory">
	</component>
	<component name="indexUpdateCallback" class="org.codelibs.fess.ds.callback.IndexUpdateCallbackImpl" instance="prototype">
	</component>

            // Do more stuff...
        }
}
```

When a component is created, the framework tracks its lifecycle. When the test exits, any components that were
created during the test are automatically closed.

### Writing Components

To add a new component, you'll first need to create a top-level folder for your component under the
[components folder](https://github.com/istio/istio/tree/master/pkg/test/framework/components).

<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components>
	<component name="rankFusionProcessor"
		class="org.codelibs.fess.rank.fusion.RankFusionProcessor">
		<postConstruct name="setSeacher">
			<arg>
				<component
					class="org.codelibs.fess.rank.fusion.DefaultSearcher">
				</component>
			</arg>
		</postConstruct>
	</component>

		return true
	}
	if len(i.components) != len(components) {
		return false
	}
	for c := 0; c < len(i.components); c++ {
		if i.components[c].ComponentName() != components[c].ComponentName() {
			return false
		}
		if i.components[c].Namespace() != components[c].Namespace() {
			return false
		}
		if i.components[c].Enabled() != components[c].Enabled() {
			return false
		}

import org.gradle.internal.component.model.AttributeMatcher;
import org.gradle.internal.component.model.ComponentGraphResolveMetadata;
import org.gradle.internal.component.model.GraphSelectionCandidates;
import org.gradle.internal.component.model.GraphVariantSelector;
import org.gradle.internal.component.model.VariantGraphResolveState;
import org.gradle.internal.component.resolution.failure.ResolutionCandidateAssessor;

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE components PUBLIC "-//DBFLUTE//DTD LastaDi 1.0//EN"
	"http://dbflute.org/meta/lastadi10.dtd">
<components namespace="fessCrawler">

	<component class="org.lastaflute.di.naming.StyledNamingConvention">
	</component>

	<!-- Container -->
	<component name="crawlerContainer"
		class="org.codelibs.fess.crawler.container.LastaCrawlerContainer">
	</component>

--

This is an important concept because:

- By default, a variant provides a capability corresponding to the GAV coordinates of its component
- No two variants in a dependency graph can provide the same capability
- Multiple variants of a single component may be selected as long as they provide _different capabilities_

model {
    components {
        custom(ComponentWithValue) {
            valueForBinary = "create-value"
        }
    }
    components {
        custom {
            valueForBinary = "configured-value"
        }
    }
    tasks {
        checkModel(Task) {
            doLast {
                def component = \$.components.custom
                assert component.binaries.size() == 1

    {{< text yaml >}}
    components:
      base:
        enabled: false
      pilot:
        enabled: false
      istiodRemote:
        enabled: true
    values:
      global:
        externalIstiod: true
    {{< /text >}}

    If the remote cluster also serves as the config cluster for the external control plane,
    the `base` component would also be enabled:

    {{< text yaml >}}
    components:
      base:

			<arg>"//*[self::H1 or self::H2 or self::H3]"</arg>
			<arg>true</arg>
		</postConstruct>
	</component>

	<component name="fessFileTransformer" class="org.codelibs.fess.crawler.transformer.FessFileTransformer" instance="singleton">
		<property name="name">"fessFileTransformer"</property>
	</component>

	<component name="fessStandardTransformer" class="org.codelibs.fess.crawler.transformer.FessStandardTransformer" instance="singleton">