I posted a prob. with my own UserManager implementation yesterday, and I
said I got it working when I put my class-files inside orion.jar. 

Well, not quite true, now I get this in the application.log for my
application:

---snip---

4/4/00 12:36 PM lektor-web: Error in UserManager
java.lang.RuntimeException: can't lookup datasource
(jdbc/DefaultPooledDS): javax.naming.NamingException: Not in an
application scope - start Orion with the -userThreads switch if using
user-created threads
        at
com.lektor.j2ee.orion.LektorUserManager.getUser(LektorUserManager.java,
Compiled Code)
        at
com.evermind.server.http.EvermindHttpServletRequest.getUserPrincipal(JAX,
Compiled Code)
        at com.evermind.server.http.HttpApplication.oe(JAX, Compiled Code)
        at com.evermind.server.http.HttpApplication.nk(JAX, Compiled Code)
        at com.evermind.server.http.dc.ca(JAX)
        at com.evermind.util.b.run(JAX, Compiled Code)
4/4/00 12:37 PM lektor-web: Stopped

---snip---

Why the heck? Have the UserManager related stuff ever been tested with
other UserManagers than the ones that come with orion as default?

The thing I do that trigger the exeption is this:

ConnectionPoolDataSource ds;

try {
    ds = (ConnectionPoolDataSource) ictx.lookup(datasource);
} catch (NamingException e) {
    throw new RuntimeException ("can't lookup datasource (" +
datasource + "): " + e);
}

Where 'datasource' is a string with the value "jdbc/DefaultPooledDS".


Am I missing something obvious, or is the UserManager stuff in orion
seriously screwed?

/Rgrds. Jimmy

__________________________________________________________________________
Jimmy Larsson, N�takademin AB, http://www.natakademin.se                 
  e-mail: [EMAIL PROTECTED]
  Tel: 08 - 751 00 40, 070 - 950 39 65


Reply via email to