[Paul Webber]

Using JBoss 4.0.3 SP1 and a web app from an SCM (subversion). That is it works on someone else’s machine but not mine. Installed MyEclipse; JBoss 4.0.3SP1, Checked out the project, Configured JBoss in the MyEclipse Preferences, Configured a Project deployment. It deployed but the a directory name did not have the .war extension (so JBoss ignored it). Packaged Archive worked fine.

The general question is what configuration could I have missed to prevent the deploy sub directory from having the .war extension.

Thanks,
Paul

*** Date: Fri Apr 07 15:32:56 PDT 2006

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

*** MyEclipse details:
MyEclipse Enterprise Workbench

Version: 4.1.1 GA
Build id: 20060309-4.1.1-GA

*** Eclipse details:
Eclipse SDK

Version: 3.1.2
Build id: M20060118-1600

Eclipse Platform

Version: 3.1.2
Build id: M20060118-1600

Eclipse RCP

Version: 3.1.2
Build id: M20060118-1600

Eclipse Java Development Tools

Version: 3.1.2
Build id: M20060118-1600

Eclipse Plug-in Development Environment

Version: 3.1.2
Build id: M20060118-1600

Eclipse Project SDK

Version: 3.1.2
Build id: M20060118-1600

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-launcher
C:\Java\eclipse312\eclipse.exe
-name
Eclipse
-showsplash
600
-exitdata
1654_68
-vm
C:\Java\jdk1.5.0_06\bin\javaw.exe

[Riyad Kalla]

Does the project have a period in the name? This is actually a feature that is causing you the problem that we should remove in MyEclipse 5.0 and improve it’s implementation to not be so secrative.

[Paul Webber]

No period in the project name. The project came as a new checkout from subversion. Is it suppose to have a period?

[Riyad Kalla]

Paul,
No it doesn’t need a period, it’s actually better it doesn’t.

If you create the deployment using a packaged deployment I”m assuming it works right?

[Paul Webber]

Nope – that’s the problem as stated initially; disregarding the period as I don’t have that. The Project name is ido, here are the particulars:
<Info>
Path: /ido
Type: Project
Location: C:\Java\workspaceIDO\ido
<MyEclipse-Web>
Web-root folder: war
Web Context-root /

[Riyad Kalla]

I’m sorry, I missed that “packaged works fine”. If you don’t deploy to root, for example change web context-root to something like /test, does it work?

[Paul Webber]

Interesting – That worked. I put in /ido and the ido.war folder was created. It failed to run the first time but after removing, stopping JBoss and redploy and starting JBoss all seemed to work. Now I would like to understand the “Notice” in the Project Properties and why did this work?

Here is the Notice:
Context-root changes only apply to exploded and packaged WAR deployments of this project.

To update the context-root when this project is deployed as a module of an enterprise project
select the enterprise project. From the context menu (i.e., right-click) choose
MyEclipse > Add/Remove Module dialog. From this dialog remove the web-project from
the enterprise project. Then re-add the web-project to the enterprise project while
specifying the new context-root.

First there is no context menu “MyEclipse > Add/Remove Module” dialog. There is a menu item on the menu bar MyEclipse -> Remove WebProject Capabilities. When I select this I get a context menu “MyEclipse -> Add WebProject Capabilities” which brings up a nice dialog. This now has the /ido as the context which I put back to / The Project properties still had /ido as the context.

I then redeployed and all still worked! Very Interesting….

[Riyad Kalla]

The notification pertains to Enterprise Projects, not Web Projects. Also the reason you are seeing “Add Web Capabilities” is because the particular project you are clicking that on is not a Web Project, most likely just a Java Project, so MyEclipse allows you to enter some metadata and convert it into a Web Project if you wanted to.

Everything is working now?

[Paul Webber]

Yes, all is working except for my understanding (but only time will fix that). Yes, the project is a Java project, plus some natures when it came out of subversion; as the .project xml file was in subversion also. Below are the current natures, which happen to be the same as the ones checked into subversion. Just to recap the ido project was checked out into a clean image using subversion and the Eclipse “Check Out As” wizard. Then modification were made to the properties to get the exploded deployment to work. The project properties for the MyEclipse-Web context came out as / but adding an exploded deployment was non-operational. Start configuring the properties to get everything to work led to the above situation. Thanks for your help.

<natures>
<nature>com.genuitec.eclipse.ast.deploy.core.deploymentnature</nature>
<nature>com.genuitec.eclipse.j2eedt.core.webnature</nature>
<nature>org.springframework.ide.eclipse.core.springnature</nature>
<nature>com.genuitec.eclipse.hibernate.hibernatenature</nature>
<nature>org.eclipse.jdt.core.javanature</nature>
</natures>

[Author]

Posts