shibboleth-dev - RE: Bug 308: Exception thrown on multi-results with JNDI connector

Subject: Shibboleth Developers

List archive

RE: Bug 308: Exception thrown on multi-results with JNDI connector

From: "Scott Cantor" <>
To: "'Chad La Joie'" <>, <>
Subject: RE: Bug 308: Exception thrown on multi-results with JNDI connector
Date: Tue, 17 May 2005 20:49:17 -0400
Organization: The Ohio State University

> JNDI, not JDBC. This isn't an issue with the database stuff.

But what's the difference? If this is the same issue (not sure, but it
sounds similar), why wouldn't we just move the JDBC code that configures the
min/max values up the hierarchy, and then implement the restrictions in the
result set processing in the two connectors.

The only reason I did it that way in the first place is that I didn't have
experience with or examples of JNDI databases to test with.

-- Scott

Bug 308: Exception thrown on multi-results with JNDI connector, Chad La Joie, 05/17/2005
- RE: Bug 308: Exception thrown on multi-results with JNDI connector, Scott Cantor, 05/17/2005
  - Re: Bug 308: Exception thrown on multi-results with JNDI connector, Chad La Joie, 05/17/2005
    - RE: Bug 308: Exception thrown on multi-results with JNDI connector, Scott Cantor, 05/17/2005
      - Re: Bug 308: Exception thrown on multi-results with JNDI connector, Chad La Joie, 05/17/2005
        
        RE: Bug 308: Exception thrown on multi-results with JNDI connector, Scott Cantor, 05/17/2005
        
        Re: Bug 308: Exception thrown on multi-results with JNDI connector, Chad La Joie, 05/17/2005
- Re: Bug 308: Exception thrown on multi-results with JNDI connector, Walter Hoehn, 05/17/2005

List archive

RE: Bug 308: Exception thrown on multi-results with JNDI connector