In JSF, anything that fails validation will suppress the action process. That's a fundamental design aspect of JSF designed to ensure that only "good" data is posted to the backing bean before an action can execute.
You want to have your cake (non-required items) and eat it (requiring them) too and that doesn't work.
However, looking at your example, I think a different approach will serve.
Right now, you appear to have the entire view wrapped in one big form, even thought the edit and delete sections appear to both be independent of each other. If you split the page definition into 2 forms - one for the edit part and one for the delete part, that would eliminate your problem. Only one form can be submitted - the one that contains the commandButton that the user clicked on. And validation only applies to the submitted form, not to any other form on the page.
An IDE is no substitute for an Intelligent Developer.
Joined: May 16, 2011
thank you Tim but main goal is to have it in the single form itself. is there a way out may be by using rich faces or something
Why should it be a "goal" to have everything in one form? A form is simply a collection of objects submitted as a unit and has no graphical characteristics other than the standard XML limitations of nesting elements. The user won't see the difference.