Seam is an extremely helpful library, especially if you are going to be using hibernate or EJB3 persistence. Its conversation scope is very robust as well as its navigation handling extensions. Its security is also fairly easy to work with (once you have it configured).
The only thing you may notice with Seam is that it is very integrated into the JSF lifecycle and if you start doing some advanced coding with your application you may run into areas where you have to consider how you may affect Seam's functionality. -Andrew On 8/29/07, x y <[EMAIL PROTECTED]> wrote: > > Anybody with JSF/Seam experience to share your thoughts? Thank you in > advance. > > ----- Original Message ---- > From: x y <[EMAIL PROTECTED]> > To: MyFaces Discussion <users@myfaces.apache.org> > Sent: Wednesday, August 29, 2007 9:08:47 AM > Subject: Re: Which components to use? > > > I am so sorry for the late reply. Thank you so much. Your suggestion will be > of great help. > > Cheers! > > ----- Original Message ---- > From: David Delbecq <[EMAIL PROTECTED]> > To: MyFaces Discussion <users@myfaces.apache.org> > Sent: Wednesday, August 22, 2007 11:19:02 PM > Subject: Re: Which components to use? > > Situation here: > > using here: Facelets + Myfaces + Tomahawk + Sandbox + Ajax4JSF + > RichFaces+ Custom components. Only limit we found is that one of our > really big forms (around 200+ components in it, with lots of Javascript > enabled components like t:calendar and lots of ui:include)take around 2 > seconds to be first time generated to user. We still have to investigate > whever it comes from JSF tree or from the database backend which has a > few tables to explore :) > > We are probably not the best example, as we use it for a reasonable > traffic intranet. But for component compatibility we did not notice > things that make them unusable. Of course each component has it's > limitations, but they are not that hard to cope with. > > x y a écrit : > > Hello, > > > > I know this kind of question is sometimes annoying, but with so much > > components being created and enhancements on the existing ones, it is > > hard to make a decision, in a formal process, for the components to > > start an professional enteprise application. > > > > We are using Spring, then I think it could be a clue in which > > directions we could go. I am thinking in MyFaces with its variations: > > Trinidad, Tomahawk, etc. Another alternative would be to use Seam > > integrating with Myfaces and Spring, but I am not sure about how it > > has been working in production. > > > > The main aspect here, is that I would not like to start with a > > componet, and suddenly find that there are so many bugs to be > > corrected or there are limitation to integrate with other components > > to provide more features. > > > > You people, that have been working with those components in production > > (or at least close to it), would you mind to share you thought? > > > > Thank you very much. > > > > > ------------------------------------------------------------------------ > > Looking for a deal? Find great prices on flights and hotels > > > <http://us.rd.yahoo.com/evt=47094/*http://farechase.yahoo.com/;_ylc=X3oDMTFicDJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20-> > > with Yahoo! FareChase. > > > ________________________________ > Boardwalk for $500? In 2007? Ha! > Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! > Games. > > ________________________________ > Got a little couch potato? > Check out fun summer activities for kids.
