Re: [OS-webwork] Request parameters not being set

Mon, 15 Sep 2003 09:41:20 -0700

Title: Message
Yep, it has both.  When I call the action directly it works fine (http://localhost:8080/secure/modules/admin/users/UserDetails.action?id=143).
 
Here is the class:
>>===================================================<<
package com.contego.arx.actions.user;
 
import com.contego.arx.domain.Person;
import com.opensymphony.xwork.ActionSupport;
 
public class Detail extends ActionSupport {
    private Integer id;
    private Person user;
 
    public String execute() throws Exception {
        user = Person.getPersonById(id);
        System.out.println( "Id: " + id );
        System.out.println( "User: " + user );
 
        return SUCCESS;
    }
 
    public Integer getId() { return id; }
    public void setId(Integer integer) {
        id = integer;
        System.out.println( "Setting ID: " + integer );
    }
 
    public Person getUser() { return user; }
    public void setUser(Person person) { user = person; }
}
>>===================================================<<
----- Original Message -----
Sent: Monday, September 15, 2003 11:27 AM
Subject: RE: [OS-webwork] Request parameters not being set

Does your Action have an "id" property? Does it have a getter and a setter? Sometimes the Java introspection stuff doesn't find a property with only a setter or only a getter...
-----Original Message-----
From: Chris Widhelm [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 12:22 PM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Request parameters not being set

In that case I already have the defaultStack set as the default interceptor which includes the ParameterInterceptor.
 
I have included all of the configuration as well as the jsp page that I am trying to access and the request.
 
Do you see anything that looks weird?
 
Still to no avail.  Here is my entire xwork.xml file.
 
>>=================================================<<
<!DOCTYPE xwork PUBLIC "-//OpenSymphony Group//XWork 1.0//EN" "http://www.opensymphony.com/xwork/xwork-1.0.dtd">
 
<xwork>
    <include file="webwork-default.xml"/>
 
    <package name="default" extends="webwork-default">
 
        <interceptors>
            <interceptor name="params" class="com.opensymphony.xwork.interceptor.ParametersInterceptor"/>
 
            <interceptor-stack name="defaultComponentStack">
                <interceptor-ref name="defaultStack"/>
            </interceptor-stack>
        </interceptors>
 
        <default-interceptor-ref name="defaultStack"/>
 
        <action name="UserDetails" class="com.contego.arx.actions.user.Detail">
            <result name="success" type="dispatcher">
                <param name="location">/secure/modules/admin/users/user_detail.jsp</param>
            </result>
        </action>
 
    </package>
</xwork>
>>=================================================<<
 
This is the JSP file that I am accessing:
 
>>=================================================<<
<%@ taglib uri="sitemesh-page" prefix="page" %>
<%@ taglib uri="webwork" prefix="ww" %>
 
<ww:action name="UserDetails" id="details"/>
<page:applyDecorator name="admin">
<table width="100%" cellpadding="2" cellspacing="0" border="0" class="STEP">
  <form action="" method="get">
    <ww:textfield label="First Name" name="FName" size="40" value="#details.user.FName"/>
  </form>
</table>
</page:applyDecorator>
>>=================================================<<
 
The request is:
 
 
 
 
 
----- Original Message -----
Sent: Monday, September 15, 2003 10:55 AM
Subject: RE: [OS-webwork] Request parameters not being set

This is just for defining the interceptors. You need to specify which interceptors are applied to your actions.
 
 
You can see that Action elements have interceptor-refs inside:
 
       <action name="Foo" class="com.opensymphony.xwork.SimpleAction">
            <param name="foo">17</param>
            <param name="bar">23</param>
            <result name="success" type="chain">
                <param name="actionName">Bar</param>
            </result>
            <interceptor-ref name="debugStack"/>
            <interceptor-ref name="defaultStack"/>
        </action>
You can also supply a default interceptor-ref which will be applied to Actions if no other interceptor-ref is supplied, like so:
<package name="default" extends="webwork-default">
        <interceptors>
            <interceptor-stack name="defaultComponentStack">
                <interceptor-ref name="component"/>
                <interceptor-ref name="defaultStack"/>
            </interceptor-stack>
        </interceptors>
        <default-interceptor-ref name="defaultStack"/>
        ...
</package>
See also http://wiki.opensymphony.com/space/Using+webwork-default.xml
-----Original Message-----
From: Chris Widhelm [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 11:15 AM
To: [EMAIL PROTECTED]
Subject: Re: [OS-webwork] Request parameters not being set

Is there any documentation on the available interceptors and how to configure them?
 
Here is my interceptor configuration section:
 
<interceptors>
    <interceptor name="params" class="com.opensymphony.xwork.interceptor.ParametersInterceptor"/>
 
    <interceptor-stack name="defaultComponentStack">
        <interceptor-ref name="component"/>
        <interceptor-ref name="defaultStack"/>
        <interceptor-ref name="params"/>
    </interceptor-stack>
</interceptors>
 
This doesn't seem to work.  *shrug*
 
The interceptor documentation that I have found in the xwork configuration section doesn't quite make it clear for me.
----- Original Message -----
Sent: Monday, September 15, 2003 10:03 AM
Subject: RE: [OS-webwork] Request parameters not being set

Did you apply the ParameterInterceptor to the Action? This is what sets the parameters into the Action.
-----Original Message-----
From: Chris Widhelm [mailto:[EMAIL PROTECTED]
Sent: Monday, September 15, 2003 10:59 AM
To: [EMAIL PROTECTED]
Subject: [OS-webwork] Request parameters not being set

I am in the process of switching to WW2 from WW1 and it appears that the parameters on a request are no longer being automatically set for an action.  Is this the case?
 
How do I access the parameters on a request?
 
Thanks,
 
Chris

Reply via email to