...
Warning | ||
---|---|---|
| ||
Once you make this change, DLM will no longer read fragments from dlm.xml; you must define all your fragments in the database. |
layoutContext.xml
Modify dlmConfigurationLoader
bean, replacing:
...
Code Block | ||
---|---|---|
| ||
<bean id="dlmConfigurationLoader" class="org.jasig.portal.layout.dlm.RDBMConfigurationLoader"> <property name="configurationFile" value="classpath:/properties/dlm.xml" /> <property name="fragmentDao" ref="fragmentDefinitionDao" /> </bean> |
Importing Fragment Definitions
Now that you've enabled the RDBMConfigurationLoader
, you'll need a way to get fragment definitions into the database. Import/Export provides support for these entities.
Use the following command to import a directory that contains .fragment-definition files:
>ant data-import -Ddir<pathDdir=<path.to.frag-def.dir>
The .fragment-definition.xml
files support the same XML syntax as dlm.xml
Example fragment-definition File
Code Block | ||||
---|---|---|---|---|
| ||||
<fragment-definition xmlns:dlm="http://org.jasig.portal.layout.dlm.config" script="classpath://org/jasig/portal/io/import-fragment-definition_v3-1.crn"> <dlm:fragment name='Guests' ownerID='guest-lo' precedence='20'> <dlm:audience evaluatorFactory='org.jasig.portal.layout.dlm.providers.GuestUserEvaluatorFactory'/> </dlm:fragment> </fragment-definition> |
- Setting the precedence attribute
- Each fragment must also declare an integer precedence value. This value is used during merging of fragments to position elements contributed from different fragments. It is also used to determine which precedence elements can override a lower precedence. The higher the number the higher the precedence.
Info | ||
---|---|---|
| ||
Additional References |
...