[2.1.2 -> 2.2.0] Erreur de connexion base de données [Fait] [Résolu]

[slobberbone]

Bonjour à tous !!

Je ne poste pas très souvent, mais je lis pas mal de posts à droite à gauche qui m'apportent la plupart du temps des réponses. Ce coup-ci, ça n'est aps vraiment le cas ...

Voici mon problème, mon appli java génère tout ce que je veux peux importe la bdd (mysql,oracle,sqlqerver) avec birt 2.1.2, hors rien que le fait de passer en 2.2.0 me fait obtenir cette erreur ci :

Code :

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
26 oct. 2007 11:00:04 org.eclipse.birt.report.data.oda.sampledb.SampledbPlugin start
INFO: Sampledb plugin starts up. Current startCount=0
26 oct. 2007 11:00:04 org.eclipse.birt.report.data.oda.sampledb.SampledbPlugin init
INFO: Creating Sampledb database at location D:\Dev\OTAppServer\V7.3.3\apache-tomcat-5.5.12\temp/BIRTSampleDB_1193389204524_1c4c955
26 oct. 2007 11:00:20 org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager loadAndRegisterDriver
ATTENTION: Failed to load JDBC driver class: net.sourceforge.jtds.jdbc.Driver
26 oct. 2007 11:00:20 org.eclipse.birt.data.engine.odaconsumer.ConnectionManager openConnection
GRAVE: Cannot open connection.
org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot load JDBC Driver class: net.sourceforge.jtds.jdbc.Driver 
	at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.loadAndRegisterDriver(JDBCDriverManager.java:605)
	at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.doConnect(JDBCDriverManager.java:180)
	at org.eclipse.birt.report.data.oda.jdbc.JDBCDriverManager.getConnection(JDBCDriverManager.java:146)
	at org.eclipse.birt.report.data.oda.jdbc.Connection.connectByUrl(Connection.java:150)
	at org.eclipse.birt.report.data.oda.jdbc.Connection.open(Connection.java:111)
	at org.eclipse.datatools.connectivity.oda.consumer.helper.OdaConnection.open(OdaConnection.java:235)
	at org.eclipse.birt.data.engine.odaconsumer.ConnectionManager.openConnection(ConnectionManager.java:149)
	at org.eclipse.birt.data.engine.executor.DataSource.newConnection(DataSource.java:134)
	at org.eclipse.birt.data.engine.executor.DataSource.open(DataSource.java:121)
	at org.eclipse.birt.data.engine.impl.DataSourceRuntime.openOdiDataSource(DataSourceRuntime.java:214)
	at org.eclipse.birt.data.engine.impl.QueryExecutor.openDataSource(QueryExecutor.java:265)
	at org.eclipse.birt.data.engine.impl.QueryExecutor.prepareExecution(QueryExecutor.java:210)
	at org.eclipse.birt.data.engine.impl.PreparedQuery.doPrepare(PreparedQuery.java:486)
	at org.eclipse.birt.data.engine.impl.PreparedDataSourceQuery.execute(PreparedDataSourceQuery.java:161)
	at org.eclipse.birt.data.engine.impl.PreparedOdaDSQuery.execute(PreparedOdaDSQuery.java:142)
	at org.eclipse.birt.report.data.adapter.impl.DataRequestSessionImpl.execute(DataRequestSessionImpl.java:423)
	at org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExecuteQuery(DteDataEngine.java:149)
	at org.eclipse.birt.report.engine.data.dte.DteDataEngine.doExecuteQuery(DteDataEngine.java:115)
	at org.eclipse.birt.report.engine.data.dte.AbstractDataEngine.execute(AbstractDataEngine.java:178)
	at org.eclipse.birt.report.engine.executor.ExecutionContext.executeQuery(ExecutionContext.java:1678)
	at org.eclipse.birt.report.engine.executor.QueryItemExecutor.executeQuery(QueryItemExecutor.java:82)
	at org.eclipse.birt.report.engine.executor.DynamicTextItemExecutor.execute(DynamicTextItemExecutor.java:72)
	at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.execute(WrappedReportItemExecutor.java:45)
	at org.eclipse.birt.report.engine.internal.executor.l18n.LocalizedReportItemExecutor.execute(LocalizedReportItemExecutor.java:33)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:86)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:91)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:91)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:91)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:91)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeMasterPage(ReportExecutorUtil.java:70)
	at org.eclipse.birt.report.engine.layout.pdf.PDFPageLM.startPage(PDFPageLM.java:240)
	at org.eclipse.birt.report.engine.layout.pdf.PDFPageLM.layout(PDFPageLM.java:211)
	at org.eclipse.birt.report.engine.layout.pdf.PDFReportLayoutEngine.layoutReport(PDFReportLayoutEngine.java:64)
	at org.eclipse.birt.report.engine.layout.pdf.PDFReportLayoutEngine.layout(PDFReportLayoutEngine.java:87)
	at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:148)
	at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:71)
	at com.optitime.otffa.businesslayer.report.utils.ReportingTools$RenderTask.executeReport(ReportingTools.java:141)
	...
26 oct. 2007 11:00:20 org.eclipse.birt.report.engine.data.dte.DteDataEngine doExecuteQuery
GRAVE: Cannot open the connection for the driver: org.eclipse.birt.report.data.oda.jdbc
Cannot load JDBC Driver class: net.sourceforge.jtds.jdbc.Driver 
26 oct. 2007 11:00:20 org.eclipse.birt.report.engine.executor.ExecutionContext evaluate
GRAVE: ReferenceError: "row" n'est pas défini (<inline>#1)
org.mozilla.javascript.EcmaError: ReferenceError: "row" n'est pas défini (<inline>#1)
	at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3240)
	at org.mozilla.javascript.ScriptRuntime.constructError(ScriptRuntime.java:3230)
	at org.mozilla.javascript.ScriptRuntime.notFoundError(ScriptRuntime.java:3303)
	at org.mozilla.javascript.ScriptRuntime.name(ScriptRuntime.java:1566)
	at org.mozilla.javascript.gen.c11._c0(<inline>:1)
	at org.mozilla.javascript.gen.c11.call(<inline>)
	at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:304)
	at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2769)
	at org.mozilla.javascript.gen.c11.call(<inline>)
	at org.mozilla.javascript.gen.c11.exec(<inline>)
	at org.eclipse.birt.core.script.ScriptContext.eval(ScriptContext.java:223)
	at org.eclipse.birt.report.engine.executor.ExecutionContext.evaluate(ExecutionContext.java:571)
	at org.eclipse.birt.report.engine.executor.ExecutionContext.evaluate(ExecutionContext.java:550)
	at org.eclipse.birt.report.engine.executor.DynamicTextItemExecutor.execute(DynamicTextItemExecutor.java:88)
	at org.eclipse.birt.report.engine.internal.executor.wrap.WrappedReportItemExecutor.execute(WrappedReportItemExecutor.java:45)
	at org.eclipse.birt.report.engine.internal.executor.l18n.LocalizedReportItemExecutor.execute(LocalizedReportItemExecutor.java:33)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:86)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:91)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:91)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:91)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeAll(ReportExecutorUtil.java:91)
	at org.eclipse.birt.report.engine.executor.ReportExecutorUtil.executeMasterPage(ReportExecutorUtil.java:70)
	at org.eclipse.birt.report.engine.layout.pdf.PDFPageLM.startPage(PDFPageLM.java:240)
	at org.eclipse.birt.report.engine.layout.pdf.PDFPageLM.layout(PDFPageLM.java:211)
	at org.eclipse.birt.report.engine.layout.pdf.PDFReportLayoutEngine.layoutReport(PDFReportLayoutEngine.java:64)
	at org.eclipse.birt.report.engine.layout.pdf.PDFReportLayoutEngine.layout(PDFReportLayoutEngine.java:87)
	at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:148)
	at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:71)
	...

Je suppose que celà vient de la manière dont je passe mes paramètres à Birt donc voici la portion de code que j'utilise :

Code :

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
 
static private class RenderTask {
                public IReportRunnable design = null;
                public IRunAndRenderTask task = null;
 
 
		public boolean executeReport(List<ReportParameter> params) throws EngineException {
			task.setParameterValue("source_DriverClass", driverClass);
			task.setParameterValue("source_DatabaseURL", dataBaseURL);
			task.setParameterValue("source_UserName", userName);
			task.setParameterValue("source_Password", password);
			task.setParameterValue("leftIcon", leftIconName);
			task.setParameterValue("rightIcon", rightIconName);
			task.setParameterValue("company", company);
 
			// set SnapshotId, begin, end... parameters
			for (ReportParameter p : params) {
				task.setParameterValue(p.getName(), p.getValue());
			}
 
			task.run();

Et c'est donc dan cette fonction run() que ça plante ... sachant qu'en repassant à birt 2.1.2 celà fonctionne !

Toutes les données ont la meme forme et sont corretces ...

Avez-vous une idée ?

D'avance merci !

[BiM]

Bonjour,

Il n'arrive pas à charger ton Driver JDBC tout simplement. Vérifie que celui-ci est bien disponible.

[slobberbone]

Merci pour ta réponse, mais comment se fait-il qu'avec la version précedente de Birt sans rien modifier, il arrive à le charger ... et plus maintenant ???

[gattino]

La gestion des classpaths a été revue en 2.2.x... résultat des courses tout a refaire niveau config et accessibilité des classes/jars en tout genre...

Voir du côté des FAQ Birt:

JDBC Drivers

You will likely want to use your own JDBC driver with BIRT. Use the data source editor’s JDBC driver management wizard. To start the wizard, open a BIRT report design, go to the Data Explorer view, right click on “Data Sources” and select “New Data Source”. Choose “JDBC Data Source” and click “Next”. In the next dialog, choose “Manage Drivers…” to bring up the “Manage JDBC Drivers” dialog.

In the “JAR Files” tab, click on “Add…” to add the JAR file required by your JDBC driver. Then go to the “Driver” tab to confirm that the list of drivers includes the new drivers added. You may also want to assign a display name and URL template for the new drivers in this tab.

lien: http://www.eclipse.org/birt/phoenix/build/#drivers

Peut être qu'il faut que tu le (re)fasses une fois ;-)

Bon courage

[slobberbone]

Ok merci beaucoup je vair voir ça !!

[nymorg]

Oui mais comment fait on pour declarer le driver depuis l'API?

J'ai essayé dans le classpath , la datasource la config du report engin et rien ne marche : toujours no class found exception

[Stefan C]

Dans le designer , engine ET viewer , il y a un chemin pour les jar des JDBC

A savoir :

\plugins\org.eclipse.birt.report.data.oda.jdbc_2.2.2.v20071218-1951\drivers