Re: [jboss-as7-dev] Datasources: Driver binaries

We do this for OSGi bundles, but in that case they have a well defined service lifecycle, so they are certainly more like a deployment. In AS7, a deployment can pretty much do all of the same things that a module can do (provided it provides a classloading descriptor). The difference as you mention is that it's lifecycle is dynamic. I was more referring to a mechanism to distribute static modules, which do not need DUPs to be ran on them. I think we really need to think carefully about what capabilities we are looking for.

On 4/7/11 12:58 PM, Brian Stansberry wrote: > Is that how we'd want to handle modules? > > Deployment encompasses content distribution, plus a particular way of > getting services installed in the runtime. I don't think we should mix > the two unless it's really what we want. Better IMHO to have a separate > distribution mechanism and associated operations for managing modules. > > David can better comment whether I'm all wet; i.e. whether a deployment > unit processor that detects a module and handles it correctly is no big > deal. > > I can foresee lifecycle issues as well if modules start coming in as > deployments. I.e. subsystems that expect that modules are there and > available, not something that might appear at some point in the future > when some deployment gets processed. > > On 4/7/11 9:16 AM, Heiko Braun wrote: >> >> maybe. it might be possible if the deployment API is able to identify >> modules, >> like it does with JDBC drivers. >> >> but that's something Brian may answer. >> >> On Apr 7, 2011, at 4:09 PM, Andrig Miller wrote: >> >>> Wouldn't we be able to use the console to add and/or remove modules? >>> Seems like this should be an included piece of our management story. >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > >