Yes, the Optional Validator framework still needs more work to support wrapping arbitrary validators inside of an OptionalValidator validator component, so you will need to find another way to do this in the short-term.
However, you can use the framework right now to convert "required" attributes into required validators and that will solve a lot of issues. -Mike On 10/17/05, Rafael Nami <[EMAIL PROTECTED]> wrote: > Alexander said: > As I see for the quick-solution your way might be a > Javascript-controlled > pop-up! (And I HATE JS...) > > Me too ;) I'm with Core Java Server Faces beside me to learn how can I do > this validator component. > > Cheers > > Rafael Mauricio Nami > > > > > > > 2005/10/17, Jesse Alexander (KBSA 21) > <[EMAIL PROTECTED]>: > > Mike and I have experimented for quite some time before diving into the > > rather complicated world of the optional validator... Guess why we > > finally > > dived into that? Because there is no way around it. > > > > As I see for the quick-solution your way might be a > > Javascript-controlled > > pop-up! (And I HATE JS...) > > > > reagrds > > Alexander > > ________________________________ > > > > From: Rafael Nami [mailto:[EMAIL PROTECTED] > > Sent: Monday, October 17, 2005 1:30 PM > > To: MyFaces Discussion > > Subject: Re: [MyFaces] Custom Validator??? > > > > > > PS - The main problem that persists is that - if the user fills the > > form1, and I use immediate="true" in "Add Details" button, the form1 > > values will be empty when the user navigate from detail page to form1 > > again (don't know FOR SURE, but I think immediate="true" skips the > > validation, conversion and update values phases). > > What can I do just to mantain the POJO values between the pages, and > > just validate the form1 values with a "Complete Process" click? > > > > Thanks and Best All > > > > Rafael Mauricio Nami > > > > 2005/10/17, Rafael Nami <[EMAIL PROTECTED]>: > > > > Thank you both for your support. > > The point Jesse raised is cool, having a "optional validator" > > component, and we ***WILL*** need something like it for our other > > requirements, but in this one, I think we'll go for something like > > Volker said, because in the "details" page, our team saw that we don't > > need any information from "form1" to add the details to validate. We > > simply can add as much details as we need, go back to the form1, and > > then use the "Complete Process" button to validate all form1 fields. > > > > Thanks again > > > > Rafael Mauricio Nami > > > > 2005/10/16, Volker Weber > <[EMAIL PROTECTED]>: > > > > Hello, > > > > if i understand you correct, you need to execute > > updateModelPhase, but > > skip validationPhase. > > > > Have you tryed immediate="true", to skip both, in your > > "Go to Detail" > > button and invoke viewRoot.processUpdates() in your "Go > > to Detail" action? > > > > Regards > > > > Volker > > > > > > Rafael Nami wrote: > > > Good morning everyone. > > > Thank you guys for pointing me out a good solution for > > the popup thing. > > > The current problem is something like this: > > > > > > We developed a Wizard-Style to avoid the use of > > Popups. The flow consists > > > in something like this: > > > form1->details->back to form1 to confirm the flow. > > > The main problem is that we need to go to the details > > WITHOUT validation > > > when the user clicks the "Go to Detail" button, but if > > the details are > > > complete > > > and the user clicks the "Complete Process" button, the > > form1 HAVE to be > > > validated. > > > > > > Did I have to use/write a custom Validator component > > to addthis kind of > > > behavior? > > > > > > Thanks in advance, and Best All > > > > > > Rafael Mauricio Nami > > > > -- > > Don't answer to From: address! > > Mail to this account are droped if not recieved via > > mailinglist. > > To contact me direct create the mail address by > > concatenating my forename to my senders domain. > > > > > > > > > > > >
