On 04.04.13 22:04, Robert Lee wrote:
> When I try
> criteria.clear();
> criteria.addSelectColumn("TURBINE_USER.LOGIN_NAME");
> List userList = TurbineUserPeer.doSelect(criteria);
This at least should work without the addSelectColumn() call. The Peer
class does all the column adding by itself.
> I get
> com.workingdogs.village.DataSetException: Bad conversion:
> java.lang.NumberFormatException: For input string: "admin"
> from the line
> 336 obj.setUserId(row.getValue(offset + 0).asInt());
> in 329 public static void populateObject(Record row, int Offset,
> TurbineUser obj)
> which is called from
> 296 public static TurbineUser row2Object(Record row, int offset, Class
> cls)
This means that the first column read from the dataset is not an integer
- which is true because you added a select column that is declared as
varchar(64). If you add select columns by yourself, you need to handle
row2Object() by yourself. But this is a Torque issue, actually.
> TR.props contains
> services.SecurityService.classname=org.apache.turbine.services.security.torque.TorqueSecurityService
> services.SecurityService.user.manager =
> org.apache.turbine.services.security.torque.TorqueUserManager
>
>
>
> #services.SecurityService.user.class =
> org.apache.turbine.services.security.torque.TorqueUser
> #services.SecurityService.group.class =
> org.apache.turbine.services.security.torque.TorqueGroup
> #services.SecurityService.permission.class =
> org.apache.turbine.services.security.torque.TorquePermission
> #services.SecurityService.role.class =
> org.apache.turbine.services.security.torque.TorqueRole
>
> services.SecurityService.userPeer.class=org.apache.turbine.om.security.peer.TurbineUserPeer
I need to check these. Why do you have a separate userPeer.class? The
configuration should work without this.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
