Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
I've been seraching about what's the difference between managed beans and backing beans and i've allready got the idea but i came through a website that mentioned this fact (or claim) for which i don't understand the reason : "Backing Beans should be defined only in the request scope". Is that even correct? If so ... why??
There is no difference between the terms managed bean and backing bean in the context of JSF. The Java EE 6 tutorial uses them interchangeably.
You don't quote the website so there is no context to the author's generalization but request scope is often preferred to broader scopes for performance and concurrency reasons.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
Liferay internally uses spring and hibernate. In that perspective, I want to ask that is it correct to say that Liferay is built on top of Spring and hibernate. Please correct me if I am wrong...thanx in advance.
If you also use in a context where you assume that it is not exclusively built on top of those frameworks, you will be correct.
Hibernate and Sprint are 2 pillars of several that sustain Liferay. Hibernate for instance is essential for developers using Liferay as well, even if they do not know or do not care about how the service builder does its job.
Liferay 7 is a bit different as we are seeing OSGi becoming more and more important, and significantly more utilized for building custom modules and sometimes replacing spring functionality.
Overall, it depends on your context and angle. Struts, Spring, Hibernate, OSGi are all mixed in harmony with Apache libraries, scribe and other famous libraries to build Liferay. And this is just with regards to back-end stuff.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 7 years ago.
Improve this question
Is it possible to use the following APIs with tomcat (as a lightweight server):
JSF, JPA, JTA, JAAS, CDI, Bean Validation.
Yes. Except of JAAS.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
Can I run JavaServer Faces technology on tomcat server, or I need to use application server, like glassfish, jboss etc?
Thanks.
Can I run JavaServer Faces technology on tomcat server
Yes.
or I need to use application server, like glassfish, jboss etc?
No.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
On the Thoughtworks Technology radar - they put Java Server Faces on Hold - stating:
We continue to see teams run into trouble using JSF -- JavaServer Faces -- and are recommending you avoid this technology. Teams seem to choose JSF because it is a J2EE standard without really evaluating whether the programming model suits them. We think JSF is flawed because it tries to abstract away HTML, CSS and HTTP, exactly the reverse of what modern web frameworks do. JSF, like ASP.NET webforms, attempts to create statefulness on top of the stateless protocol HTTP and ends up causing a whole host of problems involving shared server-side state. We are aware of the improvements in JSF 2.0, but think the model is fundamentally broken. We recommend teams use simple frameworks and embrace and understand web technologies including HTTP, HTML and CSS.
As I understand it, they're basically saying you can fall into a trap if you wrap a stateless protocol like http with a stateful abstraction. ie that a team can run into trouble wrapping their heads around this.
My question is: Is there evidence to suggest Thoughtworks' assertion that JSF is a broken abstraction?
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
JSF lifecycle with real example.
JSF have request,processvalidation,render respose,invoke application,update model values.These event when should occuring in the real application ?
For example:
Login application.
username,password:checking in the database.so Could please give me the how the lifecycle occuring in this application.
Please help me.
There is an excellent tutorial by BalusC here:
Debug JSF lifecycle.
If you take the time to read it and put it into practice you'll acquire a pretty nice understanding of the JSF lifecycle.