My preferred solution would be to do this via the Scanner. The farm is a subclass of DeploymentScanner.
i.e. Telll the scanner you are adding a new url and get it to suspend its work while you deploy. This will also allow it to update its deployment/timestamp correctly so it doesn't try to redeploy. The only downside to this, is that the Scanner can monitor any URLs. You would have to matchup the file URL with the Scanner that is monitoring it. What do you do when there are no file URLs being monitored, e.g. netboot? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851814#3851814 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851814 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
