Anonymous | Login | Signup for a new account | 12-17-2024 08:47 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001276 | [Resin] | minor | always | 08-07-06 11:27 | 08-07-06 14:34 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | |||||||
Summary | 0001276: JNDI/EJB issue | ||||||||
Description |
It seems as though none of the EJB's declared in our .ejb file are being deployed or made available to JNDI. I noticed a recent change in the EJB deployment code between .19 and .20 in com.caucho.ejb.cfg.EjbConfig.deployBeans(). Specifically, the following commented out section stuck out to me: /* XXX: handled by bean.deployServer if (bean.getServerProgram() != null) bean.getServerProgram().configure(server); */ I don't see where that functionality was moved to or if it is actually significant. The exact same application code runs fine in the 7/05 snap and earlier versions. I found this after stepping into our JNDI lookup code and examining the /ejb Context object's MemoryModel. In the 8/03 snap the "_children" are empty but in the 7/05 snap and earlier, "_children" is chock full of EJB's. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 25 unique queries executed. |