I've been messing around with JDBCCacheLoader and I have realised that we don't
currently have a unit test that can test the JDBCCacheLoader inside an AS. Ok, we have
JDBCCacheLoaderTest that can work based on the cache-jdbc.properties and you could start
AS manually and test it.
This however is a manual process and when it comes to CC, only standalone JDBCCacheLoader
is being tested.
I think it'd be ideal to basically extend JDBCCacheLoaderTest to set it up to work
with an AS (starting it/stopping it). This would give us even more confidence and coverage
for the ManagedConnectionFactory area. I might not have time to do that before I commit my
current work for BETA1 but definitely something worth bearing in mind.
Another question would be of course, what AS version would be integrate against?
There're various projects out there that have done something similar, first obviously
AS itself and second messaging. What's your experience with this? What have we learnt
about it? Shall we reuse some code for this? We would need a very limited AS version
actually with JNDI, JDBC Connection Pooling, HS and HS driver.
As you can see, this opens ups whole bunch of questions. Thoughts? Opinions? Critics?
Cheers,
Galder ZamarreƱo
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat
IT executives: Red Hat still #1 for value
http://www.redhat.com/promo/vendor/