Strange behavior for sysdeo on fedora core 5

[Paul Fenerty]

Hello,

Starting with:

1) Linux 2.6.17-1.2174_FC5 (Fedora Core 5)
2) tomcat5-5.5.15-1jpp_6fc
3) Eclipse SDK Version: 3.1.2
Build id: M20060118-1600 (Fedora Core release 5 (Bordeaux))

all of which came with the FC5 distribution, I added:

4) jdk1.5.0_08

and most recently:

5) SYSDEO Tomcat Plugin 3.1.0

Inbetween (4) & (5) I ran an existing webapp of mine, outside of eclipse, and so much of the infrastructure seemingly works OK.

But then:

New Project -> Tomcat Project

failed with:

Project hohos is missing required library:
'/usr/share/tomcat5/common/lib/jasper-runtime.jar'
Project hohos is missing required library:
'/usr/share/tomcat5/common/lib/jsp-api.jar'
Project hohos is missing required library:
'/usr/share/tomcat5/common/lib/servlet-api.jar'

all of which were absent from the FC5 distribution. So I went to find them, and downloaded copies from apache-tomcat-5.5.17, which was the closest to my tomcat5-5.5.15-1jpp_6fc I could find at the jakarta site.

Now

New Project -> Tomcat Project

finished, and Package Explorer view showed the expected file structure. But when I moved some files into WEB-INF/classes, the 'classes' directory disappeared from Package Explorer view. I can open a file from that directory, in eclipse, but the Package Explorer GUI shows only 'lib' as a subdirectory of WEB-INF. I can move files and subdirectories into WEB-INF, and Package Explorer shows them. If I try to create the 'classes' subdirectory in eclipse, it won't, because there already is one.

Subsequently, I have created new Tomcat Projects, and none of them now display the 'classes' subdirectory of WEB/INF, even at project creation. I get no error messages when I create these projects, and the 'classes' subdirectory is always really there in the filesystem.

Anybody ever seen this before? I've read about some strange problems regarding tomcat on FC5, and I have to wonder why the above mentioned jar files were left out.

Is it likely that Sysdeo 3.1.0 will work here?

Thanks (!)
Paul

[Paul Fenerty]

Just to close the loop on this, it all works great, except that the WEB-INF/classes directory is never visible in the Package Explorer, no matter what, while anything else I stick there is always visible, and far be it from me to complain about any such minor idiosyncracies in an otherwise marvelous tool.

In fact, had that directory not started out perfectly visible, right after first bringing it all up, along with the rest of the typical webapp filesystem structure, and so generating the sort of warm happy glow that comes along when something works just as expected, first time out, then I never would have spent all that time trying to get it back.

[Jeanne Boyarsky]

Paul,
Thanks for posting the solution so that others who see this thread in the future can benefit.