[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[news.eclipse.dtp] Re: [ODA Ecore] Connection Profiles and Connection Properties

Hi John,
A quick update on this: I believe the bits are ready to get this feature working as you have requested. Unfortunately, the change will break existing reports because of the way we currently store our properties and the way we put the file URI in those properties. I will need to get Jeff's second pair of eyes on my code to make sure everything looks good before checking in and to make sure he is comfortable committing breaking changes.
These are the latest changes. Please let me know if they sound like what you need:
1. It is possible to create a Connection Profile for the Ecore ODA data source. The Connection Profile stores the URI for the ecore file.
2. It is now possible to use BIRT property binding to dynamically set the URI of the ecore model (the data source property is exposed publicly).
3. There is now a 3rd option on the data source selection dialog page that allows a user to configure a literal URI for the ecore model (as well as options for using a filesystem or workspace resource, which are browsable as Ed Merks noted in another thread).


Note that I have not exposed the DataSet properties (the queryString or the column list) for dynamic property binding. This would represent another breaking change if the feature were requested in the future.

One thing -- I would probably ask for your help in verifying that the implementation does what you expect, as I am not sure how I would set up a functional test case for the Connection Profile or Connection Properties features.
Let me know if it sounds like these features suit your needs.
Thanks for your patience.


-----Tim------


Tim Myer wrote:
Hi John,
I made some good progress on this over the weekend but did not get the changes checked in yet. I will update the posting when the code is in so you can see if the implementation fits your needs.
-----Tim-----


Tim Myer wrote:
Hi John,
Terrific. Much appreciated.
I have started looking into an implementation for this. I'll try to get something into CVS this weekend and to fit your scenario.
------Tim------


John E. Conlon wrote:
Hi Tim,

Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=243499
to ask for addition of Connection Properties.

thanks,
John


John E. Conlon wrote:
Hi Tim,

Well they can stand alone but both are needed.

I will open a bug for an enhancement to add Connection Properties as well.


cheers, John

Tim Myer wrote:
Hi John,
If they represent 2 independent features, then I would say "yes". If Connection Profiles require Connection Properties, and if Connection Properties are only useful in conjunction with Connection Profiles, then a separate bug might be in order. That's just my thought on the subject and I would be interested to hear others (especially as I have not used Connection Profiles and Properties before so am speaking without experience).
Thanks.
-----Tim------


John E. Conlon wrote:
Hi Tim,

Shall I open a bug for the lack of Connection Properties as well?

John
Tim Myer wrote:
Hi John,
Thanks very much for the use case and for the steps to reproduce this. I will be looking into the bug you filed and will update it soon.
-----Tim-----


John E. Conlon wrote:
As I am just coming up to speed with BIRT, I have been going through the Field Guild Book as I am working with the ODA Ecore. While I have been able to generate reports with the ODA Ecore I have noticed that it does not support Connection Profiles nor Connection Properties.

I reported the bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=243099 regarding the lack of support for Connection Profiles but on seeing that there was no support for Connection Properties I thought it was best to ask the newsgroup if this is a problem or not?


Without Profiles or Properties would all my reports have to be hard coded? How would that work at deploy time?

thanks for any clarification,
John