Bugs item #634677, was opened at 2002-11-06 21:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=634677&group_id=22866
Category: JBossServer Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Colin Sampaleanu (colins) Assigned to: Nobody/Anonymous (nobody) Summary: EJB in ja in server lib dir auto-deploys Initial Comment: If a jar is added to the server lib dir (e.g. server/default/lib), to make use of some classes in that jar, and that jar also contains one or more EJBs, those EJBs are automaticallly deployed as the server is started. This is quite problematic. Even if deployment of the EJBs was desired, the auto-deployment at this time happens before some other resources have been deployed (such as datasources, etfc.) that the EJBs may need. Ideally EJBs are packaged standalone, separate from other java classes. However, it is quite legal to put them together with other code. OSUser, from OpenSymphony, for example, is packaged in this fashion. Inside the jar file is a JBoss login module, which to be available to used by JBoss requires the osuser.jar to be added to the server lib dir. Inside OSUser.jar are also some EJBs, useful in other osusr usage scenarios. Those EJBs then (erronously) automatically get deployed at server startup. This bug is somewhat similar to the (resolved) bug # 589808 (EJB Jars already deployed by MANIFEST.MF), and a resolution should be similar. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=634677&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
