Dave Newton wrote the following on 1/6/2006 9:35 AM:
Doesn't it just need validation info rather than model knowledge (you
listed validation constraints/msgs in your original list, which is why I
can't figure out why it needs any more info).
Not necessarily related to the model per-se but I see what Ted is saying
about other areas and to me it is the most 'grey' area in regard to web
apps - that is the 'other stuff' such as "How do I want my JSP form to
know whether it should display certain things as an Edit form or an
Insert form." If I have a JSP that has all my form inputs and set up
looking exactly how I want, but if it's being used as insert page I want
the title on the page to be different than if I'm doing an edit. Same
thing with the buttons. Possibly I might want the button to say "Update"
if I'm doing an edit and "Insert" if doing an insert. This came up in
another post a while back, and there is no real clear-cut best practice.
I'm guessing Ted refers to this as the "data entry hint" in his first
list I posted.
Then there are such things as maybe the user of the form is a "Special
User" and thus we need to show a special text box for the user to enter
the "Gold club membership number." Then you need some logic to decide if
the user is a gold member some processing needs to be totally different
of the form data... so do you:
a) Change where the form submits. In the Struts world a different
dispatch or Action, which involves logic in the JSP to decide how to
declare the <html:form> tag or
b) submit to the same action or dispatch method and then branch from there.
Obviously, I think choice b makes the most sense but in other cases it's
not always so clear.
In complex applications, things often become very blurry.
As a side note, at the moment, this is why I'm comfortable with JSTL on
the front end. When I was using MyFaces what I could do on the front end
with complex situations seem to be predicated on what the renderer could
give me - such as the DataTable (I think that was the name). Possibly
it's just my particular use cases I've run into... but often times my
front end had to be tweaked in different ways. "if this type of user" -
display extra text boxes here. "if this other user"- hide this div but
create another div with this stuff in it. Of course sometimes if the
views become too complex different views need to be broken out into
separate JSPs or possibly include files etc. The point is, though, that
I seem to have a lot of control. I felt I was missing some of this
front-end control when I was working with JSF - my markup seemed bound
to what rendering components I used - versus me having the complete
flexibility with JSTL to create the front end stuff in ways I was used to.
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
