If someone wanted to work up a proposal to address these things, that would be fine. A couple things it would need to address: 1) Semantics in a managed domain. 2) The API to interact with jboss-modules to identify where to store the modules (and perhaps to delegate storage to jboss-modules). The AS shouldn't make assumptions about module loading; anything it does should be based on a clear contract with jboss-modules. For the managed domain stuff, a simple step is to scope the management operations to an individual host (e.g. /host=foo:add-configuration-file) and not try to deal on the server side with pushing out content to multiple hosts On 5/21/13 7:25 AM, Ondrej Zizka wrote: > Hi all, > > for the purpose of migration, it would be nice to have a possibility to > upload certain files. Namely: > - create modules (e.g. JDBC drivers) > - copy .properties files - logging, security etc. > - ssh keys, certificates etc. > > Is there a chance to have this in Wildfly mgmt API? > It could be limited to the examples above - i.e. one op for > creating/removing a module, one op for copying a file to configuration/ . > > Thanks, > Ondra > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev >