On Sat, 10 Feb 2001, Ole Husgaard wrote:
> 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?
It's actually a backward-compatibility feature of JBoss: the
classes org.jboss.jdbc.JDBCDataSourceLoader and
org.jboss.jdbc.XADataSourceLoader. That's what everyone has used to
configure data sources in the past, and I figure we might as well let it
continue to work in the future. But if no one minds removing it, we can
just document a new Connector-based data source system for the next
release.
As for whether the backward-compatibility code can deploy it, the
answer is yes, but it still has to be packaged into a .RAR, and the RAR
still has to go in a standard location so that the backward-compatibility
code can find it to deploy it. And once you've gone that far, there's no
reason not to deploy it using some sort of automatic deployment mechanism.
So I think the suggestion for a static deployment directory is a good one.
Aaron
> 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.
>
