LiferayTodo

Introduction

This is a list of the tasks remaining before the Liferay integration is ready for release and production use.

Todos

Please delete items from the list below when they are completed.

• Change code so it handles Ontopia transactions correctly.
• Ensure that the RelatedTopics portlet does not show content which is not approved. (And also not content which is deleted/expired/scheduled.) This solution should be reusable in other portlets, if possible.
• Develop a search integration, adding a search predicate to tolog.
• Develop a search portlet.
• Resolve the classpath hack.
• Get rid of the predefined group for "Guest" with hardcoded ID. These IDs change with Liferay versions and so are guaranteed to break often and hard. Have to make the code handle this some other way.
• Add support for more Liferay objects like documents, files, etc.

Ideas for more portlets

• A tree view portlet.
• A "similar content" portlet.
• A breadcrumb portlet (?).

Known Issues

• OntopiaAdapter:

• Editing Webcontent or Wikipages that don't have a topic representation in the tm will lead to an errorpage embedded in Liferay's edit page.

• Editing and saving Webcontent or Wikipages that don't have a topic representation in the tm, will create a topic without connecting the topic to a community

  • That's because Groups are handled differently in the update method. They are not being created in an empty inMemo topicmap like all other topics.

• Logging in with a user that is known to Liferay will result in the creation of that user inside the tm, because an update() is triggered everytime a user logs in.

• If the integration should - for some reason - throw an exception while processing updates() the users won't be able to login. Undeploying the integration would make login possible again.

• If Webcontent or WikiNodes are created that are linked to a group that is unknown inside the tm, the creation will fail.

  • no topic will be created (technically it is created but removed upon failure of creating the association to the group).

• topicNamePortlet:

• no preferences can be set for this portlet

• RelatedTopicsPortlet:

• On the preference page: Only "topic id" and "association id" is wired to the view.jsp. All else is passed to view.jsp but is not processed.

• On the preference page: After once supplying one or more association ids, and then removing all again, the portlet will fail.

  • something's fishy with the way the portlet handles an empty string, when it tries to make a Set of it before passing it to view.jsp

• A once set topic id is stored to the preferences and can't be reset as of now.

• There's no helptext when following the "Help" menu.