[Jeff Orford]

I’m having a problem deploying a project (struts-based) to Tomcat 6 within MyEclipse. It used to work using the same server installation within Ganymede. I have tried a few things (deleting and importing the project back into MyEclipse), but no luck so far. Is there something that I should do?

Thanks.

[Loyal Water]

Can you go to MyEclipse > Installation Summary > Installaton Details and paste the information here for me.

What is the error that you get when the deployment fails?

[Jeff Orford]

There isn’t really an error. Here’s the whole story …
1) I deleted the project (including from the filesystem) using ME.
2) I import the same project in it’s original form. At this point the project would not be recognized in the “Project” drop down of the deployment manager (2nd page of deployment manager).
3) To correct the problem mentioned in step 2 I r-click the project then MyEclipse->Add Web Project capabilities and select the “WebContent” folder as the “web root directory” and click “finish”. Unfortunately this doesn’t finish per se, but gets far enough that the project shows up in the “Project” drop down of the deployment manager (solving the issue from step 2)
4) When I cancel out of the “Add Web Project capabilities” dialog, I do the deployment using the “Deploy J2EE projects to server” button and it <b>says</b> the deployment was successful.
5) When I attempt to look at the project in a browser I get a 404. Note: I have tried accessing the project thru Tomcat Manager, but get the same result. Also, in Tomcat Manager, the line for my project looks slightly different than the other webapps (manager, examples, etc.) in that these other webapps have Undeploy as a link to execute the Undeploy command, but my webapp does not AND there is no “expire” button. This is why I surmise that the Deployment did not go correctly.

Thank you for any help.

Here are the installation details:
<details>
*** Date:
Thursday, October 2, 2008 1:34:53 PM MDT

** System properties:
OS=WindowsXP
OS version=5.1
Java version=1.6.0_06

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 6.5.1 GA
Build id: 6.5.1-GA-20080715

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 6.5.1 GA
Build id: 6.5.1-GA-20080715

Eclipse Project SDK

Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
Build id: M20080221-1800

Eclipse Platform

Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
Build id: M20080221-1800

Eclipse RCP

Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
Build id: M20080221-1800

Eclipse Plug-in Development Environment

Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
Build id: M20080221-1800

Eclipse Java Development Tools

Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
Build id: M20080221-1800

Eclipse Graphical Editing Framework

Version: 3.3.2.v20080129
Build id: 20080221-1602

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Orf\Applications\MyEclipse\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\Orf\Applications\MyEclipse\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
-startup
C:\Orf\Applications\MyEclipse\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata
11fc_4c
-clean
-vm
C:\Orf\Applications\Java\bin\javaw.exe
</details>

[Jeff Orford]

I noticed one additional thing, from my Tomcat startup log:
Oct 2, 2008 4:19:45 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property ‘source’ to ‘com.ibm.wtp.web.server:ShopperWeb’ did not find a matching property.

Thanks again.

[Jeff Orford]

So in trying to start from scratch here I created a Web app from scratch and Tomcat complained about a missing .deployables directory. Should myEclipse have created a .deployables directory? Should I?

[Loyal Water]

orphord,
Sounds like a problem related to the project directory structure. I would suggest you create a new MyEclipse Web Project and transfer you code to this project. Now does the deployment work?

[Jeff Orford]

Yes. I worked hard to work around it and found a number of things that were causing the issue. Some of which may have been identifiable by myEclipse during the “import project” process. For example, maybe creating a basic context.xml file in the META-INF/, though that may be a tomcat specific thing.

Thank you for your help.

[Loyal Water]

Your welcome.

[Author]

Posts