I face the same problem. It is more complicated if used with <jsp:include> or Tiles. So I dont give the JSP pages back to graphics designer for editing because it wont display it properly and no Struts html tags are understood and no html input elements displayed. So to edit HTML I have to go through all the steps of deploying, refreshing and consumes time.
And here is the advantage of JSF over Struts because it have tool vendor support and makes the life of programmers easier by rendering tags. I think that Spring is better than Struts in this repspect. I used it only for learning only. rgds Antony Paul On Wed, 22 Dec 2004 12:02:21 -0700, Wendy Smoak <[EMAIL PROTECTED]> wrote: > This is my first time having someone else do the page design. I'm thrilled > to have someone else do it, but they use DreamWeaver and I'm not sure what's > going to happen if it sees <html-el:form>. Then there's the fun of JSTL > tags embedded within HTML tags, which works fine but can't exactly be > considered valid syntax. > > I checked the archives, but only found suggestions to use something other > than DreamWeaver. I don't think that's going to go over well. > > My current plan is to have them use plain-old html form elements, and I'll > automate as much as possible the task of switching them over to > <html-el:...> tags. Not much fun, but far better than having to do the > page design. > > Does anyone have suggestions for coordinating page design with Struts webapp > development? > > -- > Wendy > > --------------------------------------------------------------------- > 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]
