Hi all, Just wondering whether there is a simple way to reset AS7 to a pristine state - as if you've just installed it... Seems like emptying deployments, removing the data and log directories and removing the deployments entries from standalone.xml get me pretty far along the way but maybe there's a quicker way? Cheers, David _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

On Nov 29, 2010, at 11:41, Kabir Khan wrote: > This is also an issue with the embedded testing (or managed/remote for that matter). If I stop a testcase in my IDE while running it, then the next time I try to run it I get a 'blah.jar is already deployed error'. In embedded that can possibly be avoided by setting an alternative path for standalone.xml and the output folder. I think Thomas might have done something to handle that in the stuff I took over, but I have been concentrating on getting the core functionality working. > > One thing I wanted to ask was to maybe keep a standalone.xml.original which is never changed? +100 (even though not just having standalone.xml.original won't cut it since you might have done edits for it since..) This behavior about actually changing the state of the XML while running is kinda annoying in some cases ;) I really would prefer if there was something like: standalone.xml + standalone-delta1.xml + standalone-delta2.xml or similar so one could see what actually are *my* input and what is done by editing/adding in a console or deployments. I know that is not trivial but then at least someway of doing includes to model something like: standalone.xml include deployments.xml ...or somehow intelligently (i.e. don't create a revision unless it really has changed) keep a "revision history" around of the files when its updated.

>> >> standalone.xml >> include deployments.xml >> >> ...or somehow intelligently (i.e. don't create a revision unless it really has changed) keep a "revision history" around of the files when its updated. > > > Another issue is that the original xml contains some nice comments about for example how to set up a datasource. Once the server model changes, those comments are gone Yes, we discussed that at length at Devoxx too ;) The suggested solution is simply to at least retain the comments "nearest" an element so it can be printed out together when dumping the model. Hope that will make it in too.

On 11/29/10 4:41 AM, Kabir Khan wrote: > This is also an issue with the embedded testing (or managed/remote for that matter). If I stop a testcase in my IDE while running it, then the next time I try to run it I get a 'blah.jar is already deployed error'. In embedded that can possibly be avoided by setting an alternative path for standalone.xml and the output folder. I think Thomas might have done something to handle that in the stuff I took over, but I have been concentrating on getting the core functionality working. > > One thing I wanted to ask was to maybe keep a standalone.xml.original which is never changed? We do keep the "last known good" copy around, which basically is the original, unless of course you do multiple changes. We had also talke about keeping more copies around longer on the DC.