Home

The missing glue between Alfresco and Spring MVC

Personally I do not like webscripts because of the boilerplate code that comes with them (XML, FTL, Java/Javascript). Also I am not a big fan of javascript on the server side esither, as in a medium sized application this becomes unmaintainable. That is why I wrote Alfresco @MVC.

Alfresco @MVC consists of several libraries for REST, AOP and QueryTemplate.

Distributed on Maven Central

<dependency>
  <groupId>com.gradecak.alfresco</groupId>
  <artifactId>alfresco-mvc-XXX</artifactId>
  <version>6.0.0-RELEASE</version>
</dependency>

since Alfresco MVC 6.0.0

• Alfresco 6 is supported alongside with Spring 5.x MVC features
• Spring Data dependencies for pagination are removed in favor of Alfresco Params pagination
• New annotation @Enabled configuration for Alfresco @MVC Rest
• QueryTemplate was droped in order to reuse the new public apis and their services
• Alfresco @MVC dist (amp distribution) is dropped, since we only provide libraries instead of concrete Alfresco modules. However our samples could still be provided as AMPs too.

since Alfresco MVC 5.0.0

• a new project structure is created
• no alfresco modules are registered when the jar/amp files are deployed
• include samples
• include a deployable alfresco project (alfresco-mvc-samples-bom/alfresco-5.2.e). You need to configure the database and alf_data
• an AMP artifact can be build from the source code (mvn clean package). You will find it under alfresco-mvc-dist/target. However, it is better to include the dependencies in your build