You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Table of Contents

Spring-DM-Target-Platform

Follow the setup outlined in chapters 1 and 2 of the Spring Dynamic Modules Tutorial with the following exceptions:

  1. At Step 1.2, use the following copy of pom.xml, which has been updated for Spring DM 1.2.
  2. At Step 1.5, use the name SPRING_DM_1.2 instead of SPRING_DM_1.1 for the User Library.

fedora.war

Until the Fedora Maven build is able to produce a deployable war artifact, you will need to manually create the Eclipse project that represents the Fedora WAR.

For the Spring DM extender to recognize your fedora.war Eclipse project as a web application, ensure that the project name ends in ".war", e.g. "fedora.war". The project structure should resemble the following:

  • fedora.war
    • WEB-INF
      • lib
    • MANIFEST
      • MANIFEST.MF

At this stage in development, fedora.war should have the following features disabled:

  • SSL
  • Resource Index
  • Messaging
  • Local Services
  • API-A Auth

MANIFEST.MF

Add the following META-INF/MANIFEST.MF to your copy of fedora.war
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels