> Someone mentioned calling Torque.init(). This doesn't seem right, this > should be handled by Fulcrum or Turbine, correct?
No. With all the decoupling, T3 doesn't internally use Torque. It loads all its info from the TurbineResources.properties file and doesn't do any database persistence. The internals of T2 (e.g. just the servlet/module stuff, not the pre-Fulcrum security) didn't use Torque either, but everything was still coupled so T2 went ahead and initializing it for you. In T3, you have to specifically init Torque in any number of possible ways. Personally, I found Scarab's approach to be appealing, they created a Fulcrum service and put it into TurbineResources.properties. http://scarab.tigris.org/source/browse/scarab/src/java/org/tigris/scarab /services/TorqueService.java?rev=1.1&content-type=text/x-cvsweb-markup - Stephen > > I have also looked at Scarab and how it is configured and copied some of its > methods that were not mentioned here: > http://jakarta.apache.org/turbine/torque/jdbc2pool-howto.html > I added: > torque.database.default=community > > Even with all of this configuration Torque does not appear to be starting. > How can I identify Torque in the log file? > > Certainly there are others out there using decoupled Torque with T3. > > Thank you for your time. > > -warner > > +warner onstine+ > > > -- > To unsubscribe, e-mail: <mailto:turbine-torque-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-torque-user- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
