views:

9300

answers:

8

When I start Tomcat (6.0.18) from Eclipse (3.4), I receive this message (first in the log):

WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server: (project name)' did not find a matching property.

Seems this message does not have any severe impact, however, does anyone know how to get rid of it?

A: 

hi there,

can you tell us what plugin you're using to start tomcat from Eclipse ?

anjanb
sure. I'm using Eclipse WTP (http://www.eclipse.org/webtools/)
Das
+3  A: 

From Eclipse Newsgroup:

The warning about the source property is new with Tomcat 6.0.16 and may be ignored. WTP adds a "source" attribute to identify which project in the workspace is associated with the context. The fact that the Context object in Tomcat has no corresponding source property doesn't cause any problems.

I realize that this doesn't answer how to get rid of the warning, but I hope it helps.

Swati
Don't you love it when you hear "it's okay to ignore that warning!" If the warning is worthless, **why do they show it??** As if we don't have enough real warnings or errors to worry about, we have to have our time wasted on rubbish like this. +1 more reason to ditch Tomcat and upgrade to Glassfish.
Crusader
A: 

I had the same problem with Eclipse 3.4(Ganymede) and dynamic web project.
The message didn't influence successfull deploy.But I had to delete row

<wb-resource deploy-path="/WEB-INF/classes" source-path="/src/main/resources"/>

from org.eclipse.wst.common.component file in .settings folder of Eclipse

A: 

I'm also getting the same error when i tried to install FDDPMA. This warning cause me the error 'Feb 18, 2009 3:23:25 AM org.apache.catalina.realm.JAASRealm authenticate SEVERE: Unexpected error java.lang.SecurityException: Unable to locate a login configuration'

As org.apache.catalina.realm.JAASRealm setUseContextClassLoader

Do you know how to get rid of this?

+12  A: 

The solution to this problem is very simple. Double click on your tomcat server. It will open the server configuration. Under server options check ‘Publish module contents to separate XML files’ checkbox. Restart your server. This time your page will come without any issues.

Correct answer, never 'ignore' warnings if at all possible. Ignore enough warnings, some day they'll cause you to miss a REAL problem.
Crusader
A: 

yo no encuentro esa carpeta de configuracion, yo uso el Tomcat V6.0 Server con Eclipse y me sale el mismo error, alguien me podria decir como lo resuelvo?

A: 

I'm finding that Tomcat can't seem to find classes defined in other projects, maybe even in the main project. It's failing on the filter definition which is the first definition in web.xml. If I add the project and its dependencies to the server's launch configuration then I just move on to a new error, all of which seems to point to it not setting up the project properly.

Our setup is quite complex. We have multiple components as projects in Eclipse with separate output projects. We have a separate webapp directory which contains the static HTML and images, as well as our WEB-INF.

Eclipse is "Europa Winter release". Tomcat is 6.0.18. I tried version 2.4 and 2.5 of the "Dynamic Web Module" facet.

Thanks for any help!

  • Richard
+1  A: 

server tab

-->doubleclick servername

-->server options: tick "Publish module contexts to separate XML files"

restart your server


done

kr, zara