[PLUTO-520] Provide backwards compatiblity for Portlet Applications using/embedding Pluto 1.0.1 portlet.tld

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0-refactoring, 2.0.0
• Fix Version/s: 2.0-refactoring, 2.0.0
• Component/s: portlet container taglibs
• Assignee: Ate Douma
• Reporter: Ate Douma
• Created: 02/Nov/08 21:46
• Updated: 02/Nov/08 21:48
• Resolved: 02/Nov/08 21:48

Description

The new Pluto Portlet API taglibs have new Tag class names which causes old portlet applications still embedding/using the old Pluto 1.0.1 portlet.tld to fail.
While per the portlet spec portlet applications should not embed/provide their own copy of portlet.tld but depend on the portal/container to supply it dynamically, fact is many prebuild portlet application wars do contain it.

This is easily solved by adding the "old" tag classes too, and have them just extend the new tags (albeit marked as deprecated).

I'm going to commit these classes only to the 2.0-spi-refactoring branch as the move of that branch to trunk is about to happen any time now (pending the vote currently running on the dev list).