[JBoss Seam] - Re: Seam URLs and request processing
by petemuir
This is a facelets-centric response:
anonymous wrote : a) when I go to a Seam URL, e.g. seam-registration/register.seam, is the URL processed by JSF or by Seam?
JSF, but Seam has hooks into JSF that do magic
anonymous wrote : c) is there any direct relationship between the Seam component names (e.g. the session bean annotated with @Name("register")) and the URL /register.seam?
No, to refer to properties from register in register.seam you would have to use #{register.property}
anonymous wrote : I notice that for the dvd.xhtml page in the DVD example, you explicitly point to an action by using the pages.xml - but for other pages, you have nothing in pages.xml. Why is it that you have to explicitly put this code in pages.xml for some pages and not for others?
JSF is a component based framework. pages.xml adds some action framework ability by allowing an action to be run when a page is loaded. If an action is specified in pages.xmlit is run before the page is processed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964087#3964087
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964087
19 years, 9 months
[Clustering/JBoss] - Why not always use cache invalidation option?
by anarvekar
I have a question regarding the 'Standard CMP 2.x EntityBean with cache invalidation' container configuration vs. 'Standard CMP 2.x EntityBean'. I know what both of these do. My question is this. When would I ever want to use 'Standard CMP 2.x EntityBean' because 'Standard CMP 2.x EntityBean with cache invalidation' seems to give me the benefits of commit option A when I am in a single server mode and in a clustered environment it gives me the benefit of keeping the entity beans in sync by invalidating the cache on the other servers.
Wouldn't you always want to use the cache invalidation option regardless of whether you are in a single-server or clustered setup? This is of course based on my assumption that in a single-server setup, the cache for the single server will not be invalidated (that would lose the benefit of commit option A). What am I missing here?
Thanks.
Ashish.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964084#3964084
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964084
19 years, 9 months