From the linked issue I understand I need `sudo asadmin` for stop/start-domain (would need sudo for jsp in the kill9 script too), having the order of commands right too, I seem to get rid of the mess and the web-ui now reacts as one should expect: requiring a fresh login after following the un/re-deploy procedure above.
However I still don't see the fine logging I added to the refactored classes, despite set-log-leves in asadmin.
> I'm not sure why you're trying to create a dvinstall.zip file.
At
DANS we grew happy by using vagrant to develop our major systems.
- Each developer has an identical environment to work with and we don't
need answers like 'whatever floats your boat' as everyone
has the same environment.
- Developers also have a separate environment for each system contributing to.
Just for debugging we launch a
client or service from our IDE using resources
from the vagrant.
Rather than an extra step to replace a war, we
might feel better with creating vagrant instances with a local dvinstall. It would make us less dependent on having our enhancements accepted in your own time line and we can also test the full round-trip of our changes.