[WW-1645] Move Portlet Support to a Plugin

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.1.0
• Component/s: Plugin - Portlet
• Assignee: Nils-Helge Garli
• Reporter: Ted Husted
• Created: 16/Jan/07 02:06
• Updated: 28/Oct/12 22:08
• Resolved: 19/Jul/07 11:32

Description

---------- Forwarded message ----------
From: Don Brown <[e-mail]>
Date: Jan 15, 2007 12:33 AM
Subject: Re: [S2] Experimental Features
To: Struts Developers List <[e-mail]>

I got 90% of the way once moving the portlet support out to a plugin,
but there were a couple hardcoded references in the URL component and
another internal class that escapes me ATM, so I backed off. This could
be revisited for 2.1.

Don

Tom Schneider wrote:
> Ted Husted
> whttp://www.netidentity.com/Landing7.aspx?d=dail.com&mp=DomainRedirect&DomainID=18855&CategoryID=101521869rote:
>
>> It would be great if there were a portlet plugin. I have no idea how
>> the support is implemented, but I expect it would not be that easy.
> Well, the PortletDispatcher (Jsr168Dispatcher.java) and related
> portlet request support classes would probably be easy to separate
> out. The trick would be the form and url tags which right now have
> specific portlet behavior for building portlet url's. The real
> question is do we want separate tags for portlet urls? If so it might
> be possible to have a subclass of the url and form tag for portlet
> environments. If not, then we'd either have to leave the portlet
> support in core and only use it with the portlet plugin--or find some
> way to override how urls are build in core via the plugin. These are
> the issues that I see based on my limited knowledge of the portlet code.
> Tom

Issue Links

• relates to: WW-1713 Using 'url' tag library element with Action & Method doens't work.