aspose file tools*
The moose likes JBoss/WildFly and the fly likes the deploy directory constant scanning and re-deployment mechanism ? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "the deploy directory constant scanning and re-deployment mechanism ?" Watch "the deploy directory constant scanning and re-deployment mechanism ?" New topic
Author

the deploy directory constant scanning and re-deployment mechanism ?

Myke Enriq
Ranch Hand

Joined: Feb 13, 2012
Posts: 115
I quote form the Jboss documentation: "You deploy your application code by placing application packages (JAR, WAR and EAR files) in the deploy directory. The directory is constantly scanned for updates, and any modified components will be re-deployed automatically."

How is this constant scanning mechanism implemented ? Could you point me to some (maybe visual) documentation ?
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5845
    
    7

There is a separate thread that wakes up on a timer and uses plain-old-IO to scan the deploy directory. This is governed by the hdscanner-jboss-beans.xml file (in JBoss AS 5.1.0)


JBoss In Action
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: the deploy directory constant scanning and re-deployment mechanism ?