Versions Compared

Old Version 33

changes.mady.by.user Misagh Moayyed

Saved on

compared with

New Version Current

changes.mady.by.user Misagh Moayyed

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • Scan uploaded files using AntiVirus software. (i.e. ClamAV)
  • Incorporate Apache Chemistry along with support for OpenCMIS
  • Portlet content and posts are cached by the distributed Ehcache framework.

...

Configuration

  • Role configuration (author/viewer) is done within the portal itself via PAGS or any other group types managed by the portal. Please note that this configuration is entirely independent of the portlet audience that is defined at the time of publishing the portlet in portal. The portlet configuration defines a portal-agnostic method for role-based behavior, that is defined inside the portlet.xml file of the project:

    Code Block
    languagehtml/xml
    <security-role-ref>
  <role-name>author</role-name>
  <role-link>local.2</role-link>
</security-role-ref>

    You can modify the role to map to a particular group native to the portal environment. 

    Furthermore, the portlet will be able to allow access to the EDIT mode of the portlet based on the user's role, defined above. The access rules for various portlet modes are defined as such:

    Code Block
    languagehtml/xml
    <bean id="portletModeUserRoleAuthorizationInterceptor" class="org.jasig.portlet.cms.controller.PortletModeUserRoleAuthorizationInterceptor">
	<property name="authorizedRolesMap">
		<map>
			<entry key="view" value="*" />
			<entry key="help" value="*" />
			<entry key="edit" value="author" />
			<entry key="config" value="author" />
		</map>
	</property>
</bean>

    The configuration above indicates that all users can access VIEW and HELP modes, but only those that are classified as "author" are allowed access to CONFIG or EDIT mode.

  • Portlet follows the JSR 268 Portlet specification, supported by the Spring Portlet MVC framework.

  • All published content is stored inside the Java Content Repository (JCR) supported by the JSR 170 specification with the implementation provided by Apache Jackrabbit.


    Spring framwork

     Spring framework JCR extensions are employed to communicate with the repository. 

    Info
    titleContent Management
    If you have registered multiple instances of the portlet on the page, by default they all would display the same content because the default configuration of all portlets points to the same spots in the underlying content repository.  If you wish for a portlet to administer its own content, in the preferences screen when you deploy, specify the new location of the repository to which the portlet should write content.
  • Apache Velocity is used to render the portlet user interface pages, while JSP implementation of the UI can easily be swapped.

...

  1. uPortal (3.x, 4.x)
  2. Apache Maven (2.2.1, 3.0)
  3. Tomcat 6.x

 

Info
titleScreen Cast
  A brief screen cast that highlights the portlet features and configuration options is available here.

 

Source Code

Project source code is available at: https://github.com/Jasig/ContentManagementPortlet

Build
  • Adjust the paths in the build.properties file (portal, tomcat and maven directories)
  • On the command line inside the project source directory, use the following command:
Code Block
languagenone
titleApache Ant Deployment
> ant package

...

Once the build is successful, you should be able to browse to the "<tomcat-home>/webapps" and find the "ContentManagementPortlet.war" application file.
...