I have a very simple managed bean LOB which is used for reading existing LOBs(from DB) as well as for writing new LOB to DB.
I have a JSF component which i开发者_如何学JAVAs initialized from a managed bean\'s getter getProperty(). Is it mandatory to also have a setter setProperty() in that managed bean?It depends.
I\'ve recently been given a project to work on that involves writing a web application.I\'ve never done Java EE before.A lot of resources on the web are dated and I\'m having trouble figuring out what
I have an application that has a bean that holds a list of Contacts which are referenced from various domain objects throughout the application:
I\'m running with the following problem. I have a few Managed Beans that are shared between, at this moment, two JSF applications. As I don\'t want to copy and paste the code in the two (more in the
When I access 开发者_StackOverflow中文版to my page for the fist time, the managed bean used by the page is instantiate two times (I pass two times in the contructor, with the same stack trace) :
I have a managed bean with lots of methods. I want to log the entry and exit times of each method invoc开发者_JAVA技巧ation . I thought of reusing the Interceptor that works successfully with my EJB\'
I call the managed开发者_如何学JAVABean OverzichtAlle.java from the jsf page overzichtAlleGroepen.xhtml
I noticed that there are different bean scopes like: @RequestScoped @ViewScoped @FlowScoped @SessionSco开发者_开发知识库ped
Can anyone help me to understand the JSF managed bean scope from a concurrency perspective ? My Understanding:
加载中,请稍侯......