Index: j2eeserver/apichanges.xml =================================================================== RCS file: /cvs/j2eeserver/apichanges.xml,v retrieving revision 1.16.6.3 retrieving revision 1.16.6.3.10.1 diff -c -r1.16.6.3 -r1.16.6.3.10.1 *** j2eeserver/apichanges.xml 2 Nov 2005 03:09:05 -0000 1.16.6.3 --- j2eeserver/apichanges.xml 17 Mar 2006 16:12:09 -0000 1.16.6.3.10.1 *************** *** 80,85 **** --- 80,107 ---- + + + DS management API allows clients to access and manipulate the data sources + + + + + +

+ DS management API allows clients to access and manipulate the data sources. + Data sources are created in the module and deployed when the module deployment begins. + Data sources are accessed at two places - at the modules where they are stored after creation + and on the module's target server. +

+
+ + + + + + +
Index: j2eeserver/arch.xml =================================================================== RCS file: /cvs/j2eeserver/arch.xml,v retrieving revision 1.11.10.3.2.1 retrieving revision 1.11.10.3.2.1.6.1 diff -c -r1.11.10.3.2.1 -r1.11.10.3.2.1.6.1 *** j2eeserver/arch.xml 9 Feb 2006 12:57:23 -0000 1.11.10.3.2.1 --- j2eeserver/arch.xml 17 Mar 2006 16:12:08 -0000 1.11.10.3.2.1.6.1 *************** *** 238,243 **** --- 238,291 ----

Not supported in current version.

+ +

+ Data sources created in the module and deployed on the server are accessed using + J2eeModuleProvider methods. + Some of the module's data source may be already also deployed on the server, in that case the client + is responsible for the duplicity handling. +

+

+ Retrieval from a server is done by a server plugin. Core part of the functionality is done by + DatasourceManager implementation + which is exposed from a server plugin through + OptionalDeploymentManagerFactory. +

+

+ Retrieval from a module is done with help of + ConfigSupport and + ConfigurationSupport implementations. +

+
+ + +

+ Data sources are created in a module if they does not exist yet on a server or in a module itself. + Data sources are stored in the server-specific format, only some common subset of attributes + (e.g. JNDI name, username, url, ...) is provided by a creator.
+

+

+ Data source creation is done with help of + ConfigSupport and + ConfigurationSupport implementations. + In case of conflict with existing data source, the first conflicting data source is passed to the thrown + DatasourceAlreadyExistsException. +

+
+ + +

+ Data sources stored in a module are deployed (registered) on a module's target server at the beginning + of a module deployment.
+

+

+ Data sources stored in a module are retrived and passed to a + DatasourceManager instance + for deploying (registering) on the server.
+ All module data sources having a conflict with some existing server data source are passed to the thrown + DatasourceAlreadyExistsException. +

+