[Chris Kovacs]

I have a project that was originally just a regular Eclipse java application project. Now I’m in the process of changing it over to an EJB project. I did this by checking the project out from CVS with the “Checkout as…” and using the wizard to check it out as an EJB project.

What happens next is I can deploy the project to JBoss once or twice using the “Manage Deployments” dialog, but after some events like restarting JBoss, restarting Eclipse or opening/closing the project, it does not show up in the “Manage Deployments” dialog as a deployable project.

What also happens is that when I try to add it as a module to an Enterprise Application project, it is not listed as an “Application Module” in the “New Application Module” dialog.

When I look at the project’s .mymetadata file, I see that it’s type is indeed “EJB”.

The only workaround right now is to delete the project and re-check it out from CVS and then immediately deploy it. This is happening on more than one workstation and is becoming an untenable situation.

Thanks for your help.

[Chris Kovacs]

MyEclipse Version: 6.0.1.zmyeclipse601200710
Build Id: 6.0.1-GA-200710

[Incognito.24]

Bump.

Somebody from MyEclipse Support?

We’re paying customers with a 24 user Pro license.

[Riyad Kalla]

Chris,
Sorry for missing this yesterday when you posted.

If you switch to your navigator view and open the .mymetadata file, what does it look like? Here’s an example of one that I just created for a J2EE 1.4 EJB module:

<?xml version="1.0" encoding="UTF-8"?>
<project-module
  type="EJB"
  name="TestEJB"
  id="myeclipse.1213824821499"
  j2ee-spec="1.4"
  archive="TestEJB.jar" />

I’m also curious *if* your project looks good initially, if at some point when it craps out, if you check the .mymetadata file if it either looks corrupt *or* is missing.

if it’s either of those two, I have a sneaking suspicion that you might be doing an “Override and Update” Team operation that is syncing the repository against your local disk and killing the extra metadata file that makes it an EJB project.

[Incognito.24]

Thanks for the response. Am looking into this now.

[Chris Kovacs]

I figured it out. You were close with the .metadata, but it looks like the problem was with the .project file. I created a new EJB project and compared .project files. I basically replaced everything in the existing .project file with what was in the new one except for the project name. Seems to work now, thanks.

[Riyad Kalla]

I’m glad it’s working now.

[Author]

Posts