Re: Bug in WOContext.directActionURLForActionNamed() when using query dictionary
Re: Bug in WOContext.directActionURLForActionNamed() when using query dictionary
- Subject: Re: Bug in WOContext.directActionURLForActionNamed() when using query dictionary
- From: David LeBer <email@hidden>
- Date: Wed, 26 Apr 2006 21:21:33 -0400
On 26-Apr-06, at 8:32 PM, Mike Schrag wrote:
David LeBer, Nov 15 2005 says a quick Mail search ... This teeters
on a religious debate I believe :) It comes down to how you are
using the result of that method. If you use it inside of an <a
href = ".."> then it's SUPPOSED to be escaped (to be XHTML
compliant). However, apparently it fails if you try to use it with
a WORedirect. I have no idea what happens if you try to use that
inside of Javascript as a location = '..', and obviously if
processing it in some other way internally, it will probably throw
your code for a loop. So basically, if you were expecting it the
old way, it's broken, but if you thought it was broken before, it's
fixed :)
Yeah, what he said :-)
I blogged about it here: <http://david.codeferous.com/?p=191>
I ended up doing this:
url = url.replaceAll("&", "&");
before handing the url off the the WORedirect. Ugly yes, but it works.
--
;david
--
David LeBer
Codeferous Software
'co-defer-ous' adj. producing or containing code
site: http://www.codeferous.com
blog: http://david.codeferous.com
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden