This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
Hi. What is the point of making session beans act as backing beans with event listener ? Backing beans aren't supposed to support remote access or distrubuted tx (as session beans). So, I just feel that making session beans acting as backing beans is just for marketing reasons (The JEE5 framework). Please note that I'm disdaining your work or this framework, I like Seam alot and it is one of the best frameworks today. Thanks.
I think the idea is to get rid all those XML in the faces-config.xml file.
You do not have to use EJB3 session beans. You can use POJOs with the @Name annotation (we call them Seam POJOs) as JSF backing beans as well -- this gives easy naming and dependency injection without the backing bean XML.
Originally posted by Michael Yuan: I think the idea is to get rid all those XML in the faces-config.xml file.
You do not have to use EJB3 session beans. You can use POJOs with the @Name annotation (we call them Seam POJOs) as JSF backing beans as well -- this gives easy naming and dependency injection without the backing bean XML.
With Seam POJOs, we don't have XML files also. Sorry, but I didn't get what you mean.
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to
run our stuff on 16 servers instead of 3.