Description Danny Ju 2007-11-21 15:02:41 EST

Build ID: Build id: M20070921-1145

Steps To Reproduce:
One WebLogic server adapter user had a use case where he wants to use a pre-package EJB jar file in a WTP EAR project. By adding the external EJB jar to EAR project through "J2EE Moudle dependencies", we would expect WTP
recognize the JAR is an EJB and update application.xml
and internal models to reflect the new module. But it doesn't. Without this information, WebLogic and other server adapter will not be able to deploy the EJB properly. 

As a comparison, if an EJB project is added, application.xml
is updated properly.  

Reproduce steps using WLS:
- Create WLS server
- Create Web project and add to EAR
- Deploy EAR to WLS server and make sure it works
- Now find a EJB jar (attached later) compatible with WLS server
- Add the EJB Jar file to EAR through J2EE Dependency
- Notice the application.xml is NOT update with the new moudle
- Update application.xml with the new EJB module (use the JAR file name as module name)
- Start server and deploy

Expected:
- Check WLS console
- EJB jar being deployed as EJB module on server

Actual
- The jar file not deployed as EJB



More information:
Similar result can be reproduced with JBoss4.0 generic server adapter. 

Original bug for WebLogic server adapter 
http://bugzilla.bea.com/show_bug.cgi?id=148