Hello, I have been using Seam successfully for small-mid sized project. However, now the project requires the tree (using Apache Tree2 now) and tab interfaces (the tree is available on the left of the application all the time, so are the tabs from the top).
So the QUESTION is: how will one implement using stateless or stateful or just simply Seam + POJO so that the @End of the component will be called, somehow, to cut down the run-away conversation and to end it. Otherwise, one has to implement @Begin(join=true) so no errors occur but doing this is not healty for an app server. Remember that the tree and the tab are exposed on the application interface all the time so users may tempt to click on them while in long running conversation form? Is it a limit of Seam??? Please share your thought otherwise this seems to be a limition of Seam. A nice example is greatly helpful. Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026991#4026991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026991 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
