> Okay, so this is probably not an efficient or approved way to combine
> the new torque with turbine, and it does not provide new torque
> functionality to turbine components like the fulcrum security classes.
>
> Basically it is a hack whereby I place some code like this:
>
> public class Index extends SecureScreen
> {
<snip code that statically starts Torque>
> }
> }
>
> into a turbine class. Then I make sure that this init function has
been
> called by other methods in other turbine classes that want to access
the
> database through the new torque.
>
> Basically I am having turbine use its existing database access setup
for
> its existing systems, but in the classes that I implement myself I am
> creating a separate database connection through the new Torque classes
-
> which operates completely separately - i.e. a separate configuration
> file etc.
>
> Hope that helps.
>
> If anyone has any comments on why this is not a good approach I would
be
> very interested to hear them. It seems to have worked so far.
I don't think this is a bad approach, but Scarab had a more elegant
solution that I've copied; create a new TorqueService and add it to
TurbineResources.properties.
It's only 20 or so lines of code:
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
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
