It’s possible but why bother? The server/client switches were there for the
old days when desktop and laptop machines were less powerful. If you don’t
specify it, the JVM takes a look at the hardware when it starts up and picks a
default based on how much memory and how many cores you have.
-1
A few reasons;
- ProxyAccessor exists primarily to go along with the activation system, which
is slated to be removed.
- ServiceProxyAccessor goes with the ‘start’ package, that is an implementation
detail that not all containers use
- Whether a service is implemented by a reflective
I couldn’t find a way to detect if the “-server” switch would be supported
without actually running the jvm, and then searching the value of a system
property (like: System.getProperty("java.vm.name")) for the text: “server”.
Seems nasty.
FWIW, the following docs suggest the “-server” mode is
> On Jan 5, 2016, at 10:51 PM, Peter wrote:
>
>
>
> ProxyPreparer in its current form is broken.
>
> Proxy preparation assumed that both the java sandbox and serialization are
> secure, code is downloaded, static class initialisers and readObject methods
> are executed
Thanks Dan, consider it removed.
Sent from my Samsung device.
Include original message
Original message
From: Dan Rollo
Sent: 06/01/2016 05:34:26 am
To: Cc: dev@river.apache.org
Subject: Re: Test Failures on ARM, maybe I'm missing setup?
I couldn’t find a way
The iiop tests passed, so I assume that means the stubs compiled.
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_BehaviorTest.td
Passed
com_sun_jini_test_spec_iiop_iiopexporter_Export_BehaviorTest1.td
Passed
Just curious, were you able to compile iiop stubs, or did you find that this
wasn't supported by the arm jdk
Regards,
Peter.
Sent from my Samsung device.
Include original message
Original message
From: Greg Trasuk
Sent: 06/01/2016 02:37:39 am
To: