|
If you're not running in direct connect, you'll need to set up
Apache locally. After years of using it, I despise Apache however
:) Mostly due to its weird config format. I like to run in direct
connect. I've added a vert.x woadaptor to Wonder8 to make direct
connect a lot better. I still haven't worked out my strategy to
fully replace apache/monitor/wotaskd in production, but it will
probably be a docker container and standard kubernetes stuff.
If there are any bugs with jar resource loading, I think I've
fixed them in the new NSBundle. I've recently gotten an all in one
WOApp to run with jlink. That is: D2W, persistent session storage,
h2 embedded database, vert.x webserver, java 25, all embedded in
one app. I plan to turn that into a maven archetype when I get
Wonder8 released onto maven central.
On 3/25/26 6:51 AM, Paul Hoadley wrote:
Hi Ted,
HOWEVER, I have a D2W app that was started with the
Ant paradigm. After learning maven and switching my app
over (it is much cleaner) many of the images from
ERModernDefaultSkin do not display in development.
There is an annoying edge case with Maven frameworks and
resource loading in Eclipse. I've never investigated it too
deeply, as the workaround is simple: in your case, you need
ERModernDefaultSkin.framework as an open project in your
Eclipse workspace, and the Maven version needs to match
exactly to what your app depends on. When there's a version
mismatch, it doesn't seem to be able to load resources out
of the JAR in your ~/.m2/repository.
|