[jboss-as7-dev] <deployments> section in standalone.xml

[Darran Lofthouse]

To actually change configurations I have wondered for a little while if 
we wouldn't be better to have scripts to enable the additional 
capabilities rather than completely different config i.e. some form of 
enable-ha script that is applied to the default config rather than a 
completely independent config.

Regards,
Darran Lofthouse.


On 03/14/2012 02:31 PM, Brian Stansberry wrote:
> 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.
>
> 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.
>
> On 3/14/12 3:39 AM, Heiko W.Rupp wrote:
>>
>> Am 14.03.2012 um 09:32 schrieb Emanuel Muckenhuber:
>>
>>> Yes, that is correct. Deployments added through the deployment-scanner
>>> are not persisted, however they are still added to the runtime using a
>>> special flag.
>>
>> I think this is an issue of inconsistency - if a user has stuff deployed (via api)  and wants to turn
>> the standalone server into a HA node, he can't do that by just restarting with -c standalone-ha.xml,
>> while this is (somewhat) possible with stuff deployed by copying it to the deployments directory.
>>
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
>