On 1/10/06, Angel Navarro <[EMAIL PROTECTED]> wrote: > > Hi, > > I have to take a difficult decision. > > I have to develop a new web application and I think that I have to use > JSF, > but I also think that I have use Struts as Controller.
For the purposes of this reply, I'm going to assume by your use of the term "Struts" that you mean the existing Struts 1.1 or 1.2 (or the upcoming 1.3) framework, correct? The web application that I have to develop it's a medium, big application. > > The two alternatives are Shale or Struts-faces, correct?, Not really. Shale is a completely separate framework that leverages the fact that JSF already provides a controller servlet, plus support for navigation and other simiklar things. It shares no code with the Struts 1.xcontroller framework. but Shale I think > that is not a final version, and perhaps it's a risk decision...... > But Struts-Faces, perhaps in few months, will be deprecated?.....it's a > good > alternative?, I don't know! > Have another alternative????, in this moment, I have a big problem!!! > > Thanks and sorry by my English ;) If you are absolutely required to use Struts 1.x and JSF together, then struts-faces is your alternative. It's primary purpose is to enable existing Struts based applications to be migrated -- but it can serve as the basis for new development as well. That being said, the combination is not the path I would recommend for new development, because you end up with a lot of redundant functionality (two ways to do navigation, two ways to do validation, two ways to do conversion, and so on) that will make maintaining the application more complicated than it needs to be. If JSF is a requirement, I would recommend lobbying for using either JSF by itself, or JSF with Shale -- the combination gives you pretty much the same set of overall functionality that Struts 1x does (including client side validation and support for Tiles), but without the duplications. Angel > > Craig
