To earn money on java go to upwork.com
To earn money on java go to upwork.com
Experience keeps a dear School, but Fools will learn in no other.
---
Benjamin Franklin - Postal official and Weather observer
To earn money on java go to upwork.com
But I also don't know very well which scope it is better to use.
I have my register page and user profile page where almost every control has <f:ajax> element. These pages both use the same view scoped backing bean!
Is it worhty to create separate request-scoped bean for a few methods that can be put in request scope?
Of course these methods are in session scoped bean now!
And finally, as far a I know in MVC controller is what catches events fired by my ui components from view. Controller is also called listener.
I think that managed bean is just controller as it acts like listener. State of web app is kept in model (entities)
Model administration is done in EJB, CDI, they take EntityManager to update model or they invoke web service.
Anyway EJB controls transaction, security, concurrency to update model properly.
Model is where state of program is kept in web site but not in standalone GUI(Swing) where model defines state and behaviour of program!
Experience keeps a dear School, but Fools will learn in no other.
---
Benjamin Franklin - Postal official and Weather observer
The login page has no URL. Therefore you cannot provide a link to it.
JSF doesn't support role-checking at the tag level like Struts does, but you can do something similar without too much effort:
view plaincopy to clipboardprint?
<h:commandLink id="menu1_secure" value="Secure menu 1" action="..." rendered="#{user.authenticated}"/>
To earn money on java go to upwork.com
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime. |