I don't know if I should post this in a Tomcat forum, or in an Eclipse forum, so I'll try it here:
I'm using Eclipse 3.4 and Tomcat 6.0.18 for web app development and local tests. In the olden days, I always used the Sysdeo Tomcat plugin to start, stop and restart Tomcat from inside Eclipse, that was very convenient and worked fine.
Now I've been told that I won't need the Sysdeo plugin any more, Tomcat can be added as a server in Eclipse and started from there - just as BEA WebLogic or Glassfish can be started by adding them as a "target server".
But, trying this, I failed: Eclipse's console says that everything has started all right and the server is started, but the server can't be reached over
nor any other port that may be mentioned.
So I reverted to using the Sysdeo Tomcat plugin and I could start Tomcat from there, and showed me the well known Tomcat entry page.
So what did I miss out on adding Tomcat as a "Target server" to Eclipse ? Comparing the console output of the two variants showed, that the "Eclipse only" variant failed to start the ContextListener as well as the SessionListener:
This was the version that worked (using the Sysdeo plugin):
And that's the version that did not work (starting the server instance from Eclipse itself):
The two bold lines are the ones where the two variants differ. So, what am I missing in the "Eclipse-only" solution ?
A helpful hint is highly appreciated