Hi Gavin, Maybe you can give me an example of how I should be designing my webapps using Seam.
Lets take a simple CRUD application, The home page should be accessed by a GET request and accept a parameter that identified the current user. It should display a list of products in a table, selecting a product should display a page of the product details. There should also be a shopping basket that you can add products to and remove products from. 1) How many Seam components should I need to do this? 2) In what scope(s) should they exist? 3) Do I have to tag my Entity beans as Seam components? I've checked the examples, and I know there are similarities, but what I'd like is a more in depth explanation of when and where to use things. Thanks for your help! PS: Gavin, I hear you're giving a talk in London on March 29th, as part of the JBoss ON the Road seminar. Can I ask whether the focus of the workshop is EJB3/Seam or JBoss ON? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3927446#3927446 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3927446 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
