Hi JB,
Thanks for the suggestion. We will investigate that approach and will
report if we have something useful to report.
Best,
- Daniel
Am 16.03.2022 um 18:44 schrieb Jean-Baptiste Onofré:
Hi Daniel
If it's possible to scan this in Karaf Main, the only way right now is
to hack the main (there's no plugin mechanism in the Main). The other
possible approach (in startup bundle or boot feature) would be too
late as Karaf is already "started".
I think the easiest approach is to do it in bin/karaf.bat. Here you
can check the registry and use the right java home to start karaf.
Thoughts ?
Regards
JB
On Wed, Mar 16, 2022 at 5:30 PM Daniel Krügler
<daniel.krueg...@gmx.de> wrote:
Hi,
I would like to get a hint whether (and possibly how) the following
use-case is implementable using a karaf server:
We have an karaf-based server running and the installation program
also
installs a JRE in a specific directory that should be used to
start the
server. The information where the JRE is located is stored in an
application-specific registry key (OS: Windows).
The machine where the server is running is also used by certain users
which may or may not decide to install a JRE or JDK for other
applications, but we want to be sure that the karaf server is *always*
started with the JRE which is configured by our specific registry key,
regardless of such additional JRE user installations.
Does there exist a way to inform the karaf server on startup via a
dynamical mechanism that would in our case inspect the content of the
above mentioned registry key and transfers this information to
karaf to
start with?
Maybe karaf provides a special built-in mechanism that is specifically
designed for such a dynamical start decision?
Thanks for your help,
- Daniel
