| Note | ||
|---|---|---|
| ||
Starting with uPortal 4.0.4, JPA-managed (database backed) fragments are now the default option. For those versions, you can revert back to defining fragments in dlm.xml by following these directions in reverse. You will need to create the dlm.xml file. There is an example of that in layoutContext.xml. |
As an alternative to defining DLM fragments in dlm.xml, portal administrators may elect to enable the RDBMConfigurationLoader, which loads fragment definitions from the database via Hibernate and JPA. The major advantage of this approach is that it allows fragments to be added, removed, or change their audiences without a portal restart.
RDBMConfigurationLoader can be turned on by modifying persistenceContextlayoutContext.xml and layoutContext.xml
| Warning | ||
|---|---|---|
| ||
Once you make this change, DLM will no longer read fragments from dlm.xml; you must define all your fragments in the database. |
persistenceContext.xml
Uncomment fragmentDefinitionDao bean:
| Code Block | ||
|---|---|---|
| ||
<bean id="fragmentDefinitionDao" class="org.jasig.portal.layout.dlm.FragmentDefinitionDao">
</bean>
|
layoutContext.xml
Modify dlmConfigurationLoader bean, replacing:
...
>ant data-import -Ddir<path.to.frag-def.dir>
The .fragment-definition.xml files support the same XML syntax as dlm.xml
...