Alexey Loubyansky [
http://community.jboss.org/people/alex.loubyansky%40jboss.com] created
the discussion
"Re: XML File Deployments"
To view the discussion, visit:
http://community.jboss.org/message/560479#560479
--------------------------------------------------------------
David Lloyd wrote:
> Alexey Loubyansky wrote:
>
> The reason why it is convenient is that when you have a common library which is
stable (or mostly stable and if it needs an update then all the services based on it need
the update) and want to configure multiple services (i.e. create multiple instances) with
different configuration.
> So if you bundle the library with each deployment then:
> - to modify the config you need to repackage;
> - to upgrade the common library you'll need to repackage all the deployments
including it.
Do you have some more specific examples? I don't see how this justifies single-file
deployments. It seems that at most this implies the need for deployment descriptor types
(inside an archive) to override settings.
If you have a library of classes that can
be used to create a set of services, JMX beans, other managed beans, EJBs, etc, this
library can be put into the servers classpath and then by deploying just deployment
descriptors you can create new services, managed beans, EJBs, etc.
This feature was added previously to avoid creating JARs that contain only service XML
files. Plus, with hot deploy tracking the file modifications it's like WYSIWYG editor
(after the save of course).
--------------------------------------------------------------
Reply to this message by going to Community
[
http://community.jboss.org/message/560479#560479]
Start a new discussion in JBoss AS7 Development at Community
[
http://community.jboss.org/choose-container!input.jspa?contentType=1&...]