[
https://jira.jboss.org/jira/browse/JBAS-5363?page=com.atlassian.jira.plug...
]
Eric Soyke commented on JBAS-5363:
----------------------------------
Yes, it is messy to have to embed stuff in the run.bat. You can mimic the functionality of
the run.conf by creating another bat file to load your properties and then just calling it
from within run.bat. For instance...
somewhere in run.bat:
CALL run.conf.bat
in a new file called run.conf.bat:
SET JAVA_OPTS=-Xms128m -Xmx512m
SET JAVA_OPTS=%JAVA_OPTS% -DKEY1=VALUE1
SET JAVA_OPTS=%JAVA_OPTS% -DKEY2=VALUE2
etc...
It's not totally portable as you have to duplicate the arguments over in run.conf if
you are later deploying in Unix (and change the syntax accordingly), but it's a lot
cleaner than trying to remember everything to cut and paste from run.bat to run.sh.
run.conf ignored by run.bat under Windows
-----------------------------------------
Key: JBAS-5363
URL:
https://jira.jboss.org/jira/browse/JBAS-5363
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-4.2.2.GA
Environment: WindowsXP SP2, x86
Reporter: Gregor Rosenauer
Priority: Minor
JBoss does not parse run.conf under Windows, so configuration options have to be added to
run.bat directly, which is not nice.
Under AIX, JBoss (same version) correclty parses run.conf (e.g. JAVA_OPTS).
JBoss should behave the same in both environments, so it becomes "configure once,
run anywhere" ,=)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira