On Thursday, May 9, 2002, at 03:59 AM, Fabio Daprile wrote: > i've tried to do what is written in your post, but i have some problems. > First i'm using Torque to generate the peers to access the database. > I've seen that there are some differences in the turbine classes. > For example a property NONE is missing in turbine.util.db.map.tableMap.
Hi Fabio. If I understand you correctly, you have already started with Torque and are now trying to use Turbine and the TDK. Is that correct? If so you are working on a different problem than I was describing originally. You might have a somewhat easier time of it. If you have used the decoupled Torque alone, then you will be familiar with the Torque.properties file. In Turbine 2.2 beta the decoupled Torque and Fulcrum are loaded as components. Here's an example of how to tell Turbine to start Torque as a component: TurbineResources.properties: component.name = torque component.torque.classname = org.apache.torque.Torque component.torque.config = /path/to/Torque.properties This should allow you to use objects you have created using the decoupled Torque without further modification. Be alert as you develop in this way. Because Turbine 2.2 still has the old coupled torque code within, you probably need to be careful about which classes you import in your code. Mixing classes between the two versions of torque could cause some confusing problems. I should add that I haven't actually tried using both Torque versions yet (we are still using the old Torque stuff in our apps for the time being). Please also take a look at my other post titled "Which to choose: Turbine 2.1, 2.2 or 3.0" for more info. Hope that helps more than it confuses. 8^) -Eric -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
