[jboss-as7-dev] <deployments> section in standalone.xml
Brian Stansberry
brian.stansberry at redhat.com
Thu Mar 15 17:17:53 EDT 2012
On 3/14/12 10:26 AM, Heiko W.Rupp wrote:
>
> Am 14.03.2012 um 15:31 schrieb Brian Stansberry:
>
>> If a user has added a datasource or a jms destination or a log category
>> or... via api and wants to turn the standalone server into an HA node,
>> he can't do that by just restarting with -c standalone-ha.xml.
>>
> It looks like this works for deployed apps if you put them into the deployment
> folder. So if you put a -ds.xml into the deployment folder it should work too(?)
> and perhaps other *.xml files that come up over time.
>
> So clearly this looks much better than the api that requires re-deploy when
> switching configs
>
Yes, it's the same for -ds.xml or whatever else.
To be more specific, if you install a datasource via a -ds.xml file, no
matter how you do it, scanner, web console, CLI, whatever, the contents
of the <xmlns="urn:jboss:domain:datasources:1.0"> section of the config
are unchanged. Same with JMS destinations and the messaging subsystem.
>
>> I don't see how we could meaningfully support having users change a
>> config and then having those changes auto-magically show up in a
>> completely different config. Perhaps someday tooling around this could
>> be created.
>
> Well, yeah ...
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
More information about the jboss-as7-dev
mailing list