Hi,
More information.
I used the standard TR.props file distributed with T2.3 for my test with
T2.3 release on JDK 1.4.2 on W2K.
I get:
...
[DEBUG] TurbineAvalonComponentService - -Application Root is
C:\tdk-2.3\webapps\rwtransform
[INFO] Turbine - -Double initialization of Turbine was attempted!
[INFO] Turbine - -Double initialization of Turbine was attempted!
Starting service Tomcat-Apache
Apache Tomcat/4.0.4
[ERROR] Turbine - -Turbine.handleException:
<java.lang.NullPointerException>java.lang.NullPointerException
at org.apache.turbine.Turbine.doGet(Turbine.java:692)
I traced into init() in Turbine.java
public final void init() throws ServletException
{
synchronized (this.getClass())
{
super.init();
ServletConfig config = getServletConfig();
if (!firstInit)
{
log.info("Double initialization of Turbine was attempted!");
<-------------2nd time through
return;
<-----------------------------------------------------------returns from
here
}
// executing init will trigger some static initializers, so we
have
// only one chance.
firstInit = false;
try
{
ServletContext context = config.getServletContext();
configure(config, context);
<------------------------------------1st time through
templateService = TurbineTemplate.getService();
rundataService = TurbineRunDataFacade.getService();
<----------------------never gets called
The first time thorugh it goes into configure(), never comes out but does
call init() again which means it returns from the spot shown, which means
that TurbineRunDataFacade.getService() nevers gets called. Which is why
rundataService is null when line 692 is reached.
The only thing I can think of is that there are 2 other T2.3 apps under my
webapp directory and maybe they are being intialized by Tomcat?
Regards,
David
> -----Original Message-----
> From: David Wynter [mailto:[EMAIL PROTECTED]
> Sent: 04 September 2003 20:14
> To: Turbine Users List; [EMAIL PROTECTED]
> Subject: RE: Torque as an Avalon Component [was: Re: Turbine Error]
>
>
> Hi,
>
> My objective is to get 2 Avalon components working, Torque and a Scheduler
> based on Quartz. When both failed I fell back to try to get just
> the Torque
> component to work. I discovered that T2.3 had been released and
> upgraded to
> that. Also Torque 3.1. Then I discovered that when I traced through the
> Avalon component configuration into
> TorqueComponent.configure(Configuration
> configuration) that there seemed to be a misalignment between
> Torque source
> I had attached the jar to while tracing. So I downloaded the Torque 3.1
> source and built it using maven b10. This made no difference. Now this was
> outside anything I had ever seen, call to that method on line 148 enters
> code in TorqueComponent at line 126?
>
> So I tried downloading and building T2.3 release from
> http://www.apache.org/dist/jakarta/turbine/turbine-2.3/source/ and copied
> these into a clean directory. Then I ran maven, with no target (default is
> jar). I get
>
> ....
> generate-om:
>
>
> [javac] Since fork is true, ignoring compiler setting.
> [javac] Compiling 401 source files to
> C:\jakarta-turbine-2.3\target\classes
> [javac] Since fork is true, ignoring compiler setting.
> [javac]
> C:\jakarta-turbine-2.3\target\src\org\apache\turbine\modules\Actio
> nLoader.ja
> va:64: cannot resolve symbol
> [javac] symbol : class AssemblerBrokerService
> [javac] location: package assemblerbroker
> [javac] import
> org.apache.turbine.services.assemblerbroker.AssemblerBrokerService;
> [javac] ^
> [javac]
> C:\jakarta-turbine-2.3\target\src\org\apache\turbine\modules\Actio
> nLoader.ja
> va:65: cannot resolve symbol
> [javac] symbol : class TurbineAssemblerBroker
> [javac] location: package assemblerbroker
> [javac] import
> org.apache.turbine.services.assemblerbroker.TurbineAssemblerBroker;
> [javac] ^
> [javac]
> C:\jakarta-turbine-2.3\target\src\org\apache\turbine\modules\Actio
> nLoader.ja
> va:89: cannot resolve symbol
> [javac] symbol : class AssemblerBrokerService
> [javac] location: class org.apache.turbine.modules.ActionLoader
> [javac] private static AssemblerBrokerService ab =
> TurbineAssemblerBroker.getService();
> [javac] ^
> [javac]
> C:\jakarta-turbine-2.3\target\src\org\apache\turbine\modules\Layou
> tLoader.ja
> va:65: cannot resolve symbol
> [javac] symbol : class AssemblerBrokerService
> [javac] location: package assemblerbroker
> [javac] import
> org.apache.turbine.services.assemblerbroker.AssemblerBrokerService;
> [javac] ^
> [javac]
> C:\jakarta-turbine-2.3\target\src\org\apache\turbine\modules\Layou
> tLoader.ja
> va:66: cannot resolve symbol
> [javac] symbol : class TurbineAssemblerBroker
> [javac] location: package assemblerbroker
> [javac] import
> org.apache.turbine.services.assemblerbroker.TurbineAssemblerBroker;
> [javac] ^
> [javac]
> C:\jakarta-turbine-2.3\target\src\org\apache\turbine\modules\Layou
> tLoader.ja
> va:93: cannot resolve symbol
> [javac] symbol : class AssemblerBrokerService
> [javac] location: class org.apache.turbine.modules.LayoutLoader
> [javac] private static AssemblerBrokerService ab =
> TurbineAssemblerBroker.getService();
> [javac] ^
> [javac]
> C:\jakarta-turbine-2.3\target\src\org\apache\turbine\modules\Navig
> ationLoade
> r.java:66: cannot resolve symbol
> [javac] symbol : class AssemblerBrokerService
> [javac] location: package assemblerbroker
> [javac] import
> org.apache.turbine.services.assemblerbroker.AssemblerBrokerService;
> [javac] ^
> [javac]
> C:\jakarta-turbine-2.3\target\src\org\apache\turbine\modules\Navig
> ationLoade
> r.java:67: cannot resolve symbol
> [javac] symbol : class TurbineAssemblerBroker
>
> etc. up to 100 errors before it craps out. Just checked it again and it
> behaves exactly the same.
>
> Then I had a look and found that it had copied the entire src
> tree into the
> target tree.
>
> So then I pointed to the src but used the jar downloaded for JDK 1.4.2
> (which I have switched to from 1.4.1_01 to be able to use the ready built
> jar). Still no joy with my TorqueComponent.configure problem.
> Interestingly
> I have another directory with HEAD (2.4 dev) in it and it builds
> fine on the
> same PC.
>
> Just now I fixed the config for the Avalon Scheduler component and when I
> have both roles specified in roleConfigutration.xml and
> componentConfiguration.xml not only does the Scheduler component work so
> does TorqueComponent, why the change - I have no idea.
>
> Now I am the point where the Avalon components load and configure OK but I
> have exactly the same problem as Jurgen, see his email and my last one for
> details.
>
> That adds up to about 3 days work, bit at least I am closer now and know
> more about Avalon. I am on W2K server
>
> Thanks
>
> David
>
> > -----Original Message-----
> > From: Henning P. Schmiedehausen [mailto:[EMAIL PROTECTED]
> > Sent: 04 September 2003 13:18
> > To: [EMAIL PROTECTED]
> > Subject: Re: Torque as an Avalon Component [was: Re: Turbine Error]
> >
> >
> > "David Wynter" <[EMAIL PROTECTED]> writes:
> >
> > Could you please, at some point, tell us what exactly you're trying to
> > do? You postings are so vague that at last I simply don't understand
> > what you're trying to do how. So please tell us:
> >
> > - Your OS environment
> > - Your JDK
> > - Version of Maven that you're using
> > - What source base you're trying to compile
> > - How do you try to compile?
> > - How does the build fail (exact error message).
> >
> > As for the 2.3 release code:
> >
> > (RedHat Linux 9, JDK 1.4.2, maven-1.0-beta-9-SNAPSHOT)
> >
> > % cd /tmp
> > % wget
> > http://www.apache.org/dist/jakarta/turbine/turbine-2.3/source/jaka
> > rta-turbine-2.3.tar.gz
> > --13:51:31--
> > http://www.apache.org/dist/jakarta/turbine/turbine-2.3/source/jaka
> > rta-turbine-2.3.tar.gz
> > => `jakarta-turbine-2.3.tar.gz'
> > Resolving www-cache.intermeta.de... done.
> > Connecting to www-cache.intermeta.de[192.168.2.3]:3128... connected.
> > Proxy request sent, awaiting response... 200 OK
> > Length: 1,164,296 [application/x-tar]
> >
> > 100%[=============================================================
> ==================================================================
> ==========
> ==============>] 1,164,296 128.68K/s ETA > 00:00
> >
> > 13:51:40 (128.68 KB/s) - `jakarta-turbine-2.3.tar.gz' saved
> > [1164296/1164296]
> >
> > % tar xzf jakarta-turbine-2.3.tar.gz
> > % cd jakarta-turbine-2.3
> > % maven java:jar > & /tmp/logfile
> > % ls -la target/turbine-2.3.jar
> > -rw-r--r-- 1 henning users 764860 Sep 4 14:15
> > target/turbine-2.3.jar
> >
> > => This code definitely builds fine from the release archive.
> >
> > 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]
