Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 149945

Summary: Maintain reference to an external datasource profile
Product: z_Archived Reporter: damon <walkinglife17>
Component: BIRTAssignee: Mingxia Wu <mwu>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: lchan, perseusli, wenfeng.fwd, xxue
Version: 2.1.0Keywords: plan
Target Milestone: 2.2.0 M6   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on: 175634    
Bug Blocks:    

Description damon CLA 2006-07-07 02:18:11 EDT 
i got how to use datasource profile & make it work smoothly.
now i found another bug.
pls take the following case:
1.create a new jdbc birt data source named "test" (username as "aaa")in DSE;
2.export this connection to a test profile;
3.create a rpt file using the exported profile from test data source;
4.check the rpt file in editor,that show the datasource username is "aaa";
5.now back to DES,change the datasource'username to "bbb";
6.export it again to overwrite the test profile;
7.ok, let's check the rpt file using test profile,value of the datasource's
username still is "aaa";

well, when i want to change any property of datasource profile,the datasource
of rpt must to be del and using new datasource profile.
is it right?
acceptable process is that when datasource profile changed, the rpt using it
will converted to new one automaticly.

i think there is another way to design this.when using the connection profile
in desgin rpt file, store the path and filename of profile instead of details
of profile.when preview the rpt file, parsing the profile and take the all
properties (JDBC,URL,USERNAME,PW) in use.
wish it is helpful.
could u pls give me some explain on this desgin?
thanks!
Comment 1 Linda Chan CLA 2006-07-07 17:29:15 EDT 
BIRT 2.1 only supports "import" use of a connection profile to create a new data source.  No reference is maintained beyond the initial data source creation.

BIRT plans to have more integration points with the DTP framework in the coming releases.  
Maintaining a reference to an external connection profile instance is one of the enhancements that we are looking into.  

I'd rephased the Summary to reflect the desired behavior.
Comment 2 Linda Chan CLA 2007-02-07 05:05:07 EST 
Committed in DTP 1.5 M5, the ODA runtime support of using externalized properties defined in a linked connection profile instance.  
Also includes the core implementation of adding public properties for a linked connection profile in an ODA data source design.   
BIRT consumption of this ODA feature is scheduled in M6.
Comment 3 Linda Chan CLA 2007-02-26 22:21:10 EST 
Moved the DTP portion of this feature to a new Bugzilla entry for tracking purpose:  https://bugs.eclipse.org/bugs/show_bug.cgi?id=175634

This Bugzilla enhancement now focus on the BIRT consumption of the DTP ODA feature.  It includes changes in 1) BIRT odaconsumer package to specify the use of the DTP ODA profile property provider service, and 2) the BIRT Designer's New Data Source Wizard and Data Source Editor to use the UI pages provided by DTP oda.design.ui for the connection profile selection.
Comment 4 Linda Chan CLA 2007-03-01 00:01:35 EST 
Committed runtime support in BIRT data engine's odaconsumer package to specify the use of the DTP ODA profile property provider service.
Comment 5 Linda Chan CLA 2007-03-01 03:01:23 EST 
Re-assigned for the remaining task in the BIRT Data Source designer.
Comment 6 Mingxia Wu CLA 2007-03-30 08:33:09 EDT 
Add external datasource connection profile support in birt datasource designer. Fix it!