I would like to revisit an issue that was briefly mentioned in this thread 
(http://www.jboss.com/index.html?module=bb&op=viewtopic&t=58900). Namely that I 
would like to discuss adding support for the classpath element to *-ds.xml's.

The recommended datasource deployment scenario from thread above is to bundle 
everything into a .sar file with the following structure:
./deploy/mydatasource.sar/
  |             META-INF/jboss-service.xml = <?xml 
version="1.0"?><server></server>
  |             my-ds.xml
  |             mydriver.jar    

Suggested alternative:
./deploy/my-ds.xml      (including classpath element pointing to mydriver.jar)
  | ./data/datasource_drivers/mydriver.jar

I am not suggesting this as a general alternative to the .sar approach, but for 
one particular scenario, described below, I believe it has some advantages.

1) The Admin Console is going to use the DeploymentService 
(http://www.jboss.org/wiki/Wiki.jsp?page=DeploymentService) to create, update 
and delete datasources.

2) There is an advantage in having the datasource driver .jar live outside of a 
.sar file due to the way the DeploymentService works. Namely that clients of 
the DeploymentService would not have to keep a reference to the datasource 
driver .jar, in order to pass it to the DeploymentService when doing an update. 
Keeping the reference is necessary when everything is bundled into a .sar since 
there is no way to obtain from a datasource a reference to the driver it is 
using.

3) Assuming you agree with point 2) it is also a good idea for the datasource 
driver .jar to live outside of the scanned deployment directories, so that 
multiple versions of the same driver can be supported. The classpath element is 
therefore needed to associate the configuration definition of the datasource 
and the driver.jar file.

4) It is easier to create a DeploymentService template for a -ds.xml file than 
to create a -service.xml that does the same thing.


So, assuming the scenario above is taken as being sufficient reason to add 
classpath element support for ds.xml's, how hard would it actually be to 
implement?

Thanks

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863776#3863776

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863776


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to