Re: CSS resources using url(...) syntax under Direct Connect
Re: CSS resources using url(...) syntax under Direct Connect
- Subject: Re: CSS resources using url(...) syntax under Direct Connect
- From: Paul Hoadley <email@hidden>
- Date: Mon, 30 May 2011 15:02:43 +0930
On 29/05/2011, at 6:25 PM, Paul Hoadley wrote:
> I've hit an issue that seems to be the one described at this point in a long thread about the improved Wonder JavaMonitor:
>
> http://osdir.com/ml/webobjects-dev/2010-11/msg00717.html
>
> I'm running an app from the command line, and accessing it via Direct Connect. (I'll explain this weird behaviour below.) Specifically, the browser can't find any resources referenced by the url(...) syntax from with CSS files. No complaints are logged anywhere, the app just returns an empty resource. (This is on Mac OS X, and it has nothing to do with case-sensitivity, spaces in filenames or typos: running through Eclipse returns the requested resources just fine.) I followed that thread above through to the end, but didn't see that the issue was resolved—was it? Does anyone know _any_ workaround for this?
Here's one using the hint from that thread that once an image had been displayed using a WOImage component, it was then available to the CSS file's url(...) reference. If I display on the front page of the app a div containing WOImage references to all the image files in WebServerResources, they then appear as intended by the CSS. I can set 'style="display: none;"' on that div and there's no visible difference. Obviously a complete hack, but it's sufficient for this very specific development scenario.
--
Paul.
http://logicsquad.net/
_______________________________________________
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