Ole Husgaard wrote:
> Hi,
>
> Don't know if this is useful, but
> here goes my $.02:
>
[snip]
>
> So the .RAR needs to be deployed because
> a backward-compatibility feature in
> Minerva needs it?
No. The RARs need to be deployed in order to access JDBC datasources
using either the backward-compatible *DataSourceLoader or the new
ConnectionFactoryLoader.
> If this is the case, couldn't the
> initialization of the backward-
> compatibility feature in Minerva just
> ask the deployer to deploy it?
That's definitely a possibility - include the RARs in the minerva.jar
and pass the deployer a jar: URL.
> 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.
I think we're going to be using dist/deploy/lib - makes little
difference to me either way.
Toby.
