Chris Holmes ha scritto: > One other thought is to have the driver class name and url's filled out > as defaults in the factory. In an app like uDig they can just be part > of the 'advanced' tab. For GeoServer a user would get default values, > and they wouldn't know what they do, so they'd just leave them in. That > might not be so bad, and could be better than making them pick one of > two datastores. And we could perhaps figure out some sort of 'advanced' > tab when we get a new ui.
The DataSource factory is separate from the DataStore one, sorry, so it's not possible to have such defaults. DBCPDataSourceFactory can build connection pool for _every_ database. That's why I suggested to have both factories, the easy one, few parameters, stuck on DBCP, and the advanced one, where you have a combo (in the Geoserver UI, I mean) that lets you choose which DataSourceFactory will build the connection pool, and there you go with no hints whatsoever, but you can configure the pool to your heart desire. Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
