You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Scott Eade <se...@backstagetech.com.au> on 2003/09/04 01:29:17 UTC
Torque as an Avalon Component [was: Re: Turbine Error]
David,
Please look at the following post from Henning:
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-dev@jakarta.apache.org&msgNo=15373
Using the configuration provided in the above message I was able
to get Torque running successfully as an Avalon component.
Make sure you also have all of the necessary dependent jar files
loaded - see:
http://jakarta.apache.org/turbine/turbine-2.3/dependencies.html
http://db.apache.org/torque/dependencies.html
I have added this info to an new Avalon Component Service
document that will be up on the site next time it is updated.
HTH,
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
AW: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by Jürgen Hoffmann <jh...@byteaction.de>.
Hi David,
We here had exactly the same Problem. When you step into configure and
see how all the services initialize (thats what we did) you will get to
the point where the PullService initializes. What my Problem was, was
that we had Method Calls to: NameGenerator.CONV_METHOD_UNDERSCORE and
NameFactory.generateName(NameFactory.JAVA_GENERATOR, inputs); which are
now inside of torque-gen-3.1.jar We had the gen on our build path, but
not in the WEB-INF/lib directory. So There was no error, no nothing.
Make sure that you have no calls to static methods inside of your Pull
Tools which might have moved to a separate package now.
Kind regards
A finally pleased User of T2.3
Jürgen Hoffmann
P.S. To the whole Team. GREAT WORK!
-----Ursprüngliche Nachricht-----
Von: David Wynter [mailto:david@roamware.co.uk]
Gesendet: Donnerstag, 4. September 2003 23:43
An: Turbine Users List
Betreff: RE: Torque as an Avalon Component [was: Re: Turbine Error]
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:david@roamware.co.uk]
> Sent: 04 September 2003 20:14
> To: Turbine Users List; hps@intermeta.de
> 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:hps@intermeta.de]
> > Sent: 04 September 2003 13:18
> > To: turbine-user@jakarta.apache.org
> > Subject: Re: Torque as an Avalon Component [was: Re: Turbine Error]
> >
> >
> > "David Wynter" <da...@roamware.co.uk> 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
> > hps@intermeta.de +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: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
turbine-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by David Wynter <da...@roamware.co.uk>.
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:david@roamware.co.uk]
> Sent: 04 September 2003 20:14
> To: Turbine Users List; hps@intermeta.de
> 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:hps@intermeta.de]
> > Sent: 04 September 2003 13:18
> > To: turbine-user@jakarta.apache.org
> > Subject: Re: Torque as an Avalon Component [was: Re: Turbine Error]
> >
> >
> > "David Wynter" <da...@roamware.co.uk> 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
> > hps@intermeta.de +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: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
RE: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by David Wynter <da...@roamware.co.uk>.
Hi Scot,
I always check the archives ;) I had modified the server.xml a while ago to
remove the context entries made by the Eclipse Sysdeo Tomcat plugin. I think
that what Jurgen has said is probably more likely the cause. I will have a
look through the 2 Turbine apps I removed from the directory to see if they
have any references to packages that have moved, they are running on older
versions of T2.3 dev.
Thanks
David
> -----Original Message-----
> From: Scott Eade [mailto:seade@backstagetech.com.au]
> Sent: 05 September 2003 00:42
> To: Turbine Users List
> Subject: Re: Torque as an Avalon Component [was: Re: Turbine Error]
>
>
> David Wynter wrote:
>
> >I played my hunch, T2.3 seems to only tolerate 1 application
> under webapps
> >directory. I moved the other 2 T2.3 applications out from under
> webapps and
> >the one remaining now initialises just fine. A bit of a limitation.
> >
> I have multiple turbine apps running under the same tomcat instance with
> no problems, though only 1 of them is T2.3 at present.
>
> Check the archives for info on double initialisation, I recall
> experiencing
> problems in the past related to modwebapp (for connecting to Apache httpd)
> and other causes of this problem.
>
> I am reasonably sure you will find the limitation stems from a problem in
> your environment.
>
> Scott
>
> --
> Scott Eade
> Backstage Technologies Pty. Ltd.
> http://www.backstagetech.com.au
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
Re: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by Scott Eade <se...@backstagetech.com.au>.
David Wynter wrote:
>I played my hunch, T2.3 seems to only tolerate 1 application under webapps
>directory. I moved the other 2 T2.3 applications out from under webapps and
>the one remaining now initialises just fine. A bit of a limitation.
>
I have multiple turbine apps running under the same tomcat instance with
no problems, though only 1 of them is T2.3 at present.
Check the archives for info on double initialisation, I recall experiencing
problems in the past related to modwebapp (for connecting to Apache httpd)
and other causes of this problem.
I am reasonably sure you will find the limitation stems from a problem in
your environment.
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
RE: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by David Wynter <da...@roamware.co.uk>.
Hi,
I played my hunch, T2.3 seems to only tolerate 1 application under webapps
directory. I moved the other 2 T2.3 applications out from under webapps and
the one remaining now initialises just fine. A bit of a limitation.
David
> -----Original Message-----
> From: David Wynter [mailto:david@roamware.co.uk]
> Sent: 04 September 2003 20:14
> To: Turbine Users List; hps@intermeta.de
> 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:hps@intermeta.de]
> > Sent: 04 September 2003 13:18
> > To: turbine-user@jakarta.apache.org
> > Subject: Re: Torque as an Avalon Component [was: Re: Turbine Error]
> >
> >
> > "David Wynter" <da...@roamware.co.uk> 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
> > hps@intermeta.de +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: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
RE: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by David Wynter <da...@roamware.co.uk>.
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\ActionLoader.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\ActionLoader.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\ActionLoader.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\LayoutLoader.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\LayoutLoader.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\LayoutLoader.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\NavigationLoade
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\NavigationLoade
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:hps@intermeta.de]
> Sent: 04 September 2003 13:18
> To: turbine-user@jakarta.apache.org
> Subject: Re: Torque as an Avalon Component [was: Re: Turbine Error]
>
>
> "David Wynter" <da...@roamware.co.uk> 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
> hps@intermeta.de +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: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
Re: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"David Wynter" <da...@roamware.co.uk> 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/jakarta-turbine-2.3.tar.gz
--13:51:31-- http://www.apache.org/dist/jakarta/turbine/turbine-2.3/source/jakarta-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
hps@intermeta.de +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)
RE: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by David Wynter <da...@roamware.co.uk>.
Hi Scott,
As I said, I already use those, although HEAD is now 2.4 dev. So I use the
ones in the T2.3 release project.xml in the download now available. But
cannot build from the source download for T2.3 release as the Maven build
copies all src tree into target directory and therefore the build fails.
Anybody experienced that?
David
> -----Original Message-----
> From: Scott Eade [mailto:seade@backstagetech.com.au]
> Sent: 04 September 2003 10:48
> To: Turbine Users List
> Subject: Re: Torque as an Avalon Component [was: Re: Turbine Error]
>
>
> David Wynter wrote:
>
> >You pointed me to the dependencies from T2.3 rc2, I used the dependencies
> >list in the project.xml for T2.3 release, and they are different. One key
> >difference is that I am using Torque 3.1 release and that is
> where I think
> >my problem lies.
> >
> David,
>
> Sorry - look at the project.xml files in cvs HEAD for the Turbine
> dependencies that work. They should be updated on the sites fairly
> soon.
>
> Scott
>
> --
> Scott Eade
> Backstage Technologies Pty. Ltd.
> http://www.backstagetech.com.au
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
Re: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by Scott Eade <se...@backstagetech.com.au>.
David Wynter wrote:
>You pointed me to the dependencies from T2.3 rc2, I used the dependencies
>list in the project.xml for T2.3 release, and they are different. One key
>difference is that I am using Torque 3.1 release and that is where I think
>my problem lies.
>
David,
Sorry - look at the project.xml files in cvs HEAD for the Turbine
dependencies that work. They should be updated on the sites fairly
soon.
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
RE: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by David Wynter <da...@roamware.co.uk>.
Hi Jurgen,
Well after my Torque compoennt fails to be found then go on to get 2 double
Turbine initializations attempted (and no there are no extra contexts in my
server.xml, just the root one, but there are 2 other T2.3 apps in webapps
though?) I then get exactly the same as you.
[ERROR] Turbine - -Turbine.handleException:
<java.lang.NullPointerException>java.lang.NullPointerException
at org.apache.turbine.Turbine.doGet(Turbine.java:692)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
....
[ERROR] Turbine - -null
<java.lang.NullPointerException>java.lang.NullPointerException
at org.apache.turbine.Turbine.handleException(Turbine.java:991)
at org.apache.turbine.Turbine.doGet(Turbine.java:867)
Not going too well so far.
David
> -----Original Message-----
> From: Jürgen Hoffmann [mailto:jh@byteaction.de]
> Sent: 04 September 2003 08:31
> To: 'Turbine Users List'
> Subject: AW: Torque as an Avalon Component [was: Re: Turbine Error]
>
>
> Hi David,
>
> I have Torque 3.1 Release and Torque seems to initialize correctly. My
> Problem is the NPE in the RunDataService/Turbine Servlet somewhere.
>
> Kind regards
>
> Jürgen Hoffmann
>
> -----Ursprüngliche Nachricht-----
> Von: David Wynter [mailto:david@roamware.co.uk]
> Gesendet: Donnerstag, 4. September 2003 09:24
> An: Turbine Users List
> Betreff: RE: Torque as an Avalon Component [was: Re: Turbine Error]
>
>
> Hi Scott,
>
> You pointed me to the dependencies from T2.3 rc2, I used the
> dependencies list in the project.xml for T2.3 release, and they are
> different. One key difference is that I am using Torque 3.1 release and
> that is where I think my problem lies.
>
> I have exactly Hennings config, in fact cut and paste it from the
> example in his posting to make sure. Has anyone else used Torque 3.1
> release rather than the Torque 3.1 beta or rc?.
>
> Because I got this mismatch between line numbers (The configure calls
> the TorqueComponent.configure( Configuration configuration) on line 148
> of TorqueComponent.java and the debugger takes me to line 126 I thought
> the src file I had attached to the Torque 3.1 release jar was out of
> step. So I built using Maven from that release src and used that jar. It
> still behaves the same way and this is outside my experience. So am
> still stalled. If you don't believe me I can setup VNCViewer and show
> you.
>
> Thanks
>
> David
>
> > -----Original Message-----
> > From: Scott Eade [mailto:seade@backstagetech.com.au]
> > Sent: 04 September 2003 00:29
> > To: Turbine Users List
> > Subject: Torque as an Avalon Component [was: Re: Turbine Error]
> >
> >
> > David,
> >
> > Please look at the following post from Henning:
> > http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-dev@ja
> > karta.apache.org&msgNo=15373
> >
> > Using the configuration provided in the above message I was able to
> > get Torque running successfully as an Avalon component.
> >
> > Make sure you also have all of the necessary dependent jar files
> > loaded - see:
> > http://jakarta.apache.org/turbine/turbine-2.3/dependencies.html
> > http://db.apache.org/torque/dependencies.html
> >
> > I have added this info to an new Avalon Component Service document
> > that will be up on the site next time it is updated.
> >
> > HTH,
> >
> > Scott
> >
> > --
> > Scott Eade
> > Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
AW: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by Jürgen Hoffmann <jh...@byteaction.de>.
Hi David,
I have Torque 3.1 Release and Torque seems to initialize correctly. My
Problem is the NPE in the RunDataService/Turbine Servlet somewhere.
Kind regards
Jürgen Hoffmann
-----Ursprüngliche Nachricht-----
Von: David Wynter [mailto:david@roamware.co.uk]
Gesendet: Donnerstag, 4. September 2003 09:24
An: Turbine Users List
Betreff: RE: Torque as an Avalon Component [was: Re: Turbine Error]
Hi Scott,
You pointed me to the dependencies from T2.3 rc2, I used the
dependencies list in the project.xml for T2.3 release, and they are
different. One key difference is that I am using Torque 3.1 release and
that is where I think my problem lies.
I have exactly Hennings config, in fact cut and paste it from the
example in his posting to make sure. Has anyone else used Torque 3.1
release rather than the Torque 3.1 beta or rc?.
Because I got this mismatch between line numbers (The configure calls
the TorqueComponent.configure( Configuration configuration) on line 148
of TorqueComponent.java and the debugger takes me to line 126 I thought
the src file I had attached to the Torque 3.1 release jar was out of
step. So I built using Maven from that release src and used that jar. It
still behaves the same way and this is outside my experience. So am
still stalled. If you don't believe me I can setup VNCViewer and show
you.
Thanks
David
> -----Original Message-----
> From: Scott Eade [mailto:seade@backstagetech.com.au]
> Sent: 04 September 2003 00:29
> To: Turbine Users List
> Subject: Torque as an Avalon Component [was: Re: Turbine Error]
>
>
> David,
>
> Please look at the following post from Henning:
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-dev@ja
> karta.apache.org&msgNo=15373
>
> Using the configuration provided in the above message I was able to
> get Torque running successfully as an Avalon component.
>
> Make sure you also have all of the necessary dependent jar files
> loaded - see:
> http://jakarta.apache.org/turbine/turbine-2.3/dependencies.html
> http://db.apache.org/torque/dependencies.html
>
> I have added this info to an new Avalon Component Service document
> that will be up on the site next time it is updated.
>
> HTH,
>
> Scott
>
> --
> Scott Eade
> Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: Torque as an Avalon Component [was: Re: Turbine Error]
Posted by David Wynter <da...@roamware.co.uk>.
Hi Scott,
You pointed me to the dependencies from T2.3 rc2, I used the dependencies
list in the project.xml for T2.3 release, and they are different. One key
difference is that I am using Torque 3.1 release and that is where I think
my problem lies.
I have exactly Hennings config, in fact cut and paste it from the example in
his posting to make sure. Has anyone else used Torque 3.1 release rather
than the Torque 3.1 beta or rc?.
Because I got this mismatch between line numbers (The configure calls the
TorqueComponent.configure( Configuration configuration) on line 148 of
TorqueComponent.java and the debugger takes me to line 126 I thought the src
file I had attached to the Torque 3.1 release jar was out of step. So I
built using Maven from that release src and used that jar. It still behaves
the same way and this is outside my experience. So am still stalled. If you
don't believe me I can setup VNCViewer and show you.
Thanks
David
> -----Original Message-----
> From: Scott Eade [mailto:seade@backstagetech.com.au]
> Sent: 04 September 2003 00:29
> To: Turbine Users List
> Subject: Torque as an Avalon Component [was: Re: Turbine Error]
>
>
> David,
>
> Please look at the following post from Henning:
> http://nagoya.apache.org/eyebrowse/ReadMsg?listName=turbine-dev@ja
> karta.apache.org&msgNo=15373
>
> Using the configuration provided in the above message I was able
> to get Torque running successfully as an Avalon component.
>
> Make sure you also have all of the necessary dependent jar files
> loaded - see:
> http://jakarta.apache.org/turbine/turbine-2.3/dependencies.html
> http://db.apache.org/torque/dependencies.html
>
> I have added this info to an new Avalon Component Service
> document that will be up on the site next time it is updated.
>
> HTH,
>
> Scott
>
> --
> Scott Eade
> Backstage Technologies Pty. Ltd.
> http://www.backstagetech.com.au
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>