11:02 p.m.
While taking a look at a change to the start up scripts I'm reminded on
what a PITA it is to get consistent behavior across platforms. There are
4 scripts, not including daemon style scripts, to launch WildFly. In
addition to the 4 scripts there are 4 I guess extension scripts. Any
change needed is likely needed in 4 of the files.
I've created an API to launch WildFly [1]. I'm proposing we could use
the API to launch WildFly. We could nix the *.conf and *.conf.bat files
and go to two properties files; a standalone.properties and a
domain.properties. The normal start up scripts would remain, but be
reduced to only setup essential environment variables and invoke a main
class in the launcher API[2]. Note this is by no means complete, just an
example of how it could be done.
If has any opinions on this let me know. It would allow making changes a
lot easier.
[1]: https://github.com/wildfly/wildfly-core/pull/28
[2]: https://gist.github.com/jamezp/2033be603da4737ac571
--
James R. Perkins
JBoss by Red Hat
7:50 a.m.
What would that mean in practice?
Extra jvm launcher process that will start wildfly.
or will this be in run in same process?
On Wed, Jul 23, 2014 at 5:02 AM, James R. Perkins <jperkins(a)redhat.com>
wrote:
While taking a look at a change to the start up scripts I'm
reminded on
what a PITA it is to get consistent behavior across platforms. There are
4 scripts, not including daemon style scripts, to launch WildFly. In
addition to the 4 scripts there are 4 I guess extension scripts. Any
change needed is likely needed in 4 of the files.
I've created an API to launch WildFly [1]. I'm proposing we could use
the API to launch WildFly. We could nix the *.conf and *.conf.bat files
and go to two properties files; a standalone.properties and a
domain.properties. The normal start up scripts would remain, but be
reduced to only setup essential environment variables and invoke a main
class in the launcher API[2]. Note this is by no means complete, just an
example of how it could be done.
If has any opinions on this let me know. It would allow making changes a
lot easier.
[1]: https://github.com/wildfly/wildfly-core/pull/28
[2]: https://gist.github.com/jamezp/2033be603da4737ac571
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
8:10 a.m.
I like the idea in general, as there are currently too many knobs to operate.
I think though that users and tools (like RHQ/JON) have already added
a lot of functionality to twiddle those .conf and what not files.
So at least make sure it gets right the first time and does not need too many iterations
:)
Heiko
10:16 a.m.
If we were to do it this way it would be another process. I also experimented with just
echoing the command back and running it that way. The issue there is a JVM is started to
get the command. There could be a better way too. If anyone has suggestions, I'm open
to them. --
James R. Perkins
JBoss by Red Hat On Jul 23, 2014 4:50 AM, Tomaž Cerar <tomaz.cerar(a)gmail.com>
wrote:
What would that mean in practice?
Extra jvm launcher process that will start wildfly.
or will this be in run in same process?
On Wed, Jul 23, 2014 at 5:02 AM, James R. Perkins <jperkins(a)redhat.com>
wrote:
While taking a look at a change to the start up scripts I'm
reminded on
what a PITA it is to get consistent behavior across platforms. There are
4 scripts, not including daemon style scripts, to launch WildFly. In
addition to the 4 scripts there are 4 I guess extension scripts. Any
change needed is likely needed in 4 of the files.
I've created an API to launch WildFly [1]. I'm proposing we could use
the API to launch WildFly. We could nix the *.conf and *.conf.bat files
and go to two properties files; a standalone.properties and a
domain.properties. The normal start up scripts would remain, but be
reduced to only setup essential environment variables and invoke a main
class in the launcher API[2]. Note this is by no means complete, just an
example of how it could be done.
If has any opinions on this let me know. It would allow making changes a
lot easier.
[1]: https://github.com/wildfly/wildfly-core/pull/28
[2]: https://gist.github.com/jamezp/2033be603da4737ac571
--
James R. Perkins
JBoss by Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
3564
days inactive
3564
days old
3 comments
3 participants
participants (3)
-
Heiko W.Rupp -
James R. Perkins -
Tomaž Cerar