Larry pretty much has it right.  The DataSource concept was introduced 
when we started to think about lining up the I/O design more with JDBC, 
and allowing for data stores with more than one dataset in them.  
Ultimately I think we abandoned this direction, and moved on with 
DataStores instead.  I think we introduced a new DataStore concept 
because we were worried that we would break DataSource if we went back 
and tried to change it,

Really this whole framework should be rationalized a bit better.  
Perhaps DataSource should be absorbed into DataStore? 

The concept of Readers and Writers is still valid, though, I think - 
they are the "nuts and bolts" of actually reading/writing a particular 
format.  How they are exposed to JUMP can vary, however.

Larry Becker wrote:
> Christopher,
>
>   I can only repeat what is in the developer's guide, which I'm sure 
> you have already seen:
>
> "A DataSource is an object that mediates to move data between the 
> Workbench and a file or
> other data source; it will replace the Readers/Writers found in 
> earlier versions of JUMP.
> Similarly, DataSourceQueryChooser replaces the now-deprecated Driver. 
> These are the UI
> panels associated with a DataSource. Note: Reader and Writer are have 
> not been
> deprecated in JUMP 1.1, because there is no plan to re-write the 
> existing Readers/Writers
> in the near future."
>
> It would appear that this was an idea that was evolving when the JUMP 
> project was suspended.
>
> regards,
> Larry Becker
>
> On Mon, Jun 9, 2008 at 9:48 AM, Christopher <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>     That seems to be the way most of the data input output
>     is done. I'm just wondering why the whole datasource
>     bit came about if it only winds up being a wrapper for
>     JUMPReader & JUMPWriter.
>
>     Thank  you for the feedback,
>     --Christopher
>
>     --- Paul Austin <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>> wrote:
>
>     > Christopher,
>     >
>     > The easiest way is to use the
>     >
>     com.vividsolutions.jump.io.datasource.StandardReaderWriterDataSource
>     > to
>     > just wrap a JUMp Reader and Jump Writer.
>     >
>     > If you then register it using
>     > InstallStandardDataSourceQueryChoosersPlugIn it will
>     > show up in the
>     > Open/Save dialogs.
>     >
>     > Paul
>     >
>
>
>
>
>
>     -------------------------------------------------------------------------
>     Check out the new SourceForge.net Marketplace.
>     It's the best place to buy or sell services for
>     just about anything Open Source.
>     http://sourceforge.net/services/buy/index.php
>     _______________________________________________
>     Jump-pilot-devel mailing list
>     Jump-pilot-devel@lists.sourceforge.net
>     <mailto:Jump-pilot-devel@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
>
>
>
> -- 
> http://amusingprogrammer.blogspot.com/
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> ------------------------------------------------------------------------
>
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>   

-- 
Martin Davis
Senior Technical Architect
Refractions Research, Inc.
(250) 383-3022


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to