[jcorbin4607]

Hello,

I renamed my EJB project from WineEJB to TrackerEJB via the refactor submenu. I would have expected this to update all the necessary files, but one doesn’t seem to be getting updated. It is the .mymetadata file under EJB project.

My application failed to deploy because it couldn’t find my EJB project (TrackerEJB) in the deployment. This is when I started looking at the configuration files that eclipse/myeclipseide generate for projects and noticed that this .mymetadata was still referencing the WineEJB name instead of the one I renamed it to, which was TrackerEJB.

I don’t know if there are others, but this seems like a bug in either Eclipse or MyEclipseIDE.

Thanks,
J.D.

[jcorbin4607]

To fix my problem, I deleted the J2EE Ear project and recreated it, adding my TrackerEJB and TrackerWeb projects.

I then viewed the application.xml source and sure enough, the TrackerEJB project that I added was incorrectly added to the application.xml as WineEJB.jar.

The next step was to delete the EAR project including disk contents, and deleting the .metadata directory underneath the workspace directory. I reran MyEclipseIDE, imported my EJB and WEB projects, then created a new EAR project, adding my existing EJB and WEB projects. This fixed the corruption which existed in a file(s) under the .metadata directory.

J.D.

[support-michael]

Thanks for the feedback. I’m sure we have a test case for this. Regardless I have entered a problem report with your info for further research.

Michael
MyEclipse Support

[jcorbin4607]

Scott,

I still really like MyEclipseIDE and realize it is a work in progress. I wanted to let your team know that they are doing a good job.

One aspect of the tool that needs to be worked on and hammered down is project deployment wizard. I have had tons of problems with this wizard. As with the application.xml editor, this editor doesn’t stay in sync with the state of the deployment to the application server. It doesn’t seem like much time was spent in testing this area of the tool.

Because deployment is such an important part of the development life cycle, I really think the MyEclipseIDE team needs to spend some more time testing this area of the tool. It should work everytime.

I am developing on a Windows XP machine (Pentium 4M 1.5GHZ laptop) and deploying to JBOSS 3.2.3.

A lot of times, I have to exit completely out of MyEclipseIDE for the application deployment wizard to right itself. I assume it cleans up underlying temporary deployment files that the wizard uses to track state.

If you need any more information, please don’t hesitate to ask. I want to help make this tool as good as it can be.

J.D.

[jcorbin4607]

One more thing that may or may not be important…This is really strange so bare with me…

My EJB project has some JUNIT test cases that I was attempting to lookup local interfaces from, which of course, would fail because the JUNIT test cases run in a different JVM (Debug).

I then refactored my code to create the remote interfaces to my bean and changed the test case to lookup the remote interface. It worked perfectly and the issues with the deployment wizard went away. I was able to undeploy, deploy as many times as needed and it didn’t appear to get out of sync.

Now, I have no idea why changing my test client to lookup remote vs. local interfaces would have any affect on the deployment of the application, but it appears to have done so.

I am not sure what was going on here. 🙂

J.D.

[support-michael]

J.D.,

There is a case in the 2.7RC1 and earlier where the metadata gets out of sync as you have identified. The 2.7RC2 release planned for tomorrow resolves this problem. Thanks for you assistance in identifying this problem.

Michael
MyEclipse Support

[Riyad Kalla]

J.D./Michael,
Is this issue resolved with the 2.7 GA release?

[Scott Anderson]

Yes it is. Marking as closed.

[Riyad Kalla]

Fixed in 3.8Beta2.

[Author]

Posts