Hey,
> I'm going to go ahead and use dist/lib/deploy unless someone dissents.
personally I'd prefer dist/deploy/lib.
This way under dist/lib (and subdirs) -> "static" jars,
while under dist/deploy (and subdirs) -> "deployable" jars, being them EJB
jars, EARs, or RARs.
Just my $0.02
Simon
>
> Toby.
>
> Dan Christopherson wrote:
>
> > Resource Adapters really aren't application components (as
> the autonumber
> > thing was). That said, they're not really components of the
> container or
> > the server either.
> > My vote would be to have an extra autodeployed directory, for any
> > 'deployed plugin' type of component.
> >
> > On Fri, 9 Feb 2001, Toby Allsopp wrote:
> >
> >
> >> This is perhaps a more general issue of how we should
> bundle application
> >> components with JBoss.
> >>
> >> At the moment, the only bundled component that I'm aware of is the
> >> AutoNumber EJB, and I seem to recall Rickard being unhappy at its
> >> appearance.
> >>
> >> The Minerva resource adapters are more fundamental to a basic JBoss
> >> installation than a primary key generator, however. Without them it
> >> isn't going to be possible to access JDBC resources by default.
> >>
> >> An option would be to put them in a directory, say
> dist/lib/connectors,
> >> that is not autodeployed but have them explicitly deployed
> by an MBean.
> >>
> >> Another option is to add an extra autodeployed directory, say
> >> dist/lib/deploy, for bundled application components.
> >>
> >> Toby.
> >>
> >> Aaron Mulder wrote:
> >>
> >>> After the most recent updates, you can use the
> JBossCX connector
> >>> module with the Minerva .RARs for JDBC and JDBC/XA
> support. However, I'm
> >>> not sure where the .RARs should go in CVS and in the dist
> directory. I
> >>> suppose they should ultimately end up in dist/deploy so
> they are deployed
> >>> when the server is started. So how about putting them in
> src/connectors
> >>> and then altering the build to dump them in dist/deploy?
> >>> The only issue is that we'll alter the
> xxxDataSourceLoaders to use
> >>> connectors under the covers, and when we do the Minerva
> .RARs will be
> >>> required for basic server operation. So it's a little
> misleading to
> >>> put them in dist/deploy, which looks like a directory for
> "user data".
> >>> Any other suggestions?
> >>>
> >>> Aaron
>
>
