[Opensource] Proposal @deprecate nested Inputs/Outputs/Transitions

[Peter A. J. Pilgrim]

Michael Rimov wrote:
> Hey All,
> 
> I'd like to get your input on the concept of @deprecating the 
> addNested() methods of Inputs, Outputs, and Transitions.  Blocks would 
> still allow nesting.
> 
> The reason for this is reliability in code.
> 
> 1- There's a lot of if/else statements because Inputs could have nested 
> Inputs.
> 

This does not seem to make sense for HTML rendering. A text field cannot
have a submit button for example.

> 2 - The extended struts tags can't even understand the concept of nested 
> Inputs/Outputs/Transitions.
> 

Redundancy

> And finally the concept of nested inputs/outputs/transitions existed 
> before Blocks existed.... and frankly, I think Blocks do a much better 
> job of organization.
> 

This is better design like Swing or AWT. What is the different between
java.awt.Component and java.awt.Container? The answer is that Container
manages and hold a list of references of Components.

> If we @deprecate the methods, they will be officially removed in version 
> 5.2
> 
> Thoughts?
>                         -Mike
+1

-- 
Peter Pilgrim
ServerSide Java Specialist

My on-line resume and for interview videos about myself, J2EE
Open Source, Struts and Expresso.
    ||
    \\===>  `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''