If your Xxx a table that exists in two schemas that you are generated? That will cause an overlap problem as I just coincidentally noted on turbine-user.
- Stephen > -----Original Message----- > From: Rick Ross [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, August 28, 2002 11:54 AM > To: Turbine Torque Users List > Subject: A fun error.... > > It seems that b3 is generating multiple methods in the BaseXXXPeer's. For example: > > [echo] ./build/WEB-INF/classes > [javac] Compiling 97 source files to ..\build\WEB-INF\classes > [javac] ..\model\BaseCriteriaPeer.java:432: doSelect(versifi.model.Criteria) is > already defined in versifi.model.BaseCriteriaPeer > [javac] public static List doSelect(Criteria obj) throws TorqueException > > As you can see, two "doSelect" methods are created with similar signatures. Here > they are: > > /** Method to do selects */ > public static List doSelect(Criteria criteria) throws TorqueException > { > return populateObjects(doSelectVillageRecords(criteria)); > } > > And > > > /** Method to do selects */ > public static List doSelect(Criteria obj) throws TorqueException > { > return doSelect(buildCriteria(obj)); > } > > Has anyone else had a problem like that? Four or five other methods had the same > problem. > > > Rick Ross > > "Patriotism is the last refuge of the scoundrel" > > - Samuel Johnson -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
