|Default VM settings in the .launch file for Tomcat server. [message #233789]
||Fri, 17 July 2009 11:31
Originally posted by: somebody.nowhere.com|
In Eclipse, Server view, I created a new Server and following the prompts
created a new Tomcat 5.5 server.
I would like to know how is the related .LAUNCH file created in
By creation, I mean it has some deafult VM settings;
where do they come from?
can I edit or set any preferance whereby the default VM settings; are
appended with a few of my own (sparing me the effort of editing the launch
configuration, every time I creat a server instance)
PS: For some reason; I need to 're-cycle' (delete & create-new) the server
instance a lot of times.
|Re: Default VM settings in the .launch file for Tomcat server. [message #233828 is a reply to message #233813]
||Fri, 17 July 2009 19:56
| Larry Isaacs
Registered: July 2009
Jeevan Sunkersett wrote:|
> Thx Larry ,
> To be explicit, I want the VM arguments in the Launch file to include....
> -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=104 4
> (for remote debuging)
> I can easily do that by editing the launch configuration via the wizard
> provided; but I was looking for a way, whereby those -X vm paramaters
> are applied to the server launch configuration everytime it is created
> by default.
> But I find myself, recycling the server instance very often and its a
> pain to edit the configuration to add the custom -X vm parameters every
> time; and so want it added by default.
> As it is done programatically by the WTP plugin, please can you point me
> to the exact plugin/ source; (I am assuming the parameters are picked
> from a resources bundle and not hard coded....that way maybe I can edit
> the resources bundle and rebuild the plugin and use).
What needs to be done to "fix up" a default launch configuration is
either dynamic or fixed, so there isn't much to gained by a resource
bundle lookup. You can start with the
class found in the tomcat.core plug-in. That is where the Tomcat
plug-in applies it's required changes to the launch configuration.
You can also look at
org.eclipse.wst.server.core.Server.getLaunchConfiguration() to see where
the launch configuration "originates". A quick look didn't seem to show
much initialization prior to being handed to the
Powered by FUDForum
. Page generated in 0.02864 seconds