This content has been marked as final. Show 2 replies
In the past, I've suggested being able to add plugins for all policy decisions.
<tx-connection-factory> ... <internal-pool-class>com.acme.Blah</internal-pool-class> </tx-connection-factory>
But the difficulty comes in matching this up to the configuration of that plugin.
With the Micrcontainer (ease of use configuration)
and the more up-to-date JBossXB schema implementation it is much easier
to mix and match configuration in a well defined way.
<deployment> <tx-connection-factory> ... <internal-pool> <pool xmlns="urn:com.acme:Pool:1.0"> <some-config-option>123</some-config-option> </pool> </internal-pool> ... </tx-connection-factory> </deployment>
With JBossXB injecting the object (preferably Micrcontainer metadata)
created through the pool schema into the internal-pool part of the standard
If there is no such element, it would just use the default.