- This topic has 5 replies, 3 voices, and was last updated 21 years, 3 months ago by
.
-
Posts
-
If you go to Window>Preferences>MyEclipse>Application Servers>Tomcat 4>JDK the “Optional Java JVM Arguments” places a limit on the amount of text you can enter into the box. It would be nice if there was no limitation or the limitation was set significantly higher. I am working with a company at the moment that places a significant amount of Arguments into it. I would like to use the TC Start Stop. But, at the moment I cannot.
I am runing on Win2k with Eclipse version 2.1.1
The optional JVM args preference is currently set to a max size of 1000 chars. Before I submit an enhancement request how large is the argument string you need to construct? Also, I’m just curious as what type of commandline entries you’re using.
Michael
MyEclipse SupportThe command line arguments are for logging levels. It doesn’t make much sense to me. But, this is the way the company i am working with is doing it. I questioned them on it and they told me that they liked it. Therefore, I am not going to argue with them. I’ll provide you an example. 😀
-Dcom.thecompany.commons.util.environment\=DEV;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.struts.util.PropertyMessageResources\=info;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.struts.util.RequestUtils\=info;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.struts.util.MessageResourcesFactory\=info;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.struts.action.ActionServlet\=info;-Dcom.thecompany.commons.database.connectionmanager.default-impl\=com.thecompany.commons.database.AS400ConnectionManager;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.commons.digester.Digester\=info;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.commons.digester.Digester.sax\=info;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.commons.beanutils.MethodUtils\=info;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.commons.beanutils.ConvertUtils\=info;-Dcom.thecompany.commons.util.defaultlog.log.org.apache.commons.beanutils.BeanUtils\=info;-Dcom.thecompany.commons.util.defaultlog.log.default\=debug;-Dcom.thecompany.commons.util.defaultlog.showdatetime\=true;-Dorg.apache.commons.logging.Log\=com.thecompany.commons.util.DefaultLog;-Dorg.apache.commons.logging.LogFactory\=org.apache.commons.logging.impl.LogFactoryImpl;
Perhaps a simple properties file is in order at this point? It’d be much easier to manage and you could check it into CVS to do change tracking on it. 🙂
–Scott
MyEclipse SupportThanks for the suggestion. Unfortunately, I do not make that decision. So, will the enhancement be included in the next point release?
I checked our tracking system and it has been picked up to be included in the next service release. We’ll be increasing the buffer to 4K, from the looks of it.
I’d still suggest the property file to whomever makes that decision though. It really is the right thing to do. 🙂
–Scott
MyEclipse Support
