Page History

...

• it is awkward to require a parent container as a wicket component. most of the time it needs to be attached to wicket:container tag because there is no reason to have an actual parent tag or a parent tag is impossible (in case of trs, lis, etc)
• having groups as non-components will allow for nested sets of checks and radios
• having groups as non-components will allow for disjointed sets of checks and radios in a cleaner fashion

cdi 1.1 upgrade

wicket-cdi should use cdi 1.1 which should remove dependency onto seam-conversation module.