Re: SSDD and ProjectWonder
Re: SSDD and ProjectWonder
- Subject: Re: SSDD and ProjectWonder
- From: Tarun Reddy <email@hidden>
- Date: Tue, 28 Aug 2007 09:35:21 -0600
Thank you for your suggestions. I looked over the wonder-disc list to
see the root causes, and it seems like there were many
recommendations for moving to native webobjects app and using the
mod_webobjects adapter.
Any benefits to this? And any simple step-by-step descriptions of
this? I found very few on the web and they all use a Solaris install CD.
Thanks,
Tarun
On Aug 27, 2007, at 8:19 AM, Jonathan Meijer wrote:
I had the same issue and did just that. Works well enough to count as
a solution.
Jonny
On 8/27/07, Travis Britt <email@hidden> wrote:
On Aug 27, 2007, at 12:21 AM, Tarun Reddy wrote:
Simply switching Application back back to WOApplication (reverting
steps 3 and 4 below) restores the application to working status.
Search for servlet and ERXApplication on the wonder-disc list.
Basically, Application.main() isn't called when the WO app is run in
a servlet container, which is a problem for ERXApplication. You might
be able to get around this by subclassing WOServletAdaptor and
overriding init() to call ERXApplication.setup(). That's as far as I
got when I was dealing with this a few months ago. (We're no longer
deploying in servlet containers and without the pressing need I
haven't had time to look into it again.)
tb
_______________________________________________
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