Raible Designs

Posted by Gary VanMatre on November 28, 2004 at 05:42 PM MST #

<h:dataTable value="#{viewcontroller.persons}" var="e" >
...


<h:outputLink value="userProfile.jsp"> 
   <f:param id="username" name="username" value="#{e.username}" />

   <h:outputText value="#{e.username}" />
</sh:outputLink>

You might try using an EL in the managed bean for your detail page.

<managed-bean>
   <managed-bean-name>adduser</managed-bean-name>

   <managed-bean-class>xxx.User</managed-bean-class>
   <managed-bean-scope>request</managed-bean-scope>
   <managed-property>
      <property-name>username</property-name>

      <value>#{param['username']}</value>
   </managed-property>
</managed-bean>

... or ....

I might handle on the details page using the prerender callback of the script collector

<hx:scriptCollector preRender="#{viewcontroller.load}">
 
public void load(FacesContext context) {
   

     // it looks like Shale is going to have a ViewController and BeanMapper to handle this kind of thing?

    ValueBinding valuebinding =  context.getApplication().createValueBinding("#{addUser}");
    xxx.User user = (User) valuebinding.getValue(context);


    String userid = (String) context.getRequestParameterMap().get("username");
    user.setUserid(userId);
}

Base tag render example....

public class OutputBaseRenderer extends HtmlBasicRenderer {

	public void encodeEnd(FacesContext context, UIComponent uicomponent)
		throws IOException {

		ResponseWriter writer = context.getResponseWriter();
		writer.write("<base href=\"");
		writer.write(getActionURL(context, (OutputBase) uicomponent));
		writer.write("\">");

		writer = null;
	}

	protected String getActionURL(
		FacesContext context,
		OutputBase uicomponent) {

		String uri = context.getViewRoot().getViewId();
		HttpServletRequest request = (HttpServletRequest) context.getExternalContext().getRequest();
		StringBuffer url = new StringBuffer();
		url.append(request.getRequestURL());
		
		// remove the Schema
		for (int i = 4; i < 5; i++ ) {
		   if (url.charAt(i) == ':') {
		      url.delete(0, i);
		      break;		
		   }
		}

                // remove all but the server name
		for (int i = 3; i < url.length(); i++ ) {
		   if ((url.charAt(i) == ':') || (url.charAt(i) == '/')) {		       	
			   url.setLength(i);
			  break;		
		   }
		}
		
		
		if (uicomponent.isSecure()) {
		   url.insert(0, "https");	
		} else {
		   url.insert(0, "http");			
		}
		url.append(":").append(uicomponent.getServerPort());
		
		url.append(context.getApplication().getViewHandler().getActionURL(
				context,
				uri));

        uri = null;
        request = null;
		return url.toString();
	}
}

Posted by Gary VanMatre on November 28, 2004 at 07:10 PM MST #

Posted by Matt Raible on November 28, 2004 at 07:32 PM MST #

<h:dataTable var="row" ... >
  ...
  <h:column>
    <h:commandLink action="some_screen"
                   immediate="true">
      <h:outputText value="yada-yada/>
        <xyz:param name="id"
                   value="#{row.id}"
                   copyTo="#{ContextBean.id}"/>
    </h:commandLink>
  </h:column>
  ...
</h:dataTable>

public class ParamComponent extends UIParameter
{
    public void decode(FacesContext context)
    {
        super.decode(context);

        ValueBinding copyTo = getValueBinding("copyTo");

        if ( copyTo == null )
        {
            return;
        }

        String name  = getName();
        Object value = context.getExternalContext().
                            getRequestParameterMap().get(name);
        if ( value == null )
        {
            return;
        }

        copyTo.setValue( context, value );
    }
...
}

Posted by Genie on November 30, 2004 at 08:37 AM MST #

In certain circumstances Struts chaining is useful. (The commenting mechanism makes it hard to insert the XML here.) If the OK result from page1.jsp is found the next forward action can be to servlet identified as preparePage2. An OK result from that servlet can cause page2.jsp to be emitted. Note that I assume I don't care about the Struts repopulation problem because some other page (and ActionForm) is being created.

Without this preparePage2 servlet the page2.jsp page must prepare its own database structures, or the action handling the POST of page1.jsp must know enough about navigation to prepare page2.

So, if I want to have this behavior in Faces can I convince to-view-id to go to a servlet destination? I've seen no examples of to-view-id that *didn't* involve a .jsp reference.

Posted by Jerome Mrozak on January 05, 2005 at 09:02 PM MST #