[wildfly-dev] Start Up Scripts

[James R. Perkins]

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 at 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 at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20140723/7a5c2f7d/attachment-0001.html