Hi, i've traced changes in 1.5-RC4.2. Found the issue 3552 [ https://issues.apache.org/jira/browse/WICKET-3552 ]. If i'm not completely in the wood the solution breaks the SingleResponsibilityPrinciple by adding a flag to the constructor which negates the class behavior. Wouldn't it be more clear and reusable if we had another AttributePrepender which acts like the AttributeAppender. Both could extend the base-class AbstractAttributeRegister or something. Then only the different part of the newValue method has to be implemented by the concrete class.
I only ask because if 1.5 is out it will be hard to exchange because many apps will be upgraded and feature is maybe used :-). What do you think? Cheers Per --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
