More information. If I use the componentConfig.xml file as distributed in
the Torque distribution -
<componentConfig>
<torque>
<configFile>/WEB-INF/conf/Torque.properties</configFile>
</torque>
</componentConfig>
Then I get the error
[ERROR]
BaseServiceBroker - -org.apache.turbine.services.InitializationException:
init failed: No value is associated with the configuration element
"configfile" at -
In the console when starting Turbine.
I am using the released Turbine 2.3 and Torque 3.1. I downloaded the T2.3
release because you cannot build using maven from the sources, for some
reason it copies the whole source tree into the /target directory and then
fails the tests because of this.
> -----Original Message-----
> From: David Wynter [mailto:[EMAIL PROTECTED]
> Sent: 03 September 2003 15:32
> To: Turbine Users List
> Subject: RE: Turbine Error
>
>
> Hi,
>
> I have got to the point where line 240 of ConfigUtil.java calls the
> configure method of the TorqueComponent.class
>
> ( (Configurable)object ).configure( configuration );
>
> When I trace into this it goes not the the configure method of
> TorqueComponent (line 148) but instead it goes to line 126? To make sure I
> was matching the src to the jar I used maven to build from the src for
> torque-3.1 release and used that jar.
>
> I thought that maybe I should try the latest T2.3 from HEAD, it fails on
> lots of tests at the moment so I cannot. The version I am using was built
> from the version on 1st September 2003.
>
> I am at a standstill at the moment, cannot debug furhter due to the
> mismapping above. Any ideas?
>
> Thanks
>
> David
>
> > -----Original Message-----
> > From: David Wynter [mailto:[EMAIL PROTECTED]
> > Sent: 03 September 2003 14:32
> > To: Turbine Users List; [EMAIL PROTECTED]
> > Subject: RE: Turbine Error
> >
> >
> > Hi Henning,
> >
> > Yes I am using the release version of torque now. But I still do
> > not pickup
> > the configuration for my components. I have traced into the
> framework and
> > excalibur. It is picking up the roles fine, but not the
> > configuration of the
> > components?
> >
> > By the way in the comment in TurbineAvalonComponentService.java
> > it tells you
> > to add "services.AvalonComponentService.lookup =
> org.apache.torque.Torque"
> > to your TR.props. I did, and it took me a while to realise it
> is wrong, it
> > should be "services.AvalonComponentService.lookup =
> > org.apache.torque.avalon.Torque"
> >
> > I alos downloaded the src for toruq 3.1 release as well as the
> > jar for same.
> > When I trace I cannot resolve the value for torqueComponent on
> line 126 of
> > TorqueComponent.java? And yes, the src file matches the jar file for
> > version? Makes it very hard to debug what is going wrong.
> >
> > With the scheduler component by the time it calls the
> > initialize() method of
> > that component the configuration object is empty. Where is it
> supposed to
> > get populated?
> >
> > Thanks
> >
> > David
> >
> > > -----Original Message-----
> > > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
> > > Sent: 03 September 2003 10:20
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: Turbine Error
> > >
> > >
> > > =?iso-8859-1?Q?J=FCrgen_Hoffmann?= <[EMAIL PROTECTED]> writes:
> > >
> > > >Hi,
> > >
> > > >I have managed to get Torque started as an Avalon Component
> =) Although
> > > >Turbine still gives me a NPE does anyone know what this could be?
> > >
> > > Using Torque 3.1 release? Make sure that you have the right
> commons-dbcp
> > > version.
> > >
> > > Regards
> > > Henning
> > >
> > > --
> > > Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> > > [EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
> > >
> > > Java, perl, Solaris, Linux, xSP Consulting, Web Services
> > > freelance consultant -- Jakarta Turbine Development -- hero for hire
> > >
> > > "Dominate!! Dominate!! Eat your young and aggregate! I have
> > > grotty silicon!"
> > > -- AOL CD when played backwards (User Friendly - 200-10-15)
> > >
> > > ---------------------------------------------------------------------
> > > 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]
> >
>
>
> ---------------------------------------------------------------------
> 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]
