- This topic has 29 replies, 6 voices, and was last updated 10 years, 3 months ago by
.
-
Posts
-
I have created a simple Maven EJB 2.0 Project and now I’m trying to run the EJB Deploy command. I am trying to deploy to WebSphere 7.0. My server configuration is setup for in-workspace mode. The EJB project has 3 Facets (EJB 2.0, Java 1.6 and Maven). When I run the EJB Deploy command against the project I receive a message “The primary runtime of project does not support EJB Deploy. Do you want to choose a different one now?” If I select “Yes”, it brings up the MyEclipse -> EJB Deploy properties with no selectable target runtimes. If I then click on the project -> MyEclipse -> Project Facets there is a tabbed window on the right. If I select the Runtimes tab it is empty. If I click on show all runtimes I see WebSPhere 7 in the list but all runtimes are disabled. If I uncheck the Maven Facet, the WebSphere 7.0 runtime becomes selectable. Can you tell me what I need to do so that I can deploy this EJB 2.0 Maven project to WebSPhere 7? My uinderstanding is that I need to manually do the EJB deploy since I am using EJB 2.0.
sfmarv,
I am afraid the In-Workspace mode will not work with Maven projects. I have filed a bug for the dev team to take a look into it.
As a workaround, please try the classic mode of deployment. If you want to work with In-Workspace mode you should manually remove the Maven facet from the project. Edit the /.settings/org.eclipse.wst.common.project.facet.core.xml file in the project and remove the line :
<installed facet=”maven” version=”1.0″/>Let us know if you see any issues.
Swapna,
Is it just the Maven EJB projects that do not work with “in-workspace” mode? I have another set of non J2EE Maven projects (JARs, WAR and EAR) that I’m running in “in-workspace” mode and it appears to be working. Since you reported this as a bug to the dev team, how can I track the status of this issue. Running in classic mode will slow down our development team so this is definitely going to be a problem for us. We cannot disable Maven because the whole purpose of the current project is to convert from ANT to Maven. We are currently running the same non-Maven J2EE projects in “in-workspace” mode. I think it’s going to irritate the developers if I tell them they need to go back to classic mode or that everyone needs to obtain a JRebel license. 🙁
sfmarv,
The Maven EJB projects do not work with In-Workspace deployment mode. Also In-Workspace mode might work with Maven projects if they have a simple DA (Deployment Assembly).The fix for the issue will be out with MyEclipse 2015 which is targeted to release in June 2014. Unfortunately, we are unable to give you any workaround right now.
Sorry for inconvenience caused. Let us know if you have any questions.
Swapna,
I changed my server configuration to “classic” mode. I am still not able to execute “Run EJB Deploy” on the Maven EJB projects. It is having the same issue. I’m not able to select a runtime. Is there something I need to modify in my projects to get this to work? Thanks.
sfmarv,
If you are not using the In-Workspace mode for deployment, you do not need to run the EJB Deploy Tool. Try deploying the project directly and see how it works for you.
sfmarv,
This problem has been fixed in our 2015 CI 1 release. For information about this release, please see this announcement.
Thanks for reporting the issue and sorry for the inconvenience it caused.
I am seeing the same problem. If I deploy my ear to the server, even in packaged mode, it doesn’t run ejb deploy. If I go back via the WebSphere console and update the application using the ear that got copied to installableApps, it then runs ejb deploy and the application runs properly. Am I missing a step or a configuration or something?
dmfahey ,
If you are not using the in-workspace mode, you do not need to manually run the EJB Deploy tool before deploying to the server. You can deploy the project directly and the Websphere’s ejb deploy tool will be run when you deploy the project.
Can you please give us some more information?
1. Can you please let us know what happens if you directly deploy the project to the server? Please share the deployment log if you see any issues. The deployment log is located under directory .myeclipse/logs in EAR project. Before sending, please delete that file and perform deployment.
2. Please share details about your project. Is your project a Maven EJB project? If yes then which version of EJB?
3. Please share what exact error you are seeing when running the EJB Deploy tool from MyEclipse. Also share the Installation Details from MyEclipse > Installation Summary > Installation Details.
1) If I run ejbdeploy against the ear project, I get a dfialog that says the “EAR project does not contain 2.x EJB projects.”
2) The project is an EAR project containing EJB 2.0 projects.
3) EJBdeploy does not seem to be running. If I update the EAR through the WAS console ejbdeploy runs. See the attached deployment.logdmfahey,
Thank you for the details. The deployment log is missing. I can only see the installation details attachment. I do not see any issues running EJB Deploy on EAR with EJB 2.x projects at my end.
Can you please give us some more information?
1. Is the EAR created in MyEclipse ? If its created in any other IDE, please share its version details. Also share the Websphere version details.
2. If you have imported this project, did you go through the migration wizard ? Did you see any errors during migration?
3. Please switch to a new workspace, import the EAR project and run the EJB Deploy tool. Check if there are any errors of interest logged in the .log file which is located at <workspace dir>/.metadata/.log. If yes then please copy paste them here.
4. If you do not have any reservations sharing the EAR project and its modules with us, please send us the project to help us replicate the issue at our end. If you cannot share the entire project, please strip the project of its source code and send us all the .* files of the EAR project and its modules.
Sorry, my computer crashed and I was unable to recreate the problem until now. I have attached a copy of deployment.log, which seems to show a -noejbdeploy option.
dmfahey,
In-workspace deployment is always a noejbdeploy deployment. noejbdeploy means that EJBDeploy is not run by the server.
Can you please check these steps ?
1. Check if the EJB modules are listed in the Deployment Assembly of the EAR project.
2. Check if EJB module has 2.0 facet. Right click on EJB project > Properties > MyEclipse > Project Facets. Check the version of the EJB Module.
3. You can run the EJB Deploy directly on the EJB project. Right click on EJB project > MyEclipse > Run EJB Deploy.
4. If you are still seeing issues, please send us the EAR project along with its modules to help us replicate the issue at our end.
Let us know how it works for you.
Swapna,
I work with dmfahey and smarv. I have tried your suggestions and here are the results.
1. Check if the EJB modules are listed in the Deployment Assembly of the EAR project.
The EJBs are listed there along with a web module2. Check if EJB module has 2.0 facet. Right click on EJB project > Properties > MyEclipse > Project Facets. Check the version of the EJB Module.
Project Facet shows EJB 2.03. You can run the EJB Deploy directly on the EJB project. Right click on EJB project > MyEclipse > Run EJB Deploy.
Run EJB Deploy fails with this message: Primary runtime of the project xxxxx does not support EJB Deploy. Do you want to choose a different one now?4. We cannot send you the EAR file.
We really need to get the “In-Workspace” mode working for development. We have converted all of our projects to Maven but now are not able to deploy “In Workspace” mode. The other modes will cost us a lot of time. Do you have any other suggestions?
