I would like to ask you about a conception problem. I m coding a application with seam and I d like to write a workflow of 7 pages (facelets) which contain some arguments such as table, list, calendar.This workflow 's behaviour seems to be like a "basket" of a web business store.
Should I write only one ejb session stateful for this workflow or use one ejb by page?
I m afraid to have one big class with all the arguments but I should have the default behaviour of a store basket.
Thanks in advance for your help and your advice
If it is really a workflow with state that goes across the entire conversation, then keeping that state together in one place probably makes sense. If there are natural divisions then you might break it up some I suppose. Seam will let you do whatever you feel is most natural for your app.