[starfight]

Hi Folks,

I have a EAR project with a Web, an EJB 3.0 and an EJB 2.1 module. Target server is the Websphere 6.1 with EJB 3.0 featurepack. The whole project is build by Maven. I just recently added the EJB 2.1 project, before that it was no problem to deploy the EAR within MyEclipse to the connected WAS 6.1. But since I added the EJB 2.1 project this isn’t possible anymore because everytime I run the “Run EJB Deploy”-Command from the MyEclipse context menu to create the deployment code it fails with the below attached exception. Looks like a classpath problem to me…???

The exported EAR file from the modules deploys perfect through the admin interface so I guess the project is valid…

!ENTRY com.genuitec.eclipse.blue.ejbdeploy 4 0 2011-08-17 07:16:13.279
!MESSAGE EJB deploy failed
!SUBENTRY 1 com.genuitec.eclipse.blue.ejbdeploy 4 0 2011-08-17 07:16:13.279
!MESSAGE Error while processing project TESPKostenstellenStammdatenEJB2-V1: org/eclipse/jst/j2ee/internal/common/classpath/J2EEComponentClasspathContainerUtils
!STACK 0
java.lang.RuntimeException: org/eclipse/jst/j2ee/internal/common/classpath/J2EEComponentClasspathContainerUtils
    at com.genuitec.eclipse.blue.ejbdeploy.was61.EJBDeployService.processEJBProject(EJBDeployService.java:315)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.genuitec.eclipse.blue.ejbdeploy.service.ProxyEJBDeployService.processEJBProject(ProxyEJBDeployService.java:48)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.genuitec.eclipse.blue.ejbdeploy.service.ProxyEJBDeployService.processEJBProject(ProxyEJBDeployService.java:46)
    at com.genuitec.eclipse.blue.ejbdeploy.EJBDeployJob.processProject(EJBDeployJob.java:499)
    at com.genuitec.eclipse.blue.ejbdeploy.EJBDeployJob.run(EJBDeployJob.java:401)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.NoClassDefFoundError: org/eclipse/jst/j2ee/internal/common/classpath/J2EEComponentClasspathContainerUtils
    at org.eclipse.jst.j2ee.ejb.project.facet.EjbFacetInstallDelegate.execute(EjbFacetInstallDelegate.java:124)
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1197)
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:349)
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:264)
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:249)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:259)
    at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:216)
    at com.genuitec.eclipse.blue.ejbdeploy.was61.EJBDeployService$1.run(EJBDeployService.java:192)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
Caused by: java.lang.ClassNotFoundException: org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainerUtils
    at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:409)
    at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:354)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
    ... 10 more

Thx in advance for any hints,
Thomas

[support-tony]

Thomas,

Sorry that you are seeing this problem. Our developers are looking into this problem.

Are you using the in-workspace deployment mode? This is a new mode with 9.1 and can be found by editing the profile in the Websphere server configuration – go to MyEclipse->Preferences then select MyEclipse->Servers->Websphere Blue Connectors->Websphere 6.1, then select the profile and click Edit; the new mode is at the bottom of the dialog.

If you’re not using the in-workspace deployment mode, you don’t need to run the EJB Deploy tool and should be able to deploy directly; EJBDeploy will be run by WAS.

[starfight]

Tony,

thank you for your reply and for looking into this.

I’m using the “Classic Mode” for deployment mode and as deployment type “Exploded archive” on the actual deployment of an EAR.

The in-workspace-deployment mode, which is a very nice feature btw, thx for that, doesn’t work in my case unfortunately. Since our customer demands a Maven build process for the EAR I kind of hacked the pom.xml for the EAR and a enclosing parent project where all application modules (EJBs, Utility-JARs and Web) are located in subdirectories of the parent project. It looks to me the in-workspace-deployment cannot handle this directory/project structure. Anyway, nice feature and I’m really looking forward to the version 10 with Maven support for EARs. 🙂

Back to die deployment problem: I thought so myself, that the EJBDeploy runs during deployment because a temporary EAR is created. But MyEclipse gives me always a yellow redeploy triangle in the Server-View for my application.

Funny thing is that I just retried it again and it worked like a charm… ??? So I guess I’m ok now.

Thx,
Thomas

[support-tony]

OK, Thomas. Thanks for letting us know.

If the problems resurface, please post again.

[Author]

Posts