|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1276 | minor | always | 08-07-06 11:27 | 08-07-06 14:34 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.21 | ||
|
|
|||||
| 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. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||