Also when we tried to extend TurbineUser we had a problem like this. In particular we tried to change the IdMethod for the security tables but it wasn�t possible. The root cause of this sort of problems seems to be that the OM classes are generated when the turbine.jar is complied thus even if you change the schema the changes do not take effect. That also seems to be the reason why you have to create yourself the accesor methods and some of the adaptor classes. I hope somebody can come up with a solution that doesn�t have this kind of problems.
One idea would be to make all the security tables part of the project-schema.xml and generate the OM classes at the same time than the rest of the project. Perhaps in the TurbineResources.properties we could configure the names of the classes where the security information is stored. If this works out extending the TurbineUser would be a matter of adding fields to the table schema. -- Humberto -----Original Message----- From: Martin Poeschl [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 06, 2002 1:46 AM To: Turbine Users List Subject: Re: Extending TurbineUser with new TDK! Saimon Moore wrote: > Hi, > > I've been following the Extending TurbineUser tutorial using martin's > latest > tdk (with torque uncoupled-updated) and have followed it exactly to the > point > where you must call 'ant init' to compile the files (i.e after creating the > mapbuilder, adapters and implementing retrieveByPK() methods.. > > Unfortunately, I'm not having much luck in compiling. The errors are quite > disparate but all seem to point at the extended user files as being the > problem. I'm not quite sure if this is a problem with the latest tdk or if > I've done something wrong. > > From what I can gather there are methods missing from both the basePeer > and > the peer classes that the Manager class is looking for. > > Do I just implement all these methods or am I missing something..? > > I'd appreciate any help on this as I'd like to really get into Turbine > again. > > Thanks > > Saimon > > Here are the compile errors... > compile: > [javac] Compiling 125 source files to > /home/saimonm/development/tdkTDUpdate020302/webapps/didaxe/WEB-INF/classes > [javac] > /home/saimonm/development/tdkTDUpdate020302/webapps/didaxe/WEB-INF/src/java/ org/sam/didaxe/om/BaseDidaxeUserManager.java:200: > > incompatible types > [javac] found : org.apache.turbine.util.db.Criteria > [javac] required: org.apache.torque.util.Criteria > [javac] Criteria crit = DidaxeUserPeer.buildCriteria(om); turbine-2 security still uses the old torque (incl. old Criteria class) your generated om-classes use the decoupled torque ... if we change the turbine-2 internal we will brake existing code ... i'll try to find a solution for this problem martin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
