Adrian, thank you for bearing with me. I believe you that the test you mention 
will fail, when you run it twice. I was being overly optimistic based on 
limiting testing using mysql drivers:

-I could deploy a datasource with driverA, delete the deployment, redeploy the 
exact same deployment and the datasource worked as expected.
-I could deploy a datasource with driverA, delete the deployment, redeploy the 
exact same deployment except use driverB and the datasource worked as expected: 
using driverA until the server was restarted when it would work using driverB.

The above held true whether I was using the "wrapped approach" of putting the 
-ds.xml and driver in .sar or the "split approach" having a -service.xml with a 
classpath entry and the driver jar stored separately. The unit test you mention 
demonstrates this does not hold true in the general case. 

I think the crux of my misunderstanding was based around the meaning of driver 
hot redeploy "not working". When I saw that statement, I thought it agreed with 
my results i.e. "The datasource will continue to function but that any driver 
change will not get picked up until the server is restarted", when the case is 
actually "in general as soon as you redeploy the the driver, the datasource 
will be broken (e.g. throw exceptions) until the server is restarted". The 
former is in my mind is a whole lot more acceptable than the latter.

I then ran another test:
deploy a datasource with a bad password, delete the deployment, redeploy the 
exact same deployment except with the correct password.

1) When using the "wrapped approach" the datasource behaved as expected. At the 
end of the test, after the redeploy, the datasource threw a NPE. After 
restarting the server the datasource worked fine.
2) When using the "split approach" and putting the driver jar in 
.default/data/datasources/ the same results as in 1) were experienced.
3) When using the "split approach" and putting the driver jar in 
.default/deploy/datasources/ no exceptions were thrown and at the end of the 
test a connection to the database could be obtained.

Is result 3) useful, or should I just stop banging my head against this 
particular wall?



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

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


-------------------------------------------------------
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