For the record, I found a workaround which will do for now. I had observed that
in the working cases the request handler key was ‘_wr_’ while in the broken
cases it was ‘wr’. In the Wonder code I found that a
ERXStaticResourceRequestHandler was registered under the ‘_wr_’ key, so in my
Applicat
also double check case, linux FS is case sensitive
> On 15 gen 2016, at 18:44, Amedeo Mantica wrote:
>
> the file / entire path permissione are correct ?
>
>
>> On 15 gen 2016, at 13:32, Rudi Angela wrote:
>>
>> On my dev machine it works when started from eclipse, no problem there. But
>>
the file / entire path permissione are correct ?
> On 15 gen 2016, at 13:32, Rudi Angela 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
I am not sure what fixed it but it's working now. I did the class generation
Chuck suggested and I was adding a prototype idLong to our
EOJDBCOraclePrototypes as we have some huge tables that exceed MAX integer. We
were seeing some Integer overflow exceptions for attributes defined as
prototype
Install VMWare ESXi on those Mac Mini, and install whatever you want (CentOS,
Ubuntu, OS X, Windows) inside virtual machines.
De : webobjects-dev-bounces+probert=macti...@lists.apple.com
de la part de
Theodore Petrosky
Envoyé : 15 janvier 2016 09:30
À
Hi,
I'm trying to build JavaMonitor from Wonder source on Windows. I have Eclipse
4.4 and Java 7.
I want to create a custom JavaMonitor build with these changes mentioned by
Markus Stoll.
add this override in your Application class:
private static String[] myAppExtensions = {};
public String[]
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 wrote:
>
> _wr_ is used when direct
_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 :
>
> Further experimentation on my development laptop gave the following results:
> If I run the applic
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-ref
The URLs come from ERXResourceManager.urlForResourceNamed(). Is
ERModernDefaultSkin open in eclipse and correctly configured?
> Am 15.01.2016 um 12:05 schrieb Rudi Angela :
>
> This is not a split deploy (and not meant to be).
> I forgot to mention that on my MacBook the same code runs without p
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 c
> 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 some
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.
> On 15 jan. 2016, at 11:46, Fabian Peters wrote:
>
> Hi Rudi,
>
> So you don't get a 404 response for the image URL? Have you lo
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 :
>
> Hi there,
> I’m running a D2W (Modern Look) application standalone (no Apache), built
> with the latest stable Wond
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
What are the paths ?
Sent from my iPhone
> On 15 Jan 2016, at 11:11, Rudi Angela wrote:
>
> 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 CS
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 butto
17 matches
Mail list logo
