alfresco 2.0 解讀
一、介紹
<a href="http://www.alfresco.com/">http://www.alfresco.com</a>
alfresco is the open source alternative for enterprise content management (ecm), providing document management, collaboration, records management, knowledge management, web content management and imaging.
采用的技術
java
spring aspect-oriented framework
acegi – aspect-oriented security framework
myfaces jsf implementation
hibernate orm persistence
lucene text search engine
jlan
poi file format conversion
pdfbox – pdf conversion
openoffice
jbpm
rhino javascript engine
支援的接口
cifs/smb microsoft file share protocol
jsr-168 portlet specification
jsr-127 java server faces
ftp
webdav
web services
rest
二、配置解讀
1、從web.xml開始入手
其它的略過，在 web.xml 中可以看到加載了如下 spring 配置檔案
<context-param>
<param-name>contextconfiglocation</param-name>
<param-value>
classpath:alfresco/web-client-application-context.xml
classpath:web-services-application-context.xml
classpath:alfresco/web-api-application-context.xml
classpath:alfresco/application-context.xml
</param-value>
<description>spring config file locations</description>
</context-param>
web client 層
alfresco/web-client-application-context.xml
打開它可以看到它引入了所有的 alfresco/web-client*.xml & alfresco/extension/web-client*.xml & jar:*!/meta-inf/web-client*.xml
web api 層
alfresco/web-api-application-context.xml
打開它可以看到它引入了 alfresco/web-api-config.xml & alfresco/extension/web-api-config-custom.xml
web service 層
web-services-application-context.xml
剛開始找這個檔案時，居然沒有找到，怪事！not exist???why?
于是後來才發現這個檔案是在 remote-api.jar 包裡，暈，不是很好的做法啊。
bean 配置定義關鍵的檔案
alfresco/application-context.xml
<import resource="classpath:alfresco/core-services-context.xml"/>
<import resource="classpath:alfresco/public-services-context.xml"/>
<import resource="classpath:alfresco/model-specific-services-context.xml"/>
<import resource="classpath:alfresco/action-services-context.xml"/>
<import resource="classpath:alfresco/rule-services-context.xml"/>
<import resource="classpath:alfresco/node-services-context.xml"/>
<import resource="classpath:alfresco/scheduled-jobs-context.xml"/>
<import resource="classpath:alfresco/network-protocol-context.xml"/>
<import resource="classpath:alfresco/content-services-context.xml"/>
<import resource="classpath:alfresco/hibernate-context.xml"/>
<import resource="classpath:alfresco/ownable-services-context.xml"/>
<import resource="classpath:alfresco/template-services-context.xml"/>
<import resource="classpath:alfresco/script-services-context.xml"/>
<import resource="classpath:alfresco/index-recovery-context.xml"/>
<import resource="classpath:alfresco/authority-services-context.xml"/>
<import resource="classpath:alfresco/authentication-services-context.xml"/>
<import resource="classpath:alfresco/policy-context.xml"/>
<import resource="classpath:alfresco/import-export-context.xml"/>
<import resource="classpath:alfresco/bootstrap-context.xml"/>
<import resource="classpath:alfresco/workflow-context.xml"/>
<import resource="classpath:alfresco/jcr-api-context.xml"/>
<import resource="classpath:alfresco/avm-services-context.xml"/>
<import resource="classpath:alfresco/audit-services-context.xml"/>
<import resource="classpath*:alfresco/patch/*-context.xml"/>
<import resource="classpath*:alfresco/domain/*-context.xml"/>
<!--
import all modules and related components.
extensions are explicitly imported after this so that the default
mechanism can still be used to override module-specific beans.
-->
<import resource="classpath*:alfresco/module-context.xml"/>
import of general extensions and bean overrides.
to give developers final control over the tuning
of their own local build, the dev-context.xml file
is processed last (note: dev-context.xml isn't
part of the source tree itself).
for details, see:
http://wiki.alfresco.com/wiki/developer_runtime_configuration
<import resource="classpath*:alfresco/extension/*-context.xml"/>
<import resource="classpath*:alfresco/extension/dev-context.xml"/>
可以看到分層次地進行加載不同的 bean ，并且在後面提供可擴充的 bean 定義的引入，友善進行擴充，而不需要更變這個配置檔案
繼續一個個往下看，并把一些重要的 bean 配置拿出來：
core-services-context.xml 核心 bean 的配置
看到配置了 jmx 的服務
<!-- custom mbeanserver -->
<bean id="alfrescombeanserver" class="org.springframework.jmx.support.mbeanserverfactorybean"/>
<bean id="registry" class="org.springframework.remoting.rmi.rmiregistryfactorybean">
<property name="port" value="${avm.remote.port}"/>
</bean>
<!-- mbeanserver connector (registers itself with custom alfrescombeanserver) -->
<bean id="serverconnector"
class="org.springframework.jmx.support.connectorserverfactorybean"
depends-on="registry">
<property name="server" ref="alfrescombeanserver"/>
<property name="objectname" value="connector:name=rmi"/>
<property name="serviceurl" value="service:jmx:rmi://localhost/jndi/rmi://localhost:${avm.remote.port}/alfresco/jmxrmi"/>
<property name="environment">
<map>
<!-- the following keys are only valid when sun jmx is used -->
<entry key="jmx.remote.x.password.file" value="${alfresco.jmx.dir}/alfresco-jmxrmi.password"/>
<entry key="jmx.remote.x.access.file" value="${alfresco.jmx.dir}/alfresco-jmxrmi.access"/>
</map>
</property>
<!-- mbeans registered with alfrescombeanserver -->
<bean id="virtserverregistry"
class="org.alfresco.mbeans.virtserverregistry"
init-method="initialize">
jmx 服務暴露
<bean id="exporter" class="org.springframework.jmx.export.mbeanexporter">
<property name="server" ref="alfrescombeanserver"/>
<property name="beans">
<map>
<!-- mbeans to register with alfrescombeanserver -->
<entry key="alfresco:name=virtserverregistry,type=virtserverregistry" value-ref="virtserverregistry"/>
<entry key="alfresco:name=fileserverconfig,type=fileserverconfig" value-ref="fileserverconfig"/>
</map>
</property>
同時暴露了 rmi 的服務
rmi
<!-- the rmi export of the repo remote transport. -->
<bean id="reporemotetransportrmi" class="org.springframework.remoting.rmi.rmiserviceexporter">
<property name="service">
<ref bean="reporemotetransport"/>
</property>
<property name="serviceinterface">
<value>org.alfresco.service.cmr.remote.reporemotetransport</value>
<property name="servicename">
<value>repo</value>
<property name="registryport">
<value>${avm.remote.port}</value>
驗證 bean 配置，也是同時暴露了 rmi 的服務
authentication-services-context.xml
<!-- here for now. probably want remote-context.xml file. -->
<!-- the authenticationservice exported as an rmi service. -->
<bean id="rmiauthenticationservice" class="org.springframework.remoting.rmi.rmiserviceexporter">
<ref bean="authenticationservice"/>
<value>org.alfresco.service.cmr.security.authenticationservice</value>
<value>authentication</value>
avm 裡也暴露了 rmi 的服務
avm-services-context.xml
<!-- the rmi wrapper around the avm remote interface. -->
<bean id="avmremoteservice" class="org.springframework.remoting.rmi.rmiserviceexporter">
<ref bean="avmremotetransport"/>
<value>org.alfresco.service.cmr.remote.avmremotetransport</value>
<value>avm</value>
<bean id="avmsyncservicetransport" class="org.alfresco.repo.avm.avmsyncservicetransportimpl">
<property name="authenticationservice">
<ref bean="authenticationservice"/>
<property name="avmsyncservice">
<ref bean="avmsyncservice"/>
<bean id="avmsyncservicetransportrmi" class="org.springframework.remoting.rmi.rmiserviceexporter">
<property name="service">
<ref bean="avmsyncservicetransport"/>
<property name="serviceinterface">
<value>org.alfresco.service.cmr.remote.avmsyncservicetransport</value>
<property name="servicename">
<value>avmsync</value>
<property name="registryport">
<value>${avm.remote.port}</value>
通過上面的 jmx 與 rmi 暴露在不同的配置檔案裡可以看到，如果我要去掉 jmx 或 rmi 服務的話，需要修改 n 個的配置檔案，實在是麻煩。
建議要二次開發時根據需要進行整理，合并到一個檔案裡進行暴露即可，或者沒有需要的話就直接 delete 掉這些：）
而且這個 jmx rmi 服務的暴露，導緻你不能僅重新開機應用就可以，而非得重新開機整個應用伺服器才行，要不然會報服務已啟動，即預設的端口50500被占用了，而整個應用啟動不了，麻煩。除非你在重新開機應用之前再去修改一下配置檔案裡的端口号，呵呵。
不過，最終的解決辦法是象我在 jmx4log4j 裡那樣自己去再封裝一個擷取端口号的類，發現有人用了，就找下一個：）這樣就ＯＫ了。
core-services-context.xml
<!-- datasource bean -->
資料庫連接配接池用的居然是 org.apache.commons.dbcp.basicdatasource ，大家自己改吧 c3p0 等等
郵件
<!-- mail service -->
<bean id="mailservice" class="org.springframework.mail.javamail.javamailsenderimpl">
lucene 索引和搜尋 api
<!-- indexing and search api -->
<bean id="indexercomponent" class="org.alfresco.repo.search.indexercomponent">
<bean id="searchservice" class="org.alfresco.repo.search.searchercomponent">
<!-- indexer and searchers for lucene -->
<bean id="luceneindexerandsearcherfactory"
class="org.alfresco.repo.search.impl.lucene.luceneindexerandsearcherfactory2">
<bean id="lucenecategoryservice" class="org.alfresco.repo.search.impl.lucene.lucenecategoryserviceimpl">
鎖
<!-- lock service -->
<bean id="lockservice" class="org.alfresco.repo.lock.lockserviceimpl" init-method="initialise">
版本控制
<!-- version service -->
<bean id="versionservice" class="org.alfresco.repo.version.versionserviceimpl" init-method="initialise">
資料庫
<!-- data dictionary -->
<bean id="dictionarybootstrap" parent="dictionarymodelbootstrap" depends-on="resourcebundles">
<property name="models">
<list>
<!-- system models -->
<value>alfresco/model/dictionarymodel.xml</value>
<value>alfresco/model/systemmodel.xml</value>
<value>org/alfresco/repo/security/authentication/usermodel.xml</value>
<!-- content models -->
<value>alfresco/model/contentmodel.xml</value>
<value>alfresco/model/bpmmodel.xml</value>
<value>alfresco/model/wcmmodel.xml</value>
<value>alfresco/model/forummodel.xml</value>
<!-- content models -->
<value>alfresco/model/applicationmodel.xml</value>
<value>alfresco/model/wcmappmodel.xml</value>
<!-- implementation models -->
<value>org/alfresco/repo/action/actionmodel.xml</value>
<value>org/alfresco/repo/rule/rulemodel.xml</value>
<value>org/alfresco/repo/version/version_model.xml</value>
<!-- deprecated types -->
<value>alfresco/model/deprecated/deprecated_contentmodel.xml</value>
</list>
</property>
<property name="labels">
<value>alfresco/model/datatypeanalyzers</value>
<value>alfresco/messages/system-model</value>
<value>alfresco/messages/dictionary-model</value>
<value>alfresco/messages/content-model</value>
<value>alfresco/messages/bpm-messages</value>
<value>alfresco/messages/application-model</value>
<value>alfresco/messages/forum-model</value>
</bean>
拷貝
<!-- copy service -->
<!-- note this uses the node service that enforces permissions so you can only copy what you can see -->
<bean id="copyservice" class="org.alfresco.repo.copy.copyserviceimpl" init-method="init">
檢出 / 檢入
<!-- checkout/checkin service -->
<bean id="checkoutcheckinservice" class="org.alfresco.repo.coci.checkoutcheckinserviceimpl">
全文搜尋
<!-- bean to support full text search -->
<bean id="lucenefulltextsearchindexer"
class="org.springframework.transaction.interceptor.transactionproxyfactorybean">
lucene 索引檔案備份
<!-- bean to backup lucene indexes -->
<bean id="luceneindexbackupcomponent"
class="org.alfresco.repo.search.impl.lucene.luceneindexerandsearcherfactory2$luceneindexbackupcomponent">
<!-- registry service -->
<bean id="registryservice" class="org.alfresco.repo.admin.registry.registryserviceimpl" init-method="init">
<!-- a simple filesystem like api for the repo implementation.
unfinished, experimental, and probably ephemeral. -->
<bean id="reporemoteservice" class="org.alfresco.repo.remote.reporemoteservice">
<!-- transactionally wrapped version of above. -->
<bean id="reporemoteservice" class="org.springframework.transaction.interceptor.transactionproxyfactorybean">
public-services-context.xml
當中引入了
<import resource="classpath:alfresco/public-services-security-context.xml"/>
public-services-security-context.xml 安全認證相關
使用的是 acegi 元件，當中引入了
<import resource="classpath:alfresco/cache-context.xml" />
cache-context.xml cache 相關的，使用的是 ehcache
<bean name="transactionalehcachemanager" class="org.alfresco.repo.cache.ehcachemanagerfactorybean">
<property name="configlocation">
<value>classpath:alfresco/ehcache-transactional.xml</value>
</property>
</bean>
<!-- service registry -->
<bean id="serviceregistry" class="org.alfresco.repo.service.servicedescriptorregistry"/>
基本上服務都從這裡注入并從中擷取，樹結構，當中有spring bean factory
model-specific-services-context.xml
<!-- file/folder specific service -->
<bean name="filefolderservice" class="org.alfresco.repo.model.filefolder.filefolderserviceimpl" init-method="init">
<bean name="tempfilemarkerinterceptor" class="org.alfresco.repo.model.filefolder.tempfilemarkerinterceptor">
<!-- multilingual specific service -->
<bean name="multilingualcontentservice" class="org.alfresco.repo.model.ml.multilingualcontentserviceimpl">
action-services-context.xml action 相關的
用 thread local containing the current action chain
<!-- action service -->
<bean id="actionservice" class="org.alfresco.repo.action.actionserviceimpl">
rule-services-context.xml 規則、觸發規則服務
<!-- rules service -->
<bean id="ruleservice" class="org.alfresco.repo.rule.ruleserviceimpl">
<!-- rules aspect -->
<bean id="rulesaspect" class="org.alfresco.repo.rule.rulesaspect" init-method="init">
<!-- rule triggers -->
<bean id="rule-trigger-base" abstract="true" init-method="registerruletrigger">
node-services-context.xml 節點相關服務
<!-- beans pertinent to node persistence and services -->
scheduled-jobs-context.xml 定時任務
<!-- task scheduler -->
<!-- triggers should not appear here - the scheduler should be injected into the trigger definition -->
<!-- this bean should not need to apear else where in extension configuration -->
<bean id="schedulerfactory" class="org.springframework.scheduling.quartz.schedulerfactorybean">
<property name="waitforjobstocompleteonshutdown">
<value>true</value>
<property name="configlocation">
<value>classpath:alfresco/domain/quartz.properties</value>
<property name="schedulername">
<value>defaultscheduler</value>
# quartz thread settings 預設的線程優先級為 3
org.quartz.threadpool.threadpriority=3
network-protocol-context.xml 網絡相關的服務
需要相關的檔案配置資訊在 file-servers.xml 中
content-services-context.xml 内容相關的服務
mime openoffice pdf mail mp3 ...
hibernate-context.xml hibernate 的映射配置檔案
<!-- load hibernate configuration properties -->
<bean id="hibernateconfigproperties" class="org.springframework.beans.factory.config.propertiesfactorybean">
<property name="locations">
<list>
<value>classpath:alfresco/domain/hibernate-cfg.properties</value>
</list>
<!-- load hibernate entity cache strategies -->
<bean id="cachestrategiesplaceholderconfigurer" class="org.springframework.beans.factory.config.propertyplaceholderconfigurer">
<property name="ignoreunresolvableplaceholders">
<value>classpath:alfresco/domain/cache-strategies.properties</value>
<!-- hibernate session factory -->
<bean id="sessionfactory" class="org.springframework.orm.hibernate3.localsessionfactorybean" parent="sessionfactorybase">
<property name="datasource">
<ref bean="datasource"/>
<bean id="sessionfactorybase" abstract="true">
<property name="hibernateproperties" ref="hibernateconfigproperties"/>
不同的cache政策
<property name="entitycachestrategies">
<property name="collectioncachestrategies">
ownable-services-context.xml
ownership service support. use in permissions framework as dynamic authority.
<bean id="ownableservice" class="org.alfresco.repo.ownable.impl.ownableserviceimpl">
template-services-context.xml 模闆引擎 freemarker
script-services-context.xml 腳本引擎 rhino javascript engine.
index-recovery-context.xml 索引校驗與恢複
<!-- index recovery and validation -->
<!--
recovery types are:
none: ignore
validate: checks that the last transaction for each store is represented in the indexes
auto: validates and auto-recovers if validation fails
full: full index rebuild, processing all transactions in order. the server is temporarily suspended.
-->
<bean
id="indexrecoverycomponent"
class="org.alfresco.repo.node.index.fullindexrecoverycomponent"
parent="indexrecoverycomponentbase">
<property name="recoverymode">
<value>${index.recovery.mode}</value>
</property>
<!-- bean that attempts to index content that was previously missing -->
id="missingcontentreindexcomponent"
class="org.alfresco.repo.node.index.missingcontentreindexcomponent"
authority-services-context.xml 授權服務
<!-- the configuration of the authority service implementation -->
<!-- this implementation supports the identification of users as admin users. -->
<!-- it also supports groups and allows groups and users to be arranged into -->
<!-- hierarchies. -->
<bean id="authorityservice" class="org.alfresco.repo.security.authority.authorityserviceimpl">
<!-- a list of users with admin rights. -->
<!-- -->
<!-- if the security framework is case sensitive these values should -->
<!-- be case sensitive user names. if the security framework is not -->
<!-- case sensitive these values should be the lower-case user names. -->
<!-- -->
<!-- by default this includes: -->
<!-- admin (the user name of default alfresco admin user) -->
<!-- administrator (the windows default admin user) -->
<!-- this assumes that user names are not case sensitive. -->
<property name="adminusers">
<set>
<value>admin</value>
<value>administrator</value>
</set>
<!-- authority dao that stores group information along with user information, -->
<!-- in the repository. -->
<!-- -->
<!-- this bean uses the usertoauthoritycache configured in cache-context.xml -->
<bean id="authoritydao" class="org.alfresco.repo.security.authority.authoritydaoimpl">
authentication-services-context.xml 驗證 acegi
<!-- this file contains the bean definitions that support authentication -->
policy-context.xml 政策服務
<!-- policy support -->
import-export-context.xml 導入導出服務
bootstrap-context.xml 系統啟動的初始化工作
如：資料庫、avm、檔案伺服器、ftp、nfs、cifs等等。。。
repository bootstrap sequence.
<!-- ensure that the schema is bootstrapped -->
<bean id="schemabootstrap" class="org.alfresco.repo.domain.schema.schemabootstrap">
<property name="localsessionfactory">
<ref bean="&amp;sessionfactory"></ref> <!-- inject the actual factory, not a session -->
workflow-context.xml 工作流相關的服務，jbpm
<!-- workflow service implementation -->
jcr-api-context.xml 實作jcr 170相關的api，即1.0版本的api
alfresco implementation of a jcr repository
avm-services-context.xml avm相關服務，以及一堆的dao
<!-- id issuers. -->
<!-- daos for persistent data types -->
<!-- issuers are not actual entities. more like pseudo entities. -->
avm-console-context.xml
<!-- use substitution values in this config. -->
avm-console.properties 預設配置為本地mysql的資料庫
# database specifics.
db.driver=org.gjt.mm.mysql.driver
db.url=jdbc:mysql://127.0.0.1/avm
db.username=root
db.password=
db.pool.initial=4
db.pool.max=32
# hibernate properties
hibernate.dialect=org.hibernate.dialect.mysqlinnodbdialect
hibernate.current_session_context_class=thread
hibernate.connection.isolation=2
hibernate.default_batch_fetch_size=16
hibernate.jdbc.batch_versioned_data=true
hibernate.cache.use_second_level_cache=true
hibernate.hbm2ddl.auto=update
# avm specific properties.
<import resource="file:config/alfresco/avm-base-context.xml"/>
audit-services-context.xml
<!-- base audit service - non tx -->
<bean id="auditservice" class="org.alfresco.repo.audit.auditserviceimpl">
<property name="auditcomponent">
<ref bean="auditcomponent"/>
<!-- audit component -->
<bean id="auditcomponent" class="org.alfresco.repo.audit.auditcomponentimpl">
其後在 application-context.xml 還加載了
<import resource="classpath*:alfresco/patch/*-context.xml"/>一堆patch，呵呵
patch-services-context.xml
<import resource="classpath*:alfresco/domain/*-context.xml"/>其它的。。。
<import resource="classpath*:alfresco/module-context.xml"/>
module-context.xml 加載其它的子產品bean
最後加載一些擴充與二次開發的bean
<import resource="classpath*:alfresco/extension/*-context.xml"/>
<import resource="classpath*:alfresco/extension/dev-context.xml"/>
同時覆寫掉想覆寫的bean，後面覆寫前面的，map嘛。比如： custom-repository-context.xml 裡的屬性配置、資源配置、事務配置等
三、配置安裝時的注意事項
1、要将 alfresco 預設安裝使用的資料庫hsql轉換為mqsql的話，隻需要删掉三個 hsql 使用的檔案：
這三個檔案分别是 tomcat/shared/classes/alfresco/extension 目錄下的
custom-db-and-data-context.xml
custom-db-connection.properties
custom-hibernate-dialect.properties
為了産生一個mysql資料庫，執行 <alfresco_installation_folder>/extra/database/mysql ，運作 db_setup.bat 檔案，或者打開檔案，手工輸入指令也一樣。
就會産生一個與一個使用者一起命名 alfresco 的 mysql 資料庫帳戶和一個 alfresco 的密碼。
2、國際化
alfresco的檔案路徑為： web-inf/classes/alfresco/messages 下面包含了一堆檔案，一個個去國際化吧，當然用插件、native2ascii或配合ant都可以。
eclipse 的 propertieseditor 插件不錯。
3、無論從一種資料庫切換到另一種資料庫，都要記得把 repository.properties 配置檔案裡 dir.root 所在的目錄下的檔案删除幹淨，要不然會出問題。
比如：caused by: org.alfresco.repo.search.searcherexception: more than one root node in index: 2
#dir.root=./alf_data
4、将 win32netbios.dll 拷貝到 %java_home%/jre/bin/ 目錄下 或者 %tomcat_home%/bin 目錄下
5、不要 scriptservice 的話，可以在 public-services-context.xml 中
注釋掉 scriptservice 和 scriptservice_transaction
<!-- script service -->
<bean id="scriptservice" class="org.springframework.aop.framework.proxyfactorybean">
...
<bean id="scriptservice_transaction" class="org.springframework.transaction.interceptor.transactioninterceptor">
6、檢視 hibernate 的 sql
修改 log4j.properties
在 log4j.logger.org.hibernate 下增加一行，即可
log4j.logger.org.hibernate.sql=debug
7、發現啟動報 "ensure that the 'dir.root' property is pointing to the correct data location." ... 之類的錯誤時可以在 repository.properties 配置檔案裡将 strict 設定為 false
# change the failure behaviour of the configuration checker
system.bootstrap.config_check.strict=false
不過，設定後很有可能可以啟動，但是仍是登入不了之類的，要小心。
如果用的是hsql的話，最好把 alf_data/hsql_data 下面的 alfresco.properties 和 alfresco.script 恢複成原來的，并删除其它的檔案，再重新開機就可以了。
8、第 7 條，仍報錯 error [repo.admin.configurationchecker] content integrity error: indexes not found for 5 stores. 的話，設定為全部索引，并按第 3 條所說的删除檔案，或者直接就換個檔案夾，不要用預設的檔案夾名稱，并删除資料庫的内容（所有的表以及hibernate_sequence），并重新開機即可。
在 repository.properties 中設定
index.recovery.mode=full
9、如果是強行關閉掉tomcat之類後，馬上啟動tomcat的話，有可能會報錯
ioexception while loading persisted sessions: java.io.writeabortedexception: writing aborted; java.io.notserializableexception: org.alfresco.web.ui.common.component.uilistitem
過一會兒再啟動就沒有問題了。
10、alfresco 2.0 需要 jdk 1.5_07 以上的版本，這個也要注意。
11、使用者名大小字問題，可以在 repository.properties 進行設定
# are user names case sensitive?
user.name.casesensitive=true
設定為 true ，大小寫敏感，預設為 false
12、關閉ftp服務，在 bootstrap-context.xml 配置中注釋掉它就可以了。file-servers.xml裡儲存相關的配置資訊
<!-- ftp server -->
<bean id="ftpserver" class="org.alfresco.filesys.ftpserver" destroy-method="stopserver">
<constructor-arg>
<ref local="fileserverconfiguration"/>
</constructor-arg>
或者也可以在 file-servers.xml 檔案中設定 <serverenable enabled="false"/>
13、關閉cifs服務
在 file-servers.xml 檔案中設定 <serverenable enabled="false"/> 即可。
四、資料庫模型
可以看附件，有包含jbpm的與不包含jbmp的兩個資料庫
五、相關資料
java content repository api 簡介 學習 jsr-170 如何使建構 cma 變得輕而易舉
<a href="http://www.ibm.com/developerworks/cn/java/j-jcr/">http://www.ibm.com/developerworks/cn/java/j-jcr/</a>
國外廠商紛紛投入開源界 自述其中原因，此文重點介紹 alfresco 的相關資訊。
<a href="http://dotnet.csdn.net/n/20060206/86350.html">http://dotnet.csdn.net/n/20060206/86350.html</a>
六、開發與代碼分析
1、換 web services 的實作方式由 axis 換到 xfire
codehaus xfire is a next-generation java soap framework. codehaus xfire makes service oriented development approachable through its easy to use api and support for standards. it is also highly performant since it is built on a low memory stax based model.
==============================================================
代碼分析有時間再繼續整理上來
category由id,title,description組成
public category(org.alfresco.webservice.types.reference id,java.lang.string title,java.lang.string description)
classification
public classification(java.lang.string classification,org.alfresco.webservice.types.category rootcategory,java.lang.string title,java.lang.string description)
reference
public reference(org.alfresco.webservice.types.store store,java.lang.string uuid,java.lang.string path)
appliedcategory
public appliedcategory(java.lang.string classification,org.alfresco.webservice.types.reference[] categories)
classdefinition
public classdefinition(java.lang.string name,java.lang.string title,java.lang.string description,java.lang.string superclass,boolean isaspect,org.alfresco.webservice.types.propertydefinition[] properties,org.alfresco.webservice.types.associationdefinition[] associations)
附件下載下傳：
![Java String.format方法的簡單使用[圖]](data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=)