managed-bean

I am using PrimeFaces with JSF2. I am trying to authenticate user by sending login and password as an Ajax request. And in the action method of the backing bean, I am trying to validate user and redirect to a new view if the validation succeeds. Is this possible while using primefaces? Because I think with primefaces' p:commandButton , I can only either have ajax behavior or the navigation. Yes, just send a redirect instead of a (default) forward as outcome. The <navigation-case> -less JSF 2.0 way would be appending ?faces-redirect=true to the outcome string in the action method. E.g. public

Is there some way how to redirect page to other page from Java method? I'm able only to forward it using: FacesContext.getCurrentInstance().getExternalContext().dispatch("/foo.xhtml"); or using navigation-rules of faces-config.xml . Do you have any ideas? Not sure what you're after, but the ExternalContext#dispatch() does only a forward, not a redirect. You'd like to use ExternalContext#redirect() instead. externalContext.redirect("foo.xhtml"); or even external (which is not possible with dispatch) externalContext.redirect("http://stackoverflow.com"); You'd normally like to do this in bean's

I figured that there are two general ways to obtain an auto-created CDI managed bean instance via BeanManager when having solely a Bean<T> to start with (which is created based on Class<T> ): By BeanManager#getReference() , which is more often shown in snippets: Bean<TestBean> bean = (Bean<TestBean>) beanManager.resolve(beanManager.getBeans(TestBean.class)); TestBean testBean1 = (TestBean) beanManager.getReference(bean, bean.getBeanClass(), beanManager.createCreationalContext(bean)); By Context#get() , which is less often shown in snippets: Bean<TestBean> bean = (Bean<TestBean>) beanManager

THIS PROBLEM IS ALREADY SOLVED IN THE MYFACES 2.1 IMPLEMENTATION I have a link which passes an Integer parameter properly like this: <h:link outcome="/process/createProcess"> <f:param name="id" value="#{process.idprocess}" /> Edit </h:link> It goes to "createProcess.xhtml?id=21" properly, and I have this code in the request scope backing Bean createProcess: @ManagedProperty(value="#{param.id}") private Integer idProcess; private Process newProcess; @PostConstruct public void init() { log(); if (idProcess!=null) newProcess = Dao.getProcessDAO().get(idProcess); else newProcess = new Process(); }

In my application in some places we are using @ManagedBean annoation for Person bean and for the same Person bean we defining in the faces-confing.xml like below at the same time. @ManagedBean("name=person") @SessionScoped Public class Person{ } faces-config.xml <managed-bean> <managed-bean-name>person</managed-bean-name> <managed-bean-class>com.test.sample.Person</managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean> my question is does this approach create two instances for the Person bean or it does matter if I do this? Does this have any effect on performance