Salut Uwe,
you don't have to run Turbine in a servlet container to use the torque
part. You can run it in a standalone mode. I use torque and the om stuff
in an ant task....
Example:
public class ImportTask extends Task {
public void initTurbine()
{
if(standalone)
{
TurbineConfig tc = new
TurbineConfig(turbineconfig,"TurbineResources.properties");
tc.init();
}
}
public void execute () throws BuildException {
initTurbine();
ImportExhibitor importExhibitor = new ImportExhibitor();
importExhibitor.setPublisherExhibitorId( "" );
importExhibitor.setFairId( convertFairId( "" );
importExhibitor.setOpptyId( results.getString( "" );
.....
importExhibitor.save();
....
}
Hope this helps (at least partly...),
Aleksandar
Uwe Pleyer wrote:
> Hallo folks,
>
> I'am very impressed on the Torque part of Turbine. The ease of use of
> the generated Peer Classes and the resulting clean Design on Objects
> insteed of an summary of JDBC-Calls are great.
>
> I want to use this Part of Turbine as Part of same EJB-EntityBeans to
> implement the persistence mechanics. Therefore I know that I need an
> TurbineConfig Object wich will be initialized first.
>
> Now my questions:
>
> - Can the TurbineConfig run outside the environment of an
> Servlet-Container?
> - Can I use the Peer-Classes whithout initializing TurbineConfig when
> I provide the Connection directly to the Peer.doSelect(crit,con) etc.?
> - Did anyone use the Peer-Classes inside an EJB-Container?
>
> Thanks in advance
> Uwe
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
