Passing Params

[Mary Cole]

Hi,
I have a page with a command button on it. On click of the button ,it calls a method in a bean which calls a BO class and gets a new VO object. If the new VO object is not null, then I need to extract some attributes of the new VO and pass it as request params to the new xhtml. The bean for the new XHTMl will read the params and displays appropriate data.How do I do this using JSF2.0

public String addToDB() {

//call the BO 
....
....
return "newPage"

//can I do like this? 
//return "newPage?param1=value¶m2=value2" 

[Prithvi Sehgal]

Hello Mary,

Please check this

It states to use a conversation scope but then you can't use this one on Tomcat, you need
application server like GlassFish.

HTH,

[Prithvi Sehgal]

Hello,

Alternatively, you also put your object in the flash scope like this

ELFlash.getFlash().put("user(key)", yourobject)

and in the next page use the value as

#{flash.user.name}

Additionally, i was trying. It will only work page to page basis. Not with Ajax. I guess you have to put it in servlet
request as an attribute and then access it. It could be something like this

  ExternalContext context = (ExternalContext) FacesContext.getCurrentInstance().getExternalContext();
  ServletRequest request = (ServletRequest)context.getRequest();
  request.setAttribute("userid", "prithvi");

But unfortunately, i am unable to access the request parameter in the new page.

Hope this helps.

BR,

[Prithvi Sehgal]

Hello,

Currently, i have found one solution, that you inject that bean as a managed property in the current bean.
You can do it either by the use of @ManagedProperty or explicitly set in faces-config.xml. I am also finding
out the proper way of passing parameters. As soon as i get some, i will update you.

My faces-config.xml looks something like this

<managed-bean>
     <managed-bean-name>userBean</managed-bean-name>
     <managed-bean-class>com.jsfcompref.register.UserBean</managed-bean-class>
     <managed-bean-scope>request</managed-bean-scope>
</managed-bean>

<managed-bean>
     <managed-bean-name>testFlashScope</managed-bean-name>
     <managed-bean-class>com.jsfcompref.register.TestFlashScope</managed-bean-class>
     <managed-bean-scope>request</managed-bean-scope>
     <managed-property>
         <property-name>userBean</property-name>
          <value>#{userBean}</value>
 </managed-property>
</managed-bean>

</faces-config>

My action method looks like this

public String test(){
         userBean.setFirstName("Prithvi");
      //  UserBean bean = new UserBean();
      //  bean.setFirstName("Prithvi");
//        ServletRequest request = (ServletRequest)FacesContext.getCurrentInstance().getExternalContext().getRequest();
//
//        ServletResponse response = (ServletResponse)FacesContext.getCurrentInstance().getExternalContext().getResponse();
//                 //("user",user);
//        //ServletRequest request = (ServletRequest)context.getRequest();
//        request.setAttribute("userid", "prithvi");
//        System.out.println("Came here");
//        RequestDispatcher rd = request.getRequestDispatcher("testf.xhtml");
//        try {
//            rd.forward(request, response);
//        } catch (ServletException ex) {
//            Logger.getLogger(TestFlashScope.class.getName()).log(Level.SEVERE, null, ex);
//        } catch (IOException ex) {
//            Logger.getLogger(TestFlashScope.class.getName()).log(Level.SEVERE, null, ex);
//        }
       // ELFlash.getFlash().put("test", bean);
       return "testf";
    }

HTH,

[Tim Holloway]

Passing parameters isn't really JSF's style. More typically, you'd set properties in a backing bean and make that backing bean available to the next process down the line. Typically that bean would be in session or flash scope.

[Mary Cole]

ELFlash worked, thanks

[Prithvi Sehgal]

Yes, but remember it won't work for an Ajax request.

As instructed by TOM, the best practice is to introduce managed properties.

HTH,