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: pass (athena.apache.org: domain of tolyen@gmail.com designates
 66.249.82.227 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=pAupyFjXl/wvRyaWPBag6n3vSKszy6S0Hhlh6virzbR6jQi2zpiBn7nA0GukHTVCDUPrRSUz0rtQZr9F9/x5Mlzql0bV1784WsqANb919i5fXvinW004G0PGi6VMqxQ1HWCP8cTLxFMtsELfS7gqgzzyjNwQ8xDLcklWY7OoK5U=
Message-ID: <ee4c78a20708231010j7c6b5464i7ac0c1abd2bbbd23@mail.gmail.com>
Date: Thu, 23 Aug 2007 20:10:46 +0300
From: "=?ISO-8859-1?Q?Toni_Lyytik=E4inen?=" <tolyen@gmail.com>
To: "Struts Users Mailing List" <user@struts.apache.org>
Subject: Re: Sanitize Text
In-Reply-To: <46CDBD44.3060905@fdar.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_13215_1752188.1187889046525"
References: <4a12aaf80708230953l23e9a364hb014efe2f6cb0edb@mail.gmail.com>
	 <46CDBD44.3060905@fdar.com>

------=_Part_13215_1752188.1187889046525
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

You could just override the string conversion in xwork:

http://struts.apache.org/2.x/docs/type-conversion.html

define something like this in xwork-conversion.properties

java.lang.String=org.example.MyConverter

Then create a class MyConverter that extends the XWorkBasicConverter and
override the behaviour of the convertValue method in the case of string to
string conversion.

I'm not sure if this is actually a good way, but it's easy enough and with
simple configuration it works everywhere in you webapp.

On 8/23/07, Ian Roughley <ian@fdar.com> wrote:
>
> This is a good approach.  In fact, you might start with the params
> interceptor - as it is responsible for assigning data to the action, and
> all that is needed is to sanitize before assignment.
>
> /Ian
>
> Richard Sayre wrote:
> > I was wondering what the best approach would be for taking form data
> > passed to an Action and removing 'special characters' from the data.
> > I am having issues with users pasting text from word docs etc.  We
> > only support ISO-8859-1 as of now and there are some characters that
> > Word will replace such as ' and " with character that are outside the
> > 8839-1 character set.
> >
> > I was thinking about an interceptor that would sanitize the request
> > parameters before they are passed to the action.  Is this a good
> > approach?  Can anyone suggest a better one?  It does not matter if it
> > uses Struts or not.
> >
> > Thank you
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> > For additional commands, e-mail: user-help@struts.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>

------=_Part_13215_1752188.1187889046525--