[JeffreyGetzin]

I’m using MyEclipse 8.5, deploying to Glassfish v3. I have two projects: an enterprise application (DCMHub) and a web module (DCMWeb).

I deploy to a local server using autodeploy.

When I deploy as “Exploded Archive (development mode)”, it works perfectly.

However, if I try to deploy as a “Packaged Archive (production mode)”, it fails. I get the following error message:

“‘Add Deployment’ has encountered a problem. An internal error has occurred during: ‘Add Deployment’.”

Clicking on “<< Details” reveals: “An internal error occurred during: ‘Add Deployment’. java.lang.UnsupportedOperationException”

Looking at the error in the Event Details reveals the following:

Severity: Error
Message: An internal error occurred during: “Add Deployment”.
Exception Stack Trace:

java.lang.UnsupportedOperationException
at com.genuitec.eclipse.j2eedt.core.internal.project.WTPEarProject.getWorkareaDirectoryPath(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.getBuildFolder(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.initBuildArea(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.EarPackager.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.PackageUtils.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.deployAsPackageArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.jobs.A.�(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.jobs.A.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

Session Data:

java.lang.UnsupportedOperationException
at com.genuitec.eclipse.j2eedt.core.internal.project.WTPEarProject.getWorkareaDirectoryPath(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.getBuildFolder(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.initBuildArea(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.EarPackager.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.DefaultPackagerStrategy.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.packaging.PackageUtils.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.exportEARProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.deployAsPackageArchive(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.jobs.A.�(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.jobs.A.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

After getting this error, MyEclipse thinks it has successfully deployed the project and I can not attempt to redeploy it, but it also doesn’t show up in the deployed projects list, so I can not attempt to undeploy it, either. Restarting MyEclipse clears this up, and the project shows up as undeployed and I can now deploy it as an exploded archive if I want.

Thanks,
Jeff

[support-shalini]

Jeff,
I shall escalate this issue to the dev team member. They will get back to you on this.

[Fred]

Can I throw a “Me Too” in there? I am converting a weblogic workbench 10.3 ear project to myeclipse and trying to use its weblogic deployer. I am not having much luck, most of the time it is exactly like the orig poster states.

In addition the same exception showed up when I checked ‘manually update application.xml’ and then changed it to ‘auto update application.xml’

Hope that helps…

-Fred

[JeffreyGetzin]

Interestingly enough, we too are migrating from WebLogic. I wonder if there’s some stuff left laying about from WebLogic that clashes with the Glassfish components.

By the way, I eventually got this to work, but it was a pain.

What I did was create brand new projects in MyEclipse for Enterprise and Web. I then compared the “pristine” .profile files to the .project files that I was having trouble with. One by one, I tried making the “broken” ones more like the “pristine” ones until I had a set that would build and deploy as an EAR file.

Jeff

[Brian Fernandes]

Seems like there is a bug in our import process which does not correctly convert EAR projects to MyEclipse EAR projects. I’m afraid the only way around for now (as Jeffrey discovered) is to create a new MyEclipse EAR project and copy your project contents into that – or copy the metadata – (the .project and .mymetadata files) after suitably modifying for your project name and directory structure, into your project.

We are filing this as a bug for further investigation, sorry for the inconvenience caused.

[JeffreyGetzin]

I can confirm that this workaround has been acceptable for me. My deployments have been going smoothly since I changed upon it.

[Author]

Posts