Community
Participate
Working Groups
Build Identifier: Build id: 20100218-1602 I have an eclipse v3.5 installation with an Apache Tomcat v6.0 server installed in it. When an attempt is made to connect to the running server, an "Access to the specified resource () has been forbidden" error results, with no error logged anywhere indicating why. Confirmation that I am connecting to the right server is obtained by stopping the server and verifying that "connection refused" results, it does. At no point does tomcat give any clue as to the name of the URL the application is hosted under. The first step is to determine what the tomcat configuration is. Right click on the Apache Tomcat v6.0.26 server in the Servers view, and select "properties". Under the "General" tab the "Location" field contains the text "[workspace metadata]", which is meaningless in this context. A further meaningless button called "switch location" is offered, with no explanation as to what locations you are switching from or to. An attempt to switch the location causes the application inside tomcat to not-start, complaining that a directory doesn't exist. As a result, it is impossible to work out with any confidence as to what config files are used by tomcat, or what the effective configuration is. Based on this, it is impossible to debug tomcat configuration problems in eclipse v3.5, as it is impossible to find the config files belonging to tomcat. Reproducible: Always Steps to Reproduce: xxx
Ugly ugly hack workaround: - Double click the server in the server view. - click "open launch configuration". - Select "arguments" tab. - Under the VM arguments, look for the following key: -Dcatalina.base="/Users/minfrin/Documents/workspace-3.5/.metadata/.plugins/org.eclipse.wst.server.core/tmp1"
There is multiple problems in here: 1) a problem with no explanation given as to what the switch location button will do, but I think this is documented in the help. 2) How to find the location of the configuration files used by eclipse. I think you were looking for the files that are shown under the server editor. To open the server editor, double click on the server, then search for the configuration path field. That field refers to the folder where the configuration files are stored. Both problems seem to be related to usability and I think the helps covers this areas. Let me know if you didn't find info in the help.
