|
This portlet messaging library is intended for situations when:
- You want to build an application out of several interacting portlets (e.g. a portlet which presents a list or index, and a number of portlets which display information about the selected item)
- You've read this Tip on java.net and decided that the PortletSession is the way to go (if you wanted one of the other methods, have a look at Limitations in the Documentation)
- You can't simply hardcode the messaging using APPLICATION_SCOPE session variables with known names, because:
- Maybe you want many instances (windows) of the same portlet on the same page, or different pages, with each instance talking to different portlets
- Maybe you want the user to be able to dynamically add new portlet instances (windows), and configure the 'wiring' of messages between portlets.
- Maybe you want portlets in different portlet applications to communicate.
This is version 2.3 of a slightly more complicated messaging system, implemented for the Discovery Net project. Please let me know if you find it useful, or have any comments/advice/bugfixes that may make it better. The source is available and you're welcome to modify/use it however you like. It's licensed under the Apache License, Version 2.0.
Download
Documentation
New in version 2.3 (August 2006)
- Bugfixes for use with recent JBoss Portal builds (>22 June 06): fixed support for messages with blank namespaces, and for Edit mode on some of the test portlets.
Older versions:
- Better example portlets - Portlet1 and Portlet2. They provide a quick way of testing messaging, and also act as a mini-tutorial.
- Practical change for users: the library now uses commons-logging for debug messages. This adds a dependency to your portlet app using the messaging library - though your portal server probably already has it.
- Cross-context messaging simple EJB example now working and tested on Geronimo 1.0, JBoss 3.2.7, and JBoss 4.0.2.
- Maven for building source.
- Improved Session ID retrieval for cross-context messaging:
- using
PortletRequest.getRequestedSessionId(), removing the need for strange hacks
- Improved Portlet ID retrieval:
- gets the actual Portlet Window ID used by the portal, rather than randomly-generating an ID at the start of each session.
- Debug messages can be turned on/off
- Applied the Apache License, Version 2.0, as a result of several queries!
- Cross-context messaging
- Support for dynamic removal of message inputs/outputs
|
|
