No, retrieving & saving work fine and the velocity log seems to show
it connected OK.
Tim Howland wrote:
Maybe the mysql driver isn't in your classpath?
-----Original Message-----
From: rankin [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 04, 2004 7:17 AM
To: [EMAIL PROTECTED]
Subject: maven torque:datadump fails w/ mysql fails - Suggestions?
Suggestions or help would be appreciated -
using latest torque I get a spurious stack trace (the driver's really
fine & I think it has connected to mysql):
torque:datadump:
Using contextProperties file:
/usr/local/turbine.apps/myapp/build.properties
[torque-data-dump] Using classpath
[torque-data-dump] Generating to file
/usr/local/turbine.apps/ocip/target/sql/report.myapp.datadump.generation
[torque-data-dump] Torque - TorqueDataDump starting
[torque-data-dump] Your DB settings are:
[torque-data-dump] driver: com.mysql.jdbc.Driver
[torque-data-dump] URL:
[torque-data-dump] user: root
SQLException while connecting to DB:
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:532)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at
org.apache.torque.task.TorqueDataDumpTask.initControlContext(TorqueDataD
umpTask.java:200)
at
org.apache.velocity.texen.ant.TexenTask.execute(TexenTask.java:480)
at org.apache.tools.ant.Task.perform(Task.java:341)
at
org.apache.commons.jelly.tags.ant.AntTag.doTag(AntTag.java:232)
at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.j
ava:79)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAc
tion(MavenGoalTag.java:110)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at
com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
at
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634
)
at
org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
at org.apache.maven.cli.App.doMain(App.java:486)
at org.apache.maven.cli.App.main(App.java:1215)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
BUILD SUCCESSFUL
the tail of the velocity.log is:
Sat Dec 04 06:08:57 CST 2004 [info] Velocimacro : initialization
complete.
Sat Dec 04 06:08:57 CST 2004 [info] Velocity successfully started.
Sat Dec 04 06:09:06 CST 2004 [info] ResourceManager : found
data/dump/Control.vm with loader
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
Sat Dec 04 06:09:06 CST 2004 [info] ResourceManager : found
data/dump/top.vm with loader
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
Sat Dec 04 06:09:07 CST 2004 [info] ResourceManager : found
data/dump/bottom.vm with loader
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
---------------------------------------------------------------------
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]
