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?
This question is related to
java
eclipse
tomcat
eclipse-3.4
I copied the dynamic Webproject before the issue came up. So, changing the org.eclipse.wst.common.component file in the .settings directory solved the issue for me. The other solutions did not work.
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.
The separate XML solution never worked for me and other's recently ...
I usually follow this process and something helps:
I am posting my answer because I suspect there might be someone out there for whom the above solutions might not have worked.
So, you are getting a warning,
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server: (project name)' did not find a matching property.
Rather than disabling this warning by checking that option in Server configuration (I did try that) I would suggest you do this:
Now if you successfully found that there is a bug in your app, the probable place would be look for a web.xml file which the container uses for loading the app. In my case I had misspelled a name in servlet mapping which made me debug meaninglessly for 3 hours. Your problem might be someplace else.
And another thing, if you have many apps synchronized with the server,there is a possibility some other app's context might be the source of problem. Try debugging one by one.
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!
Make sure you have correct jsp file name in web.xml file. By replacing default .jsp filename in web.xml with my current filename solved the problem
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
Servers tab
--> doubleclick servername
--> Server Options: tick "Publish module contexts to separate XML files"
restart your server
Delete the server instance from Eclipse and create a new one.
I am using Eclipse. I have resolved this problem by the following:
You will not get any this kind of error.
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
I respect all the solutions given here.
But what I came to know after reading all these, we haven't observed that on which folder the struts.xml file or any configuration file which is necessary for the web application.
My SOULUTION IS:
Hope the problem solved.
Source: Stackoverflow.com