Re: EJB3.0 and Backing Beans Design

[Grigoras Cristinel]

Thomas Heute wrote: Please stop fudding around... You went a bit too far. This one is funny: " I think seam is getting too complex - way too much to read, no?" If we could measure the complexity of a framework by the number of pages of the documentation, the worse documented framework would be the simplest... We decided to include lot of examples to help users. Plus you don't have to use everything, remember you can have ejb3, messaging, jbpm, JBoss rules... But you don't have to use them all ! But stilll they are here and come for free the day you will need them. This is called a reference documentation. I have nothing against you or the navigation tag (i should have a look at it) i just hate when people try to stop other people before they try something new... Read Seam's forum (not censored) if you want users' point of view. We truely believe in JSF and pushing it up hard, so we really are in the same camp. Let's save our energy to make it better. Regards, Thomas. Hi Thomas, In this case maybe you can fix inputSugestAjax component from myfaces-sandbox. Seam is building other kind of solution for Ajax. that myfaces team and the number of differences(incompatibilities) is increasing day by day. Maybe you need to look more to the others ideas about how to solve problems. Cristi. On Thursday 06 July 2006 14:58, Mario Ivankovits wrote: Hi Rogerio! But this deps comes with JBoss Seam distribution, somebody found any other big issue on JBoss Seam beyond this one? Even if they come with the distribution, you have to take care of them. Additional issues? Well, personally I dont like it to use annotations for nearly everything. And seam would like to solve too much. For example JSF has some issues with redirects, e.g. it looses all FacesMessages added so far. The next page wont display them. Seam solve this with an @In annotation. But this is a JSF defect, so it needs to be solved on JSF level. In MyFaces we solved it too, but the user do not have to learn any new paradigm, just use JSF as you know it. Also the "start on GET request" is a problem JSF has (aka bookmarkable), we should find a solution which works outside of any heavyweight new framework. I think seam is getting too complex - way too much to read, no? http://docs.jboss.com/seam/latest/reference/en/html/index.html All this injection, bijection, multiple roles for beans .... But ok, at all maybe no real issues - and I am biased, I am the developer of the conversation tag and I like it to have small pieces of code which tries to solve a single problem - and not to save the world ;-) Ciao, Mario