This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I think there is no problem doing this, but I'd rather try to let it more high level in order to keep it very understandable. Since I'm waiting for results, I can't give you sure, but I haven't even included FacesServet on my Sequences. I put a direct conversation between my XHTML files and ManagedBeans and the return was mostly a message saying "Render page X".
Joined: Oct 05, 2011
Thanks Eduardo. I think I've come too far to remove the FacesServlet now
I think it's a good way of showing the main MVC concepts, thus the reason I put it there.
Would the ManagedBean actually "return" values (e.g "return List<Object>") to the FacesController or "bind" / "process" them.
If your ManagedBean method signature is List<Object> methodXYZ(param) , I think in sequence diagram you should show the return object to FacesServlet.
Take an example, List<Product> findByCategory(categoryCode) -> where you are listing list of Products by category code. - here if you show ManagedBean returning a list of
Products (and so it is clear that managed bean is not returning just product names.... and hence controller can redirect to Product Detail page, when a product is selected ) - this seems good idea to me.