On Thursday 11 January 2001 08:32, you wrote:

> > I'm trying tdk1.1a10 with IBM JDK 1.3 and postgresql 7.0.2 with and
> > patched jdbc driver that works. 
> >
> > When I try to log in
> > tru a form in a velocity template using the LoginUser action I don't get
> > logged in. The exception catched in LoginUser
> > (catch TurbineSecurityException e) is a DataBackendException with the
> > message = "Failed to check account's presence" 
> >
> > Then I overrided LoginUser (by classpath) and tested to put the code in
> > DBUserManager.accountExists(String username) directly
> > in LoginUser:
> > 
> > Criteria criteria = new Criteria();
> > criteria.add(TurbineUserPeer.USERNAME, username) j
> > java.util.Vector users1 = TurbineUserPeer.doSelect(criteria);  
> > java.util.Vector users2 = TurbineUserPeer.selectAllUsers(criteria);
> >
> > users1 has 1 element. 
> > users2 has 2 elements (I have two users in the db) 
> > BUT the User objects are empty!! 
> > 
> > The TURBINE_LOG says: 
> >
> > -- WARNING -- A DBConnection was finalized, without being returned to the
> > ConnectionPool it belonged to 
> > 
> >
> > (and then I get thrown into DebuggingException("Family waiting") :-)
> >
> >
> > Note: If I get the connection myself and run a sql statement I manage to
> > retrive an result. 
> > 
> > regards killi
>
>
>
> I have seen the "Failed to check account's presence"-exception and the
> empty users under Informix, there the problem seems to result from the
> fact, that Informix returns the meta-information in lowercase. Therefore
> the uppercase search keys for the column names hard coded in the security
> classes can not find the rows read from the database in the hashtables. I
> have to convert all the hardcoded strings for security database elements to
> lowercase by hand, than it works.
> But I'm not shure if this problem is already present, because in some mail
> was mentioned, that this behaviour was corrected/changed, but it was not
> clear if this information belongs to the problem above.
>
> Don't know if this was the root of the problem.
>
> Stefan
>
>


YES! Thanks a lot Stefan!

Thats a very good description of the problem.

An another solution is to change line number 330 in 
org.apache.turbine.om.security.peer.TurbineUserPeer to:

   tempHash.put( columnNames[j].toUpperCase(), obj2 );


regards

killi

  
  

-- 
Penguins are nice animals -
if you get to know them!


------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to