[JRVS]

Hi MyEclipse Support Team,
I have a project that comprises of EJB, EJBClient and Web. The deployment assembly in MyEclipse would show correctly – ejb.jar, ejbclient.jar and web.war for the enterprise EAR project.

But, during deployment it would not deploy the ejbclient.jar in the EAR folder under JBOSS deployments. So, the JBOSS startup would fail with error missing dependency ejbclient.jar. Initially I thought this was a problem in the project itself, but later found this is happening when the project is deployed through MyEclipse deploy option. It does not fail with any errors during deployment though. Deployment shows as though it went through successful.

I tried the same project in Eclipse Juno using Jboss tools and the deployment was fine. All required components ejb.jar, ejbclient.jar and web.war are there.

Any ideas as to what would go wrong and with no errors during deployment I have no clue how to debug this. Please advise.

Thanks!
Sekar.

[support-swapna]

Sekar,

Sorry that you are seeing this issue. I will ask the dev team to take a look into it.
As a workaround, you can right click on the EAR > MyEclipse > Add and Remove Modules, add the EJB Client as a module project to the EAR project and deploy.

[JRVS]

Hi Swapna,
Thanks for the response. I tried your suggestion and that option would come up as blank. I did verify that the EJB Client is associated to EAR and wonder why it won’t show up. Is there any particular place I need to look at to troubleshoot this and see as to why this would not pop up.

Thanks!
Sekar

[support-swapna]

Sekar,

We will fully support EJB Client jars in MyEclipse 11.

Can you try these steps and see if it helps:

1. Add the client project as a dependent project to EAR.
2. Right click on EAR project > Properties > MyEclipse > EAR. Select the option ‘ Jar Dependent Java projects’ under Dependent Java Project Deployment Policies. This should deploy the project to the lib folder of the EAR.
3. Now you only need to modify MANIFEST.MF of the projects which refer to the Client Jar from “ClientProject.jar” to “lib/ClientProject.jar”.

Let us know how it works for you.

[JRVS]

Hi Swapna,
I tried your suggestion but the deployment fails.

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

Clicked on Details
An internal error occurred during: “Add Deploiyment”
java.lang.UnsupportedOperationException.

Starting to wonder if I need go this route of updating Maifest.MF etc to get it work or wait for MyEclipse 11. I looked at MyEclipse road map and it says projected date for MyEclipse 11 is Q4, 2012. So, I believe your team is pretty close to releasing this new version then? 🙂

Thanks!
Vasanth

[support-swapna]

Vasanth,

We have targeted MyEclipse 11 for first quarter of 2013.

Can you please prepare a sample project which exhibits this issue and send it over to help us replicate the issue at our end ?

[Author]

Posts