RE: [OS-webwork] Suggestion for a change in UI Component Tag

[Cameron Braid]

Title: Message

on second thoughts.. there was something confusing happening.. the TLD for the component tag declares that its contents MUST be empty :(

 

Please change it to JSP and all is well :)

 

I have submitted a Jira issue  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-198

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cameron Braid
Sent: Thursday, 29 May 2003 9:56 PM
To: [EMAIL PROTECTED]
Subject: RE: [OS-webwork] Suggestion for a change in UI Component Tag

you can all ignore my ignorance... I have just discovered that the Component tag is parameterizable !!

 

Thanks :)

 

..Cam..

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cameron Braid
Sent: Thursday, 29 May 2003 7:29 PM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Suggestion for a change in UI Component Tag

The WebWork2 UI Component tag is great, however I wish to be able to add custom parameters to it, using the ww:param tag

 

I suggest a couple of things:

 

1. Refactor AbstractTags into

   * AbstractUITag

   * AbstractOpeningUITag

   * AbstractClosingUITag

   * AbstractWrappingUITag

 

So that the

  * most UI tags extend AbstractOpeningTag and SKIP the body, rendering the template on doStartTag

  * the form tag extends AbstractWrappingUITag to provide templates for open and close and it allows JSP content

  * the component tag can then extend AbstractClosingUITag to enable parameterisation and render the template in doEndTag

 

How does that sound ?

 

 

..Cam..