Hmm... well, if I was doing something like that in real life I might well do it from the Action :) That doesn't make it the generally accepted "right answer' thought.
I think most people would tell you to forward to a JSP to generate what really amounts to just a snippet of HTML... IIRC, one of my examples does that. Keeps the view more properly separated and all that architectural jazz. Sometimes I think we all get so wrapped up in trying to achieve the perfect architecture that we overcomplicate things... if all I'm returning from the server is the HTML for a bunch of <option> elements, it doesn't really strike me as a bad idea to do that in an Action (or maybe from a delegate class that returns a string that the Action then returns). I'm not sure the developer community at large would agree with that though, they seem to be more concerned with perfect architecture, hence that note in the code :) -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Mon, May 2, 2005 2:37 pm, Rick Reumann said: > Frank W. Zammetti wrote the following on 5/2/2005 2:18 PM: >> Glad your enjoying it Rick! I hope you find something useful in it too. >> :) >> > > I see in your examples you make the note about writing the HTML in your > Action is bad form, but I'm curious then how you handle this in real > life. For example, looking at example 3 where the options list of > "characters" changes based on your first selection, how/where do you > write out the HTML that needs to be outputted to the response? > > Thanks again, > > -- > Rick > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
