I actually have a working solution now. All the transaction session beans basically share the same home and local interface.
This removes problems of casting to the wrong interface and works like a charm. On Mon, Jan 12, 2004 at 11:45:26AM -0800, Harkness, David wrote: > > I haven't tried this, but in theory it should work. The furthest I've > gone is having a base SLSB class that they all inherit from to supply > logging and other utility methods. However, every lookup narrows the > object to the direct remote interface -- not the base class. However, I > think it should work. Note that since you're using local interfaces > there is no narrowing, so I figure if your SLSBs extend BTL you should > be okay. > > David Harkness > Sr. Software Engineer > Sony Pictures Digital Networks > (310) 482-4756 > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user -- Alwyn Schoeman SMART Money Inc. If you're a SMARTY and you're using the better DNS connections, you can access my homepage at http://nevyn.smarties.com.ph/Members/alwyn. The other unlucky ones: http://10.126.68.24/myplone ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
