also double check case, linux FS is case sensitive > On 15 gen 2016, at 18:44, Amedeo Mantica <amedeomant...@me.com> wrote: > > the file / entire path permissione are correct ? > > >> On 15 gen 2016, at 13:32, Rudi Angela <webobjects-...@olmeca.nl> wrote: >> >> On my dev machine it works when started from eclipse, no problem there. But >> I’m trying to run it on the Linux test machine. No eclipse there, but I did >> install WebObjects/Wonder as detailed on the wocommunity site. >> >>> On 15 jan. 2016, at 13:14, Fabian Peters <lists.fab...@e-lumo.com> wrote: >>> >>> _wr_ is used when direct connect and rapid turnaround are enabled. I'd make >>> sure the ERModernDefaultSkin project is open and configured correctly. >>> >>>> Am 15.01.2016 um 13:09 schrieb Rudi Angela <webobjects-...@olmeca.nl>: >>>> >>>> Further experimentation on my development laptop gave the following >>>> results: >>>> If I run the application with the woa directory where it was created >>>> (inside dist directory of my project) then all works fine. >>>> If I first move the woa directory to somewhere else then I get the same >>>> problem with CSS-referenced images. >>>> If I run the application with the woa directory where it was created, but >>>> with WOAllowRapidTurnaround=false, then I get the same problem. >>>> Looking at the URL’s I found that all the dysfunctioning cases have URL’s >>>> with request handler key ‘wr’ and in all the functioning situations the >>>> key was ‘_wr_’. >>>> Does this help to narrow the problem? >>>> >>>>> On 15 jan. 2016, at 12:05, Rudi Angela <webobjects-...@olmeca.nl> wrote: >>>>> >>>>> This is not a split deploy (and not meant to be). >>>>> I forgot to mention that on my MacBook the same code runs without >>>>> problems. Both platforms use Java 8. >>>>> Any pointers to the Wonder code where this is handled is appreciated. >>>>> >>>>>> On 15 jan. 2016, at 11:56, lists.fab...@e-lumo.com wrote: >>>>>> >>>>>>> I have checked on the server if the file existed and if user appserver >>>>>>> had permission to it and that was all fine. Indeed I don’t get a 404, >>>>>>> but an empty response. >>>>>> >>>>>> >>>>>> And is this meant to be a split deploy with a webserver? The URLs you >>>>>> posted in the other reply (cited below) look like something from >>>>>> development mode/direct connect. I'd expect to see a URL like this: >>>>>> >>>>>> /WebObjects/pldProjektanmeldung.woa/Contents/Frameworks/ERModernDefaultSkin.framework/WebServerResources/default_login_page.css >>>>>> >>>>>> I'd say the relative URL from the CSS fails in the URL context you have. >>>>>> >>>>>>> The path to the stylesheet: >>>>>>> /cgi-bin/WebObjects/EmmaAdmin.woa/wr/wodata=/opt/Local/Library/WebObjects/JavaApplications/EmmaAdmin.woa/Contents/Frameworks/ERModernDefaultSkin.framework/WebServerResources/default_login_page.css >>>>>>> The path to the image referred to from the stylesheet (login button): >>>>>>> /cgi-bin/WebObjects/EmmaAdmin.woa/wr/wodata=/opt/Local/Library/WebObjects/JavaApplications/EmmaAdmin.woa/Contents/Frameworks/ERModernDefaultSkin.framework/WebServerResources/btn_blu.png >>>>>>> >>>>>>>> On 15 jan. 2016, at 11:46, Fabian Peters <lists.fab...@e-lumo.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Hi Rudi, >>>>>>>> >>>>>>>> So you don't get a 404 response for the image URL? Have you looked at >>>>>>>> the file on the webserver's file system? >>>>>>>> >>>>>>>> Fabian >>>>>>>> >>>>>>>>> Am 15.01.2016 um 11:11 schrieb Rudi Angela <webobjects-...@olmeca.nl>: >>>>>>>>> >>>>>>>>> Hi there, >>>>>>>>> I’m running a D2W (Modern Look) application standalone (no Apache), >>>>>>>>> built with the latest stable Wonder7 frameworks. The Modern Look >>>>>>>>> buttons have a background image they get from the CSS definition. >>>>>>>>> When loading the login page, the ModernLook CSS file is served >>>>>>>>> correctly, but the button image it refers to is served as an empty >>>>>>>>> response (content length: 0 bytes). >>>>>>>>> Any ideas anyone? >>>>>>>>> >>>>>>>>> Rudi Angela >>>>>>>>> _______________________________________________ >>>>>>>>> Do not post admin requests to the list. They will be ignored. >>>>>>>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>>>>>>>> Help/Unsubscribe/Update your Subscription: >>>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com >>>>>>>>> >>>>>>>>> This email sent to lists.fab...@e-lumo.com >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Do not post admin requests to the list. They will be ignored. >>>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>>>> Help/Unsubscribe/Update your Subscription: >>>>> https://lists.apple.com/mailman/options/webobjects-dev/webobjects-dev%40olmeca.nl >>>>> >>>>> This email sent to webobjects-...@olmeca.nl >>>> >>>> >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/webobjects-dev/lists.fabian%40e-lumo.com >>>> >>>> This email sent to lists.fab...@e-lumo.com >>> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/amedeomantica%40me.com >> >> This email sent to amedeomant...@me.com >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
