EJB MDB project Structure to export
Hi,
I have MDB project checked out from CVS. I have below project folders
VendorAppDomain
VendorAppEAR(I see some of these names in admin console of application server though)
VendorAppEjb
VendorAppStartUp
I need to export the project to EAR file to deploy. Do I need to right click on the EAR project(VendorAppEAR) to select export or EJB project(VendorAppEjb) to export.
What is the purpose of EAR and EJB and Domain projects separately.
I also have WebService project checked out from CVS. I have below project folders
VendorWebServiceAppDomain
VendorWebServiceAppEAR(whe
VendorWebServiceApp
Any links resources ideas highly appreciated. Thanks in advance
I have MDB project checked out from CVS. I have below project folders
VendorAppDomain
VendorAppEAR(I see some of these names in admin console of application server though)
VendorAppEjb
VendorAppStartUp
I need to export the project to EAR file to deploy. Do I need to right click on the EAR project(VendorAppEAR) to select export or EJB project(VendorAppEjb) to export.
What is the purpose of EAR and EJB and Domain projects separately.
I also have WebService project checked out from CVS. I have below project folders
VendorWebServiceAppDomain
VendorWebServiceAppEAR(whe
VendorWebServiceApp
Any links resources ideas highly appreciated. Thanks in advance
mccarl
Do these projects also utilise Maven as their build tool?
ASKER
No. We are not using maven to build. I just export them as EAR and then go to web sphere admin console and deploy manually myself
An EAR file can contain many modules, such as a web archive (war), EJBs (jar), simple classes (also packed in a jar) etc. So think of an EARas a files that can have many EJBs inside it (among other modules).
If the only thing you need to do is to deploy the EJB then I'd say ignore the EAR and deploy the EJB on its own.
If you want to deploy both the EJB and the web project then you can package them in an EAR and deploy them all together or package them in separate files (war for web amd jar for EJB) and deploy them seperately.
If the only thing you need to do is to deploy the EJB then I'd say ignore the EAR and deploy the EJB on its own.
If you want to deploy both the EJB and the web project then you can package them in an EAR and deploy them all together or package them in separate files (war for web amd jar for EJB) and deploy them seperately.
ASKER
>>If the only thing you need to do is to deploy the EJB then I'd say ignore the EAR and deploy the EJB on its own.
I have relevant code in domain project folder as well as VendorAppEjb project folder as well
Actually on the file we are clicking on the export and the next step dropdown we are getting VendorAppEAR(not VendorAppEjbEar) for both MDB and webserrvice projects. I wonder what is the need of VendorAppEjb project.
I have relevant code in domain project folder as well as VendorAppEjb project folder as well
Actually on the file we are clicking on the export and the next step dropdown we are getting VendorAppEAR(not VendorAppEjbEar) for both MDB and webserrvice projects. I wonder what is the need of VendorAppEjb project.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.