[Rob]

I have the following:
– Enterprise Application Project: “MyApp”
– EJB Project: “MyAppEJB”
– Web Project: “MyAppWEB”

I can deploy everything to JBoss 3.2.3, and all test cases work without issue.

My Problem:
In MyEclipse 3.9.210, I can individually deploy the Web Project, EJB Project or
EAR project, however, if the WEB project is deployed, MyEclipse will NOT allow me
to deploy the EAR project. Why!? I have removed all references to the WEB
project from the EAR project. The deploy tool complains with the error:

“Context-root ‘/MyAppWEB’ already in use by project MyAppWEB deployed on server JBoss 3.”

Is there an artifact file somewhere that needs to be deleted for the MyEclipse
to allow the deploy?

I want to be able to deploy my EAR and WAR separately. I should not need to
package the WAR in the EAR.

Is there a work-around for this for MyEclipse?

Regards,

Rob.

[Rob]

hmmm, it seems that there are a few bugs here.

1. When creating the MyAppWEB, I specified EJB 1.3, but the meta-file says 1.4.

2. When I removed the MyAppWEB reference from the EAR project, (by right-
clicking on the project and selecting –> Properties –> Project References), the
association was NOT REMOVED from the .mymetadata file.

…The price you pay for a Milestone Release:

(EnterpriseWorkbenchInstaller_4.0M2_E3.1)

[Scott Anderson]

Rob,

Sorry for the confusion and the trouble you’ve experienced on this. Yes, there were a couple of bugs in M2 related to the module relationship / metadata saving for EAR projects. The good news is we’ve already addressed them for M3, so a fix should be available shortly.

[Author]

Posts