These portlets make use of the new version of person directory that allows for searching as well. This results in changes in the person directory configuration. Person directory bean configuration is documented here: http://www.ja-sig.org/wiki/display/PDM15 This change also means you need to clean out shared/lib before deploying to ensure old versions of the person-directory api are removed.
The swapper portlets are implemented using Spring WebFlow 2. Documentation on how flows are implemented/configured in uP3 and the current flows in the framework is available here: http://www.ja-sig.org/wiki/display/UPC/Administrative+Flows One of the big benefits of flows for the portal admin UIs is the sub-flow functionality. This allows UI flows to be treated as method calls where arguments are passed in and the sub-flow returns object data to the parent flow. With the swapper portlets an example of this is the person-lookup flow. It is a self-contained user search flow that returns an IPersonAttributes object to the parent flow representing the person searched for and selected by the user. The eventual goal would be to have all portal administrative and utility UIs implemented as flows allowing for their re-use and integration and deprecating the need for the IServant API which has no portlet equivalent.
-Eric
smime.p7s
Description: S/MIME Cryptographic Signature
