Charlie Poole
2008-04-07 01:19:48 UTC
Hi All,
I should mention that DataSourceAttribute is a placeholder.
I don't really like it because of the association with
ADO.Net data sources in MsTest - and we may want to
implement that at some point.
There are two ways to go with these data provider attributes:
1) Have one attribute and overload it with different arg types
2) Have an attribute for each type of source.
Given the limitations of attribute constructor arguments,
I lean toward #2. So what should an attribute that gets
data out of static properties be called? PropertyData?
As sample of what I see coming, we may want to pull
data out of Xml files, Tables, databases, arrays,
JSON files, etc.
Charlie
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
I should mention that DataSourceAttribute is a placeholder.
I don't really like it because of the association with
ADO.Net data sources in MsTest - and we may want to
implement that at some point.
There are two ways to go with these data provider attributes:
1) Have one attribute and overload it with different arg types
2) Have an attribute for each type of source.
Given the limitations of attribute constructor arguments,
I lean toward #2. So what should an attribute that gets
data out of static properties be called? PropertyData?
As sample of what I see coming, we may want to pull
data out of Xml files, Tables, databases, arrays,
JSON files, etc.
Charlie
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone