5:07 a.m.
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
5:32 a.m.
Drivers can be added as deployments, too, see:
http://community.jboss.org/wiki/DataSourceConfigurationinAS7
On 07/04/2011 13:07, Heiko Braun wrote:
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
6:20 a.m.
thanks dimitris.
will this be turned into an official reference (aka user guide) soon?
On Apr 7, 2011, at 12:32 PM, Dimitris Andreadis wrote:
Drivers can be added as deployments, too, see:
http://community.jboss.org/wiki/DataSourceConfigurationinAS7
On 07/04/2011 13:07, Heiko Braun wrote:
>
>
> 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
6:24 a.m.
It should, we need to find the cycles for it, though.
On 07/04/2011 14:20, Heiko Braun wrote:
thanks dimitris.
will this be turned into an official reference (aka user guide) soon?
On Apr 7, 2011, at 12:32 PM, Dimitris Andreadis wrote:
> Drivers can be added as deployments, too, see:
> http://community.jboss.org/wiki/DataSourceConfigurationinAS7
>
> On 07/04/2011 13:07, Heiko Braun wrote:
>>
>>
>> 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
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Software Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://dandreadis.blogspot.com/
6:26 a.m.
we could begin by tagging all relevant wiki articles with #jboss_7_userguide
On Apr 7, 2011, at 1:24 PM, Dimitris Andreadis wrote:
It should, we need to find the cycles for it, though.
On 07/04/2011 14:20, Heiko Braun wrote:
> thanks dimitris.
> will this be turned into an official reference (aka user guide) soon?
>
>
> On Apr 7, 2011, at 12:32 PM, Dimitris Andreadis wrote:
>
>> Drivers can be added as deployments, too, see:
>> http://community.jboss.org/wiki/DataSourceConfigurationinAS7
>>
>> On 07/04/2011 13:07, Heiko Braun wrote:
>>>
>>>
>>> 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
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Software Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://dandreadis.blogspot.com/
6:27 a.m.
good idea.
On 07/04/2011 14:26, Heiko Braun wrote:
we could begin by tagging all relevant wiki articles with #jboss_7_userguide
On Apr 7, 2011, at 1:24 PM, Dimitris Andreadis wrote:
> It should, we need to find the cycles for it, though.
>
> On 07/04/2011 14:20, Heiko Braun wrote:
>> thanks dimitris.
>> will this be turned into an official reference (aka user guide) soon?
>>
>>
>> On Apr 7, 2011, at 12:32 PM, Dimitris Andreadis wrote:
>>
>>> Drivers can be added as deployments, too, see:
>>> http://community.jboss.org/wiki/DataSourceConfigurationinAS7
>>>
>>> On 07/04/2011 13:07, Heiko Braun wrote:
>>>>
>>>>
>>>> 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
>>
>
> --
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Dimitris Andreadis
> Software Engineering Manager
> JBoss Application Server
> by Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> http://dandreadis.blogspot.com/
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Software Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://dandreadis.blogspot.com/
6:39 a.m.
Aren't we going to use confluence
Dimitris can u sync up with Mark Newton, I lost track.
Cheers,
--
Bruno Georges
On Apr 7, 2011, at 19:27, Dimitris Andreadis <dandread(a)redhat.com> wrote:
good idea.
On 07/04/2011 14:26, Heiko Braun wrote:
>
>
> we could begin by tagging all relevant wiki articles with #jboss_7_userguide
>
>
> On Apr 7, 2011, at 1:24 PM, Dimitris Andreadis wrote:
>
>> It should, we need to find the cycles for it, though.
>>
>> On 07/04/2011 14:20, Heiko Braun wrote:
>>> thanks dimitris.
>>> will this be turned into an official reference (aka user guide) soon?
>>>
>>>
>>> On Apr 7, 2011, at 12:32 PM, Dimitris Andreadis wrote:
>>>
>>>> Drivers can be added as deployments, too, see:
>>>> http://community.jboss.org/wiki/DataSourceConfigurationinAS7
>>>>
>>>> On 07/04/2011 13:07, Heiko Braun wrote:
>>>>>
>>>>>
>>>>> 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
>>>
>>
>> --
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Dimitris Andreadis
>> Software Engineering Manager
>> JBoss Application Server
>> by Red Hat
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>
>> http://dandreadis.blogspot.com/
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Software Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
http://dandreadis.blogspot.com/
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
8:32 a.m.
Yes, so at some point we need to organize/port stuff over there.
On 4/7/11 6:39 AM, Bruno Georges wrote:
Aren't we going to use confluence
Dimitris can u sync up with Mark Newton, I lost track.
Cheers,
--
Bruno Georges
On Apr 7, 2011, at 19:27, Dimitris Andreadis<dandread(a)redhat.com> wrote:
> good idea.
>
> On 07/04/2011 14:26, Heiko Braun wrote:
>>
>>
>> we could begin by tagging all relevant wiki articles with #jboss_7_userguide
>>
>>
>> On Apr 7, 2011, at 1:24 PM, Dimitris Andreadis wrote:
>>
>>> It should, we need to find the cycles for it, though.
>>>
>>> On 07/04/2011 14:20, Heiko Braun wrote:
>>>> thanks dimitris.
>>>> will this be turned into an official reference (aka user guide) soon?
>>>>
>>>>
>>>> On Apr 7, 2011, at 12:32 PM, Dimitris Andreadis wrote:
>>>>
>>>>> Drivers can be added as deployments, too, see:
>>>>> http://community.jboss.org/wiki/DataSourceConfigurationinAS7
>>>>>
>>>>> On 07/04/2011 13:07, Heiko Braun wrote:
>>>>>>
>>>>>>
>>>>>> 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
>>>>
>>>
>>> --
>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>> Dimitris Andreadis
>>> Software Engineering Manager
>>> JBoss Application Server
>>> by Red Hat
>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> http://dandreadis.blogspot.com/
>>
>
> --
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Dimitris Andreadis
> Software Engineering Manager
> JBoss Application Server
> by Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> http://dandreadis.blogspot.com/
> _______________________________________________
> 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
--
Jason T. Greene
JBoss, a division of Red Hat
8:40 a.m.
yes, the tagging only acts as an interim solution
On Apr 7, 2011, at 3:32 PM, Jason T. Greene wrote:
Yes, so at some point we need to organize/port stuff over there.
On 4/7/11 6:39 AM, Bruno Georges wrote:
> Aren't we going to use confluence
> Dimitris can u sync up with Mark Newton, I lost track.
> Cheers,
>
> --
> Bruno Georges
>
> On Apr 7, 2011, at 19:27, Dimitris Andreadis<dandread(a)redhat.com> wrote:
>
>> good idea.
>>
>> On 07/04/2011 14:26, Heiko Braun wrote:
>>>
>>>
>>> we could begin by tagging all relevant wiki articles with #jboss_7_userguide
>>>
>>>
>>> On Apr 7, 2011, at 1:24 PM, Dimitris Andreadis wrote:
>>>
>>>> It should, we need to find the cycles for it, though.
>>>>
>>>> On 07/04/2011 14:20, Heiko Braun wrote:
>>>>> thanks dimitris.
>>>>> will this be turned into an official reference (aka user guide)
soon?
>>>>>
>>>>>
>>>>> On Apr 7, 2011, at 12:32 PM, Dimitris Andreadis wrote:
>>>>>
>>>>>> Drivers can be added as deployments, too, see:
>>>>>> http://community.jboss.org/wiki/DataSourceConfigurationinAS7
>>>>>>
>>>>>> On 07/04/2011 13:07, Heiko Braun wrote:
>>>>>>>
>>>>>>>
>>>>>>> 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
>>>>>
>>>>
>>>> --
>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>> Dimitris Andreadis
>>>> Software Engineering Manager
>>>> JBoss Application Server
>>>> by Red Hat
>>>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>>>
>>>> http://dandreadis.blogspot.com/
>>>
>>
>> --
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Dimitris Andreadis
>> Software Engineering Manager
>> JBoss Application Server
>> by Red Hat
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>
>> http://dandreadis.blogspot.com/
>> _______________________________________________
>> 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
--
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
9:09 a.m.
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
9:16 a.m.
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.
12:58 p.m.
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
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
1:19 p.m.
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
--
Jason T. Greene
JBoss, a division of Red Hat
1:27 p.m.
On 4/7/11 1:19 PM, Jason T. Greene wrote:
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.
Agreed. That's why I responded on this branch of the thread, where the
deployment notion got raised.
We also need to be clear about what's being looked for when; i.e.
required for AS 7.0 vs some later release.
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
>
>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
9:25 a.m.
The big things we are missing are:
1. A segregated area for user provided modules
2. A distribution mechanism for them
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
--
Jason T. Greene
JBoss, a division of Red Hat
9:33 a.m.
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
10:25 a.m.
----- Original Message -----
From: "Jason T. Greene" <jason.greene(a)redhat.com>
To: jboss-as7-dev(a)lists.jboss.org
Sent: Thursday, April 7, 2011 8:25:35 AM
Subject: Re: [jboss-as7-dev] Datasources: Driver binaries
The big things we are missing are:
1. A segregated area for user provided modules
2. A distribution mechanism for them
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.
Also, when you think about EAP packaging, and wanted to push more things into WFK, like
Seam 3 and Hibernate even, we need to be able to have separate installation of modules for
that to.
Andy
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
--
Jason T. Greene
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
5010
days inactive
5010
days old
16 comments
7 participants
participants (7)
-
Andrig Miller -
Brian Stansberry -
Bruno Georges -
Darran Lofthouse -
Dimitris Andreadis -
Heiko Braun -
Jason T. Greene