|
|
|
Re: launch configurations in java ee project can't be saved in the project [message #1008272 is a reply to message #1008117] |
Mon, 11 February 2013 09:41   |
Eclipse User |
|
|
|
On 2/9/2013 4:58 AM, Palmer Eldritch wrote:
> Larry Isaacs wrote on Fri, 08 February 2013 15:49
>> Server launches are "different". The launch is created/regenerated
>> based on your server configuration each time you start the server.
>> Some pieces of an existing launch are preserved, such as VM Arguments,
>> but otherwise the launch gets replaced each time the server is
>> started. As a result, moving the launch file to an alternate location
>> isn't supported. It always ends up under
>> "org.eclipse.debug.core\.launches".
>>
>> Cheers,
>> Larry
> A ha - thank you very much - could be that some of it is exported though
> - qualifies for an enhancement imo
>
> Could you please point the relevant part in the docs to me ?
>
> Thanks :)
>
I can point you to source code for the Tomcat support, but otherwise,
I'm not aware that it appears in documentation anywhere.
Cheers,
Larry
|
|
|
|
Re: launch configurations in java ee project can't be saved in the project [message #1009687 is a reply to message #1009094] |
Fri, 15 February 2013 09:23   |
Eclipse User |
|
|
|
On 2/14/2013 7:26 AM, Palmer Eldritch wrote:
> Larry Isaacs wrote on Mon, 11 February 2013 09:41
>> I can point you to source code for the Tomcat support, but otherwise,
>> I'm not aware that it appears in documentation anywhere.
>>
>> Cheers,
>> Larry
> Thanks that'd be nice - I meant the Eclipse docs though - this info
> should be there
>
In the class
org.eclipse.jst.server.tomcat.core.internal.TomcatServerBehaviour, there
is a method called setupLaunchConfiguration(). This method is
responsible for ensuring that the launch configuration has Tomcat
settings accurate per server configuration persisted outside of what is
persisted for the launch configuration. For example, it overwrites
certain VM Argument settings, such as "catalina.home", to ensure it is
up to date. It also tries to preserve other VM Arguments from the
launch configuration which the user might set. This is one example of
how a server launch is more than just the settings stored in the
".launch" file. There are probably others.
You can view the TomcatServerBehaviour source in Git[1], or pull it into
your workspace using File->Import.
Cheers,
Larry
[1]
http://git.eclipse.org/c/servertools/webtools.servertools.git/tree/plugins/org.eclipse.jst.server.tomcat.core/tomcatcore/org/eclipse/jst/server/tomcat/core/internal/TomcatServerBehaviour.java
|
|
|
|
Powered by
FUDForum. Page generated in 0.11888 seconds