>In my opinion, using custom tags for this purpose is not the best way >to go. Custom tags are meant to decouple code from markup.
I tend to agree with you. >I would (A) either use a controller/navigation switch for this (B) >or use some logic on the page for this, e.g. <c:if>, etc. What do you mean by (A)? (B) seems like the only practical option at the moment. My controller will return a list of "attributes" (to be completed by the user on this step). I will then have to go though each of them (iteratively) and use something like <c:choose> to display or not display the custom tag associated to this attribute (like a calendar control, text box, etc.). Does that sound about right? Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
