Hello everybody, Thanks for all your answers, hints, encouragement... I really appreciate that. I'm not about to give up, I'm just trying to figure out what's the best thing to do. Using plain old links may work in some cases but often you really have some kind of a state in your web application to deal with and this seems pretty difficult with JSF (although ADF processScope makes it somehow easier). And in fact our (implicit) goal was to limit the technology stack not to depend from too many frameworks. And we thought (naively?) that EJB + JSF should be enough as EJB takes care of business logic and database mapping and JSF is supposed to deal with the web presentation layer. Anyhow, Seam seems pretty interesting for us, especially that we are already using JBoss AS. Couple of questions though:
-) Is it possible to use Seam with EJB 2.0 or only with EJB3? I don't think we're ready to move to EJB3 at the moment (mainly out of concern that it seems to be too young to be production ready) -) Suppose we want to move to JSF+Seam+Facelets instead of JSF+JSP. How much do those approaches differ? Would it require us to write all the presentation stuff from scratch or could we somehow use what we have up till now? -) I saw in [1] that usage of Tomahawk components is not recommended - does it pose some (serious) problems? Is it possible at all to use them? How about dojo? Thanks a lot for your help, Adam Koprowski [1] http://docs.jboss.com/seam/1.1BETA2/reference/en/html/controls.html Daniel Young wrote: > > > > Hi Adam, > > > > I would recommend taking a look at JBoss Seam, which solves many (possibly > all) of these issues. > > Enjoy, and don't give up, > > Daniel. > > -- View this message in context: http://www.nabble.com/JSF-is-the-answer--I-don%27t-think-so...-tf2794657.html#a7864136 Sent from the MyFaces - Users mailing list archive at Nabble.com.
