Very true. Ironically, I think my couple of years away from WO, doing
java-only, probably improved me the most as a WO programmer. When I came back I
had a vastly different approach to WO—it was no longer the center of my
development universe, but rather just another framework to be integrated w
As you use more modern Java tools and libraries, it become increasingly
important to recognize the differences between “The WO Way” and “The Java Way”.
Trying to force one to be the other is a recipe for pain. As you have
experienced. :-) WOLifecyle needs to evolve.
Chuck
From: Paul Hoadl
Hi Hugi,
On 23 Jun 2017, at 6:17 pm, Hugi Thordarson wrote:
>> I’m stumped—any Maven aficionados want to chime in?
>
>
> WOLifecycle modifies the maven standard behaviour by enlisting src/resources
> for WO bundle resources only (equivalent to /Resources in Fluffy Bunny).
> However, the Ecli
Yes, that change to WOLifeCycle is The Right Thing To Do.
Chuck
From: Hugi Thordarson
Date: Friday, June 23, 2017 at 1:47 AM
To: Paul Hoadley
Cc: Chuck Hill , WebObjects Development
Subject: Re: java.util.logging and Maven builds
src/main/resources is a path to a Java resource. Contents/Res
Hi Robert,
You can add Logic Squad to your list. We build and maintain WebObjects
applications among other things, and we offer WebObjects consulting.
Regards,
--
Matt
http://logicsquad.net
https://www.linkedin.com/company/logic-squad/
On Fri, Jun 23, 2017, at 10:15 AM, Michael Kondratov wrot
This is expected HTML behaviour. You may find here
https://stackoverflow.com/questions/585396/how-to-prevent-enter-keypress-to-submit-a-web-form
some suggestions on how to prevent this.
--
Ralf Schuchardt
Am 23. Juni 2017 um 08:34:37, GILQUIN Pierre (pgilq...@citycable.ch) schrieb:
Hi,
L
>> src/main/resources is a path to a Java resource. Contents/Resources is a
>> path to a WebObjects resource. Java knows Jacques Schmidt about these.
>> Only WO classes know about this. Your Maven build needs to get this file
>> into the top level directory that the class files are under (w
