mirror of
https://github.com/Alfresco/alfresco-community-repo.git
synced 2025-06-23 18:05:32 +00:00
A set of extracters for different mimetypes can be activated across AVM land. The XML extraction sample has been modified to be AVM-specific, and therefore includes the necessary config to activate the metadata extraction in AVM. git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/HEAD/root@6238 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261
149 lines
5.8 KiB
XML
149 lines
5.8 KiB
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<!DOCTYPE beans PUBLIC '-//SPRING//DTD BEAN//EN' 'http://www.springframework.org/dtd/spring-beans.dtd'>
|
|
|
|
<!--
|
|
Sample configuration of a XmlMetadataExtracter in use within the WCM environment.
|
|
|
|
This show how XML metadata extraction can be set up to extract metadata from different
|
|
formats of XML. It also shows how metadata can be extracted in WCM projects.
|
|
|
|
Since: 2.1
|
|
Author: Derek Hulley
|
|
-->
|
|
<beans>
|
|
|
|
<!--
|
|
In order to limit the number of extractors active for Web Content Management, a separate registry
|
|
must be created for the extractors.
|
|
-->
|
|
<bean id="avmMetadataExtracterRegistry" class="org.alfresco.repo.content.metadata.MetadataExtracterRegistry" />
|
|
|
|
<!--
|
|
Configure the AVM services to broadcast the content update notifications.
|
|
-->
|
|
<bean id="avmNodeService" class="org.alfresco.repo.avm.AVMNodeService" init-method="init">
|
|
<property name="dictionaryService">
|
|
<ref bean="dictionaryService"/>
|
|
</property>
|
|
<property name="avmService">
|
|
<ref bean="avmLockingAwareService"/>
|
|
</property>
|
|
<property name="policyComponent">
|
|
<ref bean="policyComponent"/>
|
|
</property>
|
|
<property name="invokePolicies">
|
|
<value>true</value>
|
|
</property>
|
|
</bean>
|
|
<bean id="avmMetadataExtracter" class="org.alfresco.repo.avm.AvmMetadataExtracter" init-method="init">
|
|
<property name="policyComponent">
|
|
<ref bean="policyComponent"/>
|
|
</property>
|
|
<property name="extracterAction">
|
|
<bean class="org.alfresco.repo.action.executer.ContentMetadataExtracter" >
|
|
<property name="dictionaryService">
|
|
<ref bean="dictionaryService"/>
|
|
</property>
|
|
<property name="nodeService">
|
|
<ref bean="avmNodeService" />
|
|
</property>
|
|
<property name="contentService">
|
|
<ref bean="contentService" />
|
|
</property>
|
|
<property name="metadataExtracterRegistry">
|
|
<ref bean="avmMetadataExtracterRegistry" />
|
|
</property>
|
|
</bean>
|
|
</property>
|
|
</bean>
|
|
|
|
<!--
|
|
Configure an extractor that targets Alfresco Model XML files.
|
|
Although this inherits from the base extracter bean, the use of the 'init' method
|
|
means that it isn't automatically registered.
|
|
-->
|
|
<bean id="extracter.xml.sample.AlfrescoModelMetadataExtracter"
|
|
class="org.alfresco.repo.content.metadata.xml.XPathMetadataExtracter"
|
|
parent="baseMetadataExtracter"
|
|
init-method="init" >
|
|
<property name="mappingProperties">
|
|
<!--
|
|
The properties can also be specified using a properties file on the classpath, e.g.:
|
|
<bean class="org.springframework.beans.factory.config.PropertiesFactoryBean">
|
|
<property name="location">
|
|
<value>classpath:alfresco/extension/xml-metadata/AlfrescoModel-xpath-mappings.properties</value>
|
|
</property>
|
|
</bean>
|
|
-->
|
|
<bean class="org.springframework.beans.factory.config.PropertiesFactoryBean">
|
|
<property name="properties">
|
|
<props>
|
|
<prop key="namespace.prefix.cm">http://www.alfresco.org/model/content/1.0</prop>
|
|
<prop key="author">cm:author</prop>
|
|
<prop key="title">cm:title</prop>
|
|
<prop key="description">cm:description</prop>
|
|
</props>
|
|
</property>
|
|
</bean>
|
|
</property>
|
|
<property name="xpathMappingProperties">
|
|
<bean class="org.springframework.beans.factory.config.PropertiesFactoryBean">
|
|
<property name="properties">
|
|
<props>
|
|
<prop key="namespace.prefix.fm">http://www.alfresco.org/model/forum/1.0</prop>
|
|
<prop key="author">/model/author/text()</prop>
|
|
<prop key="title">/model/@name</prop>
|
|
<prop key="description">/model/description/text()</prop>
|
|
<prop key="version">/model/version/text()</prop>
|
|
</props>
|
|
</property>
|
|
</bean>
|
|
</property>
|
|
</bean>
|
|
|
|
<!--
|
|
This selector examines the XML documents, executing the given XPath statements until a
|
|
match is made.
|
|
-->
|
|
<bean
|
|
id="extracter.xml.sample.selector.XPathSelector"
|
|
class="org.alfresco.repo.content.selector.XPathContentWorkerSelector"
|
|
init-method="init">
|
|
<property name="workers">
|
|
<map>
|
|
<entry key="/my:test">
|
|
<null />
|
|
</entry>
|
|
<entry key="/model">
|
|
<ref bean="extracter.xml.sample.AlfrescoModelMetadataExtracter" />
|
|
</entry>
|
|
</map>
|
|
</property>
|
|
</bean>
|
|
|
|
<!--
|
|
This is the face of the XML metadata extraction. If passes the XML document to each of
|
|
the selectors, until one of them gives back a MetadataExtracter (via the selectors),
|
|
which is then used as normal to extract the values.
|
|
Note the use of the AVM-specific registry.
|
|
The overwrite policy of the embedded extracters has no effect. It is only this extractor's
|
|
policy that is used.
|
|
-->
|
|
<bean
|
|
id="extracter.xml.sample.XMLMetadataExtracter"
|
|
class="org.alfresco.repo.content.metadata.xml.XmlMetadataExtracter"
|
|
parent="baseMetadataExtracter">
|
|
<property name="registry">
|
|
<ref bean="avmMetadataExtracterRegistry" />
|
|
</property>
|
|
<property name="overwritePolicy">
|
|
<value>EAGER</value>
|
|
</property>
|
|
<property name="selectors">
|
|
<list>
|
|
<ref bean="extracter.xml.sample.selector.XPathSelector" />
|
|
</list>
|
|
</property>
|
|
</bean>
|
|
|
|
</beans> |