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 don't see the problem, if the node is restarted with '-c standalone-ha.xml' the all deployments of the directory are picked-up

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.

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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Nice idea, but I think it will be difficult to keep all XML and scripts up-to-date and in sync :( As Heiko mentioned before if deploy is done by CLI/console the deployment is gone if I change from sa.xml to sa-full.xml or even host.xml to host-xy.xml. But I think the different configs are only a template to start and never used after a server is installed. So a cli based script to add some functionality, e.g. HA, HornetQ) might be helpful for customers or even support. On 03/15/2012 01:38 PM, Darran Lofthouse wrote: > 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(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 -- Red Hat GmbH Technopark II, Building 1 Werner-von-Siemens-Ring 11-15 85630 Grasbrunn Germany Email: wfink(a)redhat.com ________________________________________________________________________ Handelsregister: Amtsgericht Muenchen HRB 153243 Geschaeftsfuehrer: Mark Hegarty, Charlie Peters, Michael Cunningham, Charles Cachera _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Am 15.03.2012 um 16:02 schrieb Sebastian Otaegui: > How about adding (if it does not already exist) "shortcuts for common simple tasks" in the CLI? That should not only be supported in the cli, as the management api is open for whatever client. If that is only implemented in the cli and you want to write some ruby code to access the api, you need to re-implement it