>From: "Chan, Jim" <[EMAIL PROTECTED]> > > Anyone who tried to refactor JSP to JSF will know that it takes some work to > adapt the existing html/JSP code to utilize the JSF tags. Because I'm under > time constraints, I've really only used JSF tags for controls that need to > be bound the backing beans. All other html/JSP code was wrapped with > everybody's favorite tag - . There are verbatim tags everywhere > - yikes. I am hoping I can refactor them out at some later time, but my > biggest dream is to have the JSF specification at the container level so > non-JSF text do not have to be buffered at all. >
I built a tool for conversion of Forte templates to JSF. These templates were html friendly so I was able to use the Swing html parser in headless mode. This was over a year ago and the client decided on Struts so it was modified to convert html to Struts JSP. I'm not sure how messy your JSP is and how much scriptlet is imbeded in your JSP's but you might be able to use the Clay html parser to build a conversion tool. It should parse out a JSP into a graph of nodes. You would then have to associated a builder\render with html nodes. This is how the Clay plugin allow creating a JSF page using HTML. I thought about trying to generate a JSF page from a Struts JSP but decided that would be silly. A conversion tool might be a waste of time depending on if you can find patterns in the current JSP's. > Anyway, I wanted to know if: > > - I am taking a good approach to refactoring the existing webapp? > - Will JSF evolve to a point where tag is not needed? > JSF 1.2 will solve the verbatim issue. > Any input would be appreciated. Thanks. Gary
