I believe you may be correct with respect to WOActionURL, as it is an
element intended to be used in generating HTML. However, I don't
agree that directActionURLForActionNamed should be returning URLs
with escaped ampersands. There should be a separate method which
transforms the URL to esc
Am 25.05.2006 23:48 Uhr schrieb "David Haggerty" unter <[EMAIL PROTECTED]>:
> We recently upgraded to 5.3.1 from 5.2.4 and are having problems with
> WOActionURL. We use WOActionURL for Ajax and the & is adding the HTML
> escape in 5.3.1 but never did this in 5.2.4. This is causing it to not
> f
rectActionURLForActionNamed(). Sometimes you need an encoded
URL, sometimes you don't.
Xavier
- David
-Original Message-
From: Dev WO [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 5:26 AM
To: Gary Teter
Cc: David Haggerty; webobjects-dev@lists.apple.com
Subject: Re: Prob
ects-dev@lists.apple.com
Subject: Re: Problems with WOAction in WO 5.3.1
Hello,
This is not a bug!
the & must be escaped in & in a hyperlink, this is the (X)HTML
specification. It was broken in 5.2.4 and corrected in 5.3.1 because
it's the correct behavior.
The remaining bug I know of
r
Cc: David Haggerty; webobjects-dev@lists.apple.com
Subject: Re: Problems with WOAction in WO 5.3.1
Hello,
This is not a bug!
the & must be escaped in & in a hyperlink, this is the (X)HTML
specification. It was broken in 5.2.4 and corrected in 5.3.1 because
it's the correct behavior.
T
Hello,
This is not a bug!
the & must be escaped in & in a hyperlink, this is the (X)HTML
specification. It was broken in 5.2.4 and corrected in 5.3.1 because
it's the correct behavior.
The remaining bug I know of is when using the href binding with
parameters, it leads to & in code which
Yes, this was broken in 5.3.1, but apparently fixed in 5.3.1. That
is, it was broken with the 5.3.1 that was introduced with (if I
recall) a Mac OS X Server updated), and may be fixed with the 5.3.1
that was introduced with Xcode 2.3.
(Perhaps Apple has exceeded its version number budget, a
We recently upgraded to 5.3.1 from 5.2.4 and are having problems with
WOActionURL. We use WOActionURL for Ajax and the & is adding the HTML
escape in 5.3.1 but never did this in 5.2.4. This is causing it to not
find the session and the URL is then invalid.
Any ideas? Is this a bug in 5.3.1?
Th
