Community
Participate
Working Groups
Build Identifier: 3.2.5 Since EJBs in WAS is part of the EJB 3.1 specification, a EJB project mapped to WEB-INF/lib is a valid scenario, however when EJB jar if the EJB jar is imported as project, it is as Utility project instead of an EJB project. Reproducible: Always Steps to Reproduce: 1.Import the attached EAR file. Import the EJB as project. 2.Check the facets of the project EJB project. You will see the project is an utility project.
Created attachment 207805 [details] EAR sample
Created attachment 207806 [details] Patch
approved
Chava, this works in the development environment, but will fail to compile in the build, since org.eclipse.jst.j2ee.web cannot prereq org.eclipse.jst.j2ee.ejb. Please replace the usage of EJBComponentImportDataModelProvider with something along the lines of: if (EarModuleManager.hasEJBModuleExtension()) { localModel = EarModuleManager.getEJBModuleExtension().createImportDataModel(); } else // just treat it like a utility { localModel = DataModelFactory.createDataModel(new J2EEUtilityJarImportDataModelProvider()); } That alleviates the need for the dependency on the EJB plugin.
Created attachment 208068 [details] Second version patch
Attaching a new version patch.
thanks looks better
Code committed to R3_2_5_patches. Resolving bug