tag:blogger.com,1999:blog-6137205730562326735.post7240025612866996053..comments2010-01-16T16:34:27.175-08:00Germán Escobarhttp://www.blogger.com/profile/05863454066402527692noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6137205730562326735.post-88139383496119218252010-01-16T16:34:27.175-08:002010-01-16T16:34:27.175-08:00You can always relay on the /debug.seam page to see what is inside of each context, although, I agree with you that it can get tricky sometimes. The source of lazy initialization exceptions are always originated elsewhere, so, if you can show me an example, I&#39;ll be glad to discuss it.Germán Escobarhttp://www.blogger.com/profile/05863454066402527692noreply@blogger.comtag:blogger.com,1999:blog-6137205730562326735.post-64290670413390127602010-01-15T07:23:15.365-08:002010-01-15T07:23:15.365-08:00I&#39;d like to see a visual (diagram) representation of this concept, its hard to grasp for many. using this on several project, i can also tell you its hard to debug things using these contexts, and you&#39;ll frequently run into lazyinitialization exceptions. there&#39;s a lot to be said for keeping things simple.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6137205730562326735.post-42043162591919273512009-12-22T12:07:01.150-08:002009-12-22T12:07:01.150-08:00Thanks German,<br />I find this article (as well as the other about Seam and JSF) very useful for those trying to understand the essence of JSF/Seam development.<br />I would love to hear from you more on advanced topics like Factory and Managed Seam components, and real life use cases from the scope management prospective...<br />Cheers and Merry Christmas!<br />Andy.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6137205730562326735.post-66633816059319885032009-12-02T10:38:58.792-08:002009-12-02T10:38:58.792-08:00Excelent, thank you!!Anonymousnoreply@blogger.com