0001276: JNDI/EJB issue

Viewing Issue Advanced Details [ Jump to Notes ]

[ View Simple ] [ Issue History ] [ Print ]

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

Platform

Status

closed

Projection

none

OS Version

ETA

none

Fixed in Version

3.0.21

Product Version

Product Build

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

Attached Files

Relationships

Notes
(0001426) ferg 08-07-06 14:34	ejb/083c

Issue History
Date Modified	Username	Field	Change
08-07-06 11:27	ferg	New Issue
08-07-06 14:34	ferg	Note Added: 0001426
08-07-06 14:34	ferg	Assigned To	=> ferg
08-07-06 14:34	ferg	Status	new => closed
08-07-06 14:34	ferg	Resolution	open => fixed
08-07-06 14:34	ferg	Fixed in Version	=> 3.0.21
08-07-06 14:34	ferg	Description Updated

Mantis 1.0.0rc3[^]

29 total queries executed.
25 unique queries executed.