I opted to create my own WORequest class and fix only this bug there.
So far, it is working perfectly.
Thanks,
sacha
On Jan 25, 2010, at 1:55 PM, Mike Schrag wrote:
Once you stray outside of ERXAjax*, you definitely take on
dependencies ... I just committed a fix that removes two
presumptions that you are inside of an ERXApplication. I would make
sure to run your test cases if you switch over.
ms
On Jan 25, 2010, at 4:51 PM, Sacha Michel Mallais wrote:
On Jan 25, 2010, at 1:08 PM, Mike Schrag wrote:
If you're extending ERXApp, I seem to recall that we fix this
ourselves "the hard way," though I ran into this in 5.3 as well --
that you'd randomly get a port stuck on when you didn't want it
(80 or 443).
In ERXRequest:
Thanks, Mike, I think that will work... we're using ERXAjaxApp,
which apparently doesn't use ERXRequest.
Anyone know of any gotchas if I just override _createRequest in my
Application and return an ERXRequest (like ERXApplication does)?
Does ERXRequest play well with ERXAjaxApplication?
sacha
--
Sacha Michel Mallais Big Kahuna
Global Village Consulting Inc. http://www.global-village.net/
PGP Key ID: 7D757B65 AIM: smallais
Blessed is the WO-geek, for he shall inherit from NSEarth (Jobs 3:14)
--
Sacha Michel Mallais 800 kg gorilla
Global Village Consulting Inc. http://www.global-village.net/
PGP Key ID: 7D757B65 AIM: smallais
1. Never tell everything at once.
-- Ken Venturi, Ken Venturi's Two Great Rules of Life
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
