Hi,
Don't know if this is useful, but
here goes my $.02:
Aaron Mulder wrote:
> So, now it appears that the current JBoss connection pool loaders
> are obsolete: if the new spec-compliant way to access data is via J2EE
> Connectors, and we have a Connector implementation for databases, why
> would you want to use XADataSourceLoader instead? But rather than
> removing it, for backward compatibility, we can just make
> XADataSourceLoader and JDBCDataSourceLoader do all their work via
> Connectors under the covers.
> Which brings me to the question in my message. Since RARs can be
> deployed into a server like JARs and WARs, it seems like they ought to go
> in dist/deploy. But if we update the xxxDataSourceLoader classes to
> behave as I just outlined, they will depend on the Minerva .RARs being
> available. And so dist/deploy isn't necessarily the best place for those.
So the .RAR needs to be deployed because
a backward-compatibility feature in
Minerva needs it?
If this is the case, couldn't the
initialization of the backward-
compatibility feature in Minerva just
ask the deployer to deploy it?
Anyway, a dist/lib/deploy could be
a good idea for "static" deployments,
ie. stuff that is to be deployed at
JBoss startup (before any auto-deploy),
and never needs re-deployment or
un-deployment.
Best Regards,
Ole Husgaard.
