Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <461A89F8.9030102@Newfield.org>
Date: Mon, 09 Apr 2007 14:46:16 -0400
From: Dale Newfield <Dale@Newfield.org>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: Struts Users Mailing List <user@struts.apache.org>
Subject: Re: resume after login feature
References: <4649a9a20704081817i1872d06es768bbf99509eeeb2@mail.gmail.com>
	 <329411.69960.qm@web56709.mail.re3.yahoo.com>
 <4649a9a20704082150g5b0aec4dpa42f263214e509b6@mail.gmail.com>
In-Reply-To: <4649a9a20704082150g5b0aec4dpa42f263214e509b6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jae K wrote:
> Last but not least, it is not obvious that the OGNL expressions need
> to be enclosed in ${} when used in the struts config file. (Is this
> even true? I don't know since it's not documented! It certainly isn't
> documented so in the OGNL documentation).

http://struts.apache.org/2.0.6/struts2-core/apidocs/org/apache/struts2/dispatcher/StrutsResultSupport.html
documents where such OGNL expressions can be used, and refers to
http://struts.apache.org/2.0.6/struts2-core/apidocs/com/opensymphony/xwork2/util/TextParseUtil.html#translateVariables(java.lang.String,%20com.opensymphony.xwork2.util.ValueStack)
to explain just how these expressions are substituted when found in 
parsable strings.

I don't disagree that it could be documented in more places, but I would 
disagree that "it's not documented".

-Dale

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org