On 04/07/2011 03:25 PM, Jason T. Greene wrote:
The big things we are missing are:
1. A segregated area for user provided modules
2. A distribution mechanism for them
I was wondering if we would every reach a time where an installation
could be made with just enough modules to get the host controller and
slave domain controller up and running with all remaining modules pulled
from the master domain controller if they are missing and required.
Could also make adding new capabilities like ESB or Portal to existing
installations easier if they only need adding to the master domain
controller.
Right now deployments are the only thing we have that's
distributed.
Even though we have really good EE deployment classloading capabilities,
I think we want to encourage modular development. It will lead to less
space and simpler packaging.
On 4/7/11 9:09 AM, Andrig Miller wrote:
> So, I have a question about modules.
>
> 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.
>
> Andy
>
> ----- Original Message -----
>> From: "Heiko Braun"<hbraun(a)redhat.com>
>> To: "jboss-as7-dev(a)lists.jboss.org
Development"<jboss-as7-dev(a)lists.jboss.org>
>> Sent: Thursday, April 7, 2011 4:07:53 AM
>> Subject: [jboss-as7-dev] Datasources: Driver binaries
>> Since drives are added as modules, I assume this can not be managed
>> from the console, right?
>> Which means that we will provide means to add datasource configuration
>> baed on existing drivers configurations
>> that have to be preconfigured.
>>
>>
>> Ike
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev