Skip to main content



      Home
Home » Language IDEs » ServerTools (WTP) » SetPropertiesRule error
SetPropertiesRule error [message #210618] Thu, 20 March 2008 08:28 Go to next message
Eclipse UserFriend
Hi,
I have installed the eclipse-jee-ganymede-M5-win32.zip. I created a new
workspace.
In my new workspace I created a dynamic web project named 'Zohar'. In my
project I created a new servlet.
I defined a new tomcat 6 (6.0.16) server.
When I add the new project to the server and run it I get:

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

All output to the console is red (err stream I suppose).
When I try to access my servlet I get a 404.

What's wrong?

Thanks,
Zohar.
Re: SetPropertiesRule error [message #210626 is a reply to message #210618] Thu, 20 March 2008 09:06 Go to previous messageGo to next message
Eclipse UserFriend
zohar wrote:
> Hi,
> I have installed the eclipse-jee-ganymede-M5-win32.zip. I created a new
> workspace.
> In my new workspace I created a dynamic web project named 'Zohar'. In my
> project I created a new servlet.
> I defined a new tomcat 6 (6.0.16) server.
> When I add the new project to the server and run it I get:
>
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
> property 'source' to 'org.eclipse.jst.jee.server:Daphna' did not find a
> matching property.
>
> All output to the console is red (err stream I suppose).
> When I try to access my servlet I get a 404.
>
> What's wrong?
>
> Thanks,
> Zohar.

I can't answer your full question, but the fact that the console window
contains red output from Tomcat does not necessarily indicate error.
When I start Tomcat, it's always red and works fine.

"INFO: Server startup in 815 ms"

If you see the above message at the end of everything else (with a
different value perhaps than 815), then your Tomcat server is almost
certainly up and running.

Look for your HTP 404 error based on a messed up path in the address
line of the browser (i.e.: doesn't match your project paths), a missing
class or JSP file, or an incorrect web.xml.

Wish I could help more, but I struggle against the mighty 404 myself all
too frequently.

Russ Bateman
Re: SetPropertiesRule error [message #210643 is a reply to message #210626] Thu, 20 March 2008 11:24 Go to previous message
Eclipse UserFriend
Windofkeltia wrote:
> zohar wrote:
>> Hi,
>> I have installed the eclipse-jee-ganymede-M5-win32.zip. I created a
>> new workspace.
>> In my new workspace I created a dynamic web project named 'Zohar'. In
>> my project I created a new servlet.
>> I defined a new tomcat 6 (6.0.16) server.
>> When I add the new project to the server and run it I get:
>>
>> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context}
>> Setting property 'source' to 'org.eclipse.jst.jee.server:Daphna' did
>> not find a matching property.
>>
>> All output to the console is red (err stream I suppose).
>> When I try to access my servlet I get a 404.
>>
>> What's wrong?
>>
>> Thanks,
>> Zohar.
>
> I can't answer your full question, but the fact that the console window
> contains red output from Tomcat does not necessarily indicate error.
> When I start Tomcat, it's always red and works fine.
>
> "INFO: Server startup in 815 ms"
>
> If you see the above message at the end of everything else (with a
> different value perhaps than 815), then your Tomcat server is almost
> certainly up and running.
>
> Look for your HTP 404 error based on a messed up path in the address
> line of the browser (i.e.: doesn't match your project paths), a missing
> class or JSP file, or an incorrect web.xml.
>
> Wish I could help more, but I struggle against the mighty 404 myself all
> too frequently.
>
> Russ Bateman

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. As Russ states, the 404 is unrelated to this warning.

Cheers,
Larry
Previous Topic:Hot-edit of JSP files with Tomcat 6.0 - should it require a republish?
Next Topic:Refactoring support for JSDT
Goto Forum:
  


Current Time: Wed Jul 23 14:08:26 EDT 2025

Powered by FUDForum. Page generated in 0.03340 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top