Yeah, I think MyFaces-78 could be closed.

I still think that the whole issue of the JSF spec requiring no
validation of fields with null submitted values needs to be addressed
though.

I still don't understand that.


On Sun, 23 Jan 2005 09:49:33 -0500, Sean Schofield
<[EMAIL PROTECTED]> wrote:
> Right.  I think Heath's situation is a little unusual.  I can't
> personally see  a situation where the component is disabled on the JSF
> side and I would want change its value via javascript and resubmit it.
>  I didn't realize this was what he wanted until his last post.
> 
> I agree with you too that if you really need to do this, Heath's idea
> of  re-enabling the checkbox (or whatever) before submitting is the
> way to go.
> 
> sean
> 
> PS.  Heath, does this mean that MYFACES-78 can be closed?
> 
> On Sun, 23 Jan 2005 10:59:15 +0100, Martin Marinschek
> <[EMAIL PROTECTED]> wrote:
> > Reconsidering it: probably the best solution would be to enable all
> > components right before submission; as Heath has pointed out.
> >
> > Still - in the current state of affairs: if the component was disabled
> > on the jsf-side, and no value is posted back for this component, we
> > should probably not assume that the value has changed to be empty.
> >
> > regards,
> >
> > Martin
> >
> > On Sun, 23 Jan 2005 10:55:38 +0100, Martin Marinschek
> > <[EMAIL PROTECTED]> wrote:
> > > Interesting comment!
> > >
> > > yes, if you do exactly that, the browser will not post the changed
> > > value; and MyFaces will of course not be able to use it.
> > >
> > > What a tricky problem...
> > >
> > > Well, there will be some more work necessary to resolve this ;)
> > >
> > > regards,
> > >
> > > Martin
> > >
> > > On Sat, 22 Jan 2005 17:17:05 -0600, Heath Borders
> > > <[EMAIL PROTECTED]> wrote:
> > > > I think this might just be a MyFaces addition.
> > > >
> > > > The problem is that if client-side javascript is used, the control
> > > > could be enabled, changed, and then re-disabled, and JSF would have no
> > > > idea.
> > > > Of course, the only way to detect this sort of thing is either with
> > > > hidden inputs, or some client-side javascript to enable all controls
> > > > before submission.
> > > >
> > > > On Sat, 22 Jan 2005 14:06:27 -0500, Sean Schofield
> > > > <[EMAIL PROTECTED]> wrote:
> > > > > > yes, there is a section in the code which checks that if a component
> > > > > > is disabled, the value will not be reset... it is in the decodexx
> > > > > > method in the RendererUtils or HtmlRendererUtils; don't ask me which
> > > > > > one of these two, though ;)
> > > > >
> > > > > Is that because the spec requires it or is that a MyFaces addition?
> > > > > If its because of the spec, then add it to the list of nice little
> > > > > improvements in JSF over Struts. :-)
> > > > >
> > > > > > Martin
> > > > >
> > > > > sean
> > > > >
> > > >
> > > >
> > > > --
> > > > -Heath Borders-Wing
> > > > [EMAIL PROTECTED]
> > > >
> > >
> >
> 


-- 
-Heath Borders-Wing
[EMAIL PROTECTED]

Reply via email to