On Fri, 13 Aug 2004 14:51:25 +0900, Prasad, Kamakshya
<[EMAIL PROTECTED]> wrote:
> HI,
>
> Thanks a lot for the information.
> I was looking through the examples of Struts-faces integration library.
> What I found was in the backing bean method a url with query string
> parameters is created to dispatch to the struts action. Is this the only
> way to dispatch? What should be done in the cases where the no of
> parameters in the screen is huge?
>
> Please help me on this.
>
> This is the code piece
>
> /**
> * <p>Create a new subscription.</p>
> */
> public String create() {
>
> FacesContext context = FacesContext.getCurrentInstance();
> StringBuffer url = base(context);
> url.append("?action=Create");
> url.append("&username=");
> User user = (User)
> context.getExternalContext().getSessionMap().get("user");
> url.append(user.getUsername());
> forward(context, url.toString());
> return (null);
>
> }
>
No, the other way to dispatch is to submit to a URL that accepts a
form, and define a form bean to hold its parameters. Then, you can
make a setup action that prepopulates the form with values, and uses a
POST action instead of a GET action.
Note that his has been a weakness of the canonical Struts example app
from the very beginning ... it has nothing to do with the advent of
the Struts-Faces library, which (like JSF) encourages you to forget
that there is such a thing as a request URL with dynamically
calculated parameters.
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
