Turns out that it can be done-- though it appears to be painfully slow compared to anything else.
 
What we had to do to get around the NamingContextFactory exception was to set up an Application scope context instead of resetting it each time through.  Now it sets up the context the first time through and just refers to the Application.jndiContext subsequently.
 
The biggest problem is that it takes a  r e a l l y long time to run (the example Interest bean takes nearly 5 seconds on a 800MHz/512MB Linux box.  On the very same machine, the very same bean takes <<1 sec as a JSP or servlet or java app.
 
I can't imagine what the hold up is... but there ya go.  Happy to help if anyone would like more information on what we had to do.
 
Rian
 
-- R i a n  S c h m i d t
-- [EMAIL PROTECTED]
-- Voice: (415)970-0170 / FAX: (415)642-8558
-- Pager: [EMAIL PROTECTED]
-- Fine Brand Media, Inc. - http://www.finebrand.com/
-- Web Development and Maintenance

Reply via email to