Well, I really don't think this is ugly UI design - the button might just be at a different position, above or below the actual form. The usual case is that the button is included, you're right.
My other problem is the more important one - there are actions I want to execute which are not supposed to trigger any validation or model update at all. The usual way to implement this is to use the "immediate" attribute - which works fine, except for input components which are themselves "immediate". For those, you'll still see validation messages popping up. regards, Martin On 12/29/05, Bernd Bohmann <[EMAIL PROTECTED]> wrote: > Hello Martin, > > Martin Marinschek schrieb: > > I thought so ;) > > > > Ok, I'm going to add a subform-component to my approach. I still need > > the attribute on the command-components, though, cause in my use-case > > (and probably many out there) the command component may be _outside_ > > the subform-component. Additionally, I might have commands which don't > > trigger validation and update for _any_ subform at all, even if they > > are children of a subform. > > Can you describe your use case? (jsp) > > In tobago we didn't have this use case so far. I think it is ugly ui > design if a command outside a subform must break the processValidation > and processUpdates. Perhaps i understand it if you describe your problem. > > I think it should not really a problem to provide a subview component in > tomahawk or sandbox that can used by all renderkits :-) > > Bernd > > > -- > Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development > Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com > phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333 > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
