I have tested this alot with my last app I was developing and
here is what I found.
The one file that does affect tomcat, (thus forcing a tomcat
restart), is the services-config.xml file.
If you edit the line:
<channel-definition id="my-amf"
class="mx.messaging.channels.AMFChannel">
<endpoint uri="
http://{server.name}:{server.port}/{context.root}/messagebroker/amf"class="flex.messaging.endpoints.AMFEndpoint"/>
<properties>
<polling-enabled>false</polling-enabled>
</properties>
</channel-definition>
And remove the {context.root} section, then yes you will need
to restart tomcat to get it to reload this change.
The other docs, such as the remoting-config.xml do not need
to have tomcat reloaded in order for them to get reloaded.
The only caviat to this is that if you make changes to the
files and such, you may need to clean and rebuild your eclipse
projects in order for those changes to be reloaded. If you do not,
the eclipse project might continue to use the old variable
definitions you have in the app. So remember to clean and rebuild
frequently if you are having problems and need to edit these files.
Jeremy Sanders
jsanders@cardinalsolutions.com