How do you do your lookup? It didn't work for me in the web application unless I used the actual ejb-name (from ejb-jar.xml)in the lookup and not the jndi name. In the other posting you refer to, I see that James Birchfield used a jndi name like 'jdbc/OraclePooledDS'. My interpretation of orion's error message is that you don't have a valid jndi context as in comp:java/env... available. This sounds reasonable to me since you are plugging in the usermanager as part of the container instead of running it as an application within the container. Let me know what you think of this. Marcel Schutte > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > [EMAIL PROTECTED] > Sent: Monday, February 05, 2001 7:09 PM > To: Orion-Interest > Subject: NamingException using custom UserManager with stand alone > applications > > > We have successfully implemented a custom UserManager which acts as a > wrapper around an entity bean that contains user information such as > userid and password. The UserManager works great for authentication > with our web application. However, when we try to authenticate a > user via a stand alone application, a NamingException is thrown in > the UserManager at the point we try to lookup the "wrapped" entity > bean. The NamingException indicates "Not in an application scope - > start Orion with the -userThreads switch if using user-created > threads". I have tried the -userThreads flag without any success. > > The issue appears very similar to the post titled "Custom UserManager > JNDI problem" by James Birchfield on 01/23/01, but I have not see any > follow up. Has anyone had success in similar configurations? Any > pointers would be greatly appreciated. > > Thanks for your time, > > Kent >
