Issue moved from:
https://sourceforge.net/tracker/index.php?func=detail&aid=1410624&group_id=36382&atid=416705
Consult original issue for any attachments.
[ 1410624 ] JROdaDataSource
Submitted By: T. Tetteroo - tetteroo
Date Submitted: 2006-01-20 01:47
Last Updated By: lucianc - Comment added
Date Last Updated: 2006-02-22 09:44
Number of Comments: 7
Number of Attachments: 3
Assigned To: Nobody/Anonymous
Priority: 5
Summary:
JROdaDataSource
Implementation of a japser data source that retrievs data from an given ODA data source.
Comments
Date: 2006-02-22 09:44
Sender: lucianc
Logged In: YES
user_id=1303298
Great! We'll check it out.
Thank you,
Lucian
Date: 2006-02-21 13:05
Sender: tetteroo
Logged In: YES
user_id=1430867
I've added an implementation of a JROdaQueryExecuter and JROdaQueryExecuterFactory. It uses SQL queries similar to the JRJdbcQueryExecuter. The zip file contains the JROdaDataSource and JROdaDataSOurceProvider, too, because of some rework in these files.
Regards,
Torsten
Date: 2006-02-08 09:29
Sender: lucianc
Logged In: YES
user_id=1303298
The query executer framework is now part of the 1.2.0 release. You can take a look at the query executer implementations shipped with JR or ask me if you need any guidance.
The ODA data source support would not be complete without a query executer, therefore we're obviously interested in such an implementation.
Thank you,
Lucian
Date: 2006-02-06 01:30
Sender: tetteroo
Logged In: YES
user_id=1430867
Hi Lucian,
i think such a query executer would be a great idea. And it shouldn't be to much effort to implement a JROdaQueryExecuter as most of the things that have to be
done should be realizable as simple forwards to the odaDataSource objects.
Currently, we are using the stable releases of jasperreports, but i can switch to CVS HEAD, take a look on the query executer and prepare a JROdaQueryExecuter implementation, if you're interested. But i think, i'll need a week to do so.
Regards,
Torsten
Date: 2006-02-01 09:14
Sender: lucianc
Logged In: YES
user_id=1303298
I think that we could improve the ODA support by implementing a query executer besides/instead of a data source provider.
Query executers will be part of the next release and will represent the canonical way to provide data to a report by executing a query. Data source providers are mainly used for GUI tools.
Advantages of an query executer:
- support for query parameters
- connection parameters are passed as report parameters
Let me know what you think.
Regards,
Lucian
Date: 2006-01-31 05:11
Sender: tetteroo
Logged In: YES
user_id=1430867
Hi,
using the native type code as the key for the dataTypeMappings map can fix the problem of inconsistent native type names in manifest and result set metadata (like in the flat file ODA data source). I changed the implementation to support both, name or type
code, as the key for the dataTypeMappings map. Which key shall be used can be specified by the boolean flag 'useNativeName'. I hope, this fixes this problem,
generally.
I've also fixed the errors in JROdaDataSourceProvider.getFields, the value class is now set to the oda scalar type name.
Regards,
Torsten
Date: 2006-01-27 10:56
Sender: lucianc
Logged In: YES
user_id=1303298
Hi
I've tried to use JROdaDataSource with a flat file ODA data source and I got an error because of a type name mimatch: the native type name obtained from the extension manifest was INTEGER while the column type name obtained from the result metadata was INT.
I fixed this by using the native type code as a key for the dataTypeMappings map. Let me know if you think this fix is OK.
Also JROdaDataSourceProvider.getFields requires some fixes:
- fields is never set to a JRDesignField instance
- setValueClassName requires a Java class name
Regards,
Lucian
Attached Files:
Name
odaDataSourceWithQueryExecuter.zip, no description
odaDataSource.zip, zip file containing the 4 files (fixed) of the oda data source package
odaDataSource.zip, zip file containign the 4 files of the oda data source package
Recommended Comments