</component>
	<component name="urlQueue"
		class="org.codelibs.fess.crawler.entity.EsUrlQueue" instance="prototype">
	</component>

	<!-- Service -->
	<component name="urlQueueService"
		class="org.codelibs.fess.crawler.service.impl.EsUrlQueueService">
		<arg>crawlerConfig</arg>
	</component>
	<component name="dataService"
		class="org.codelibs.fess.crawler.service.impl.EsDataService">
		<arg>crawlerConfig</arg>
	</component>

	</component>
	<component name="urlQueue" class="org.codelibs.fess.crawler.entity.UrlQueueImpl" instance="prototype" >
	</component>

	<!-- Service -->
	<component name="urlQueueService" class="org.codelibs.fess.crawler.service.impl.UrlQueueServiceImpl" instance="prototype" >
	</component>
	<component name="dataService" class="org.codelibs.fess.crawler.service.impl.DataServiceImpl" 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).

        when:
        project.components.add(component)

        then:
        project.components.size() == 1

        when:
        binaries.add(b1)
        binaries.add(b2)
        binaries.realizeNow()

        then:
        project.components.size() == 3
        project.components.b1 == b1
        project.components.b2 == b2
    }

    def "assemble task does nothing when no main component"() {

<?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>

		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
		}

<!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>

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;

--

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_

<?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>