schema.jboss-as-deployment-scanner_1_1.xsd Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of wildfly-deployment-scanner Show documentation

There is a newer version: 27.0.0.Final

Show newest version





    
    

    
        
            
                
            
        
        
            
        
    

    
        
            Allows configuration of an additional location where deployment
                content can be stored.
            
        
        
        
            
                The actual filesystem path. Treated as an absolute path, unless the
                'relative-to' attribute is specified, in which case the value
                is treated as relative to that path.
                
            
        
        
           
                Reference to a filesystem path defined in the "paths" section
                of the server configuration.
                
            
        
        
            
                
                    Flag indicating that all scanning (including initial scanning at startup)
                    should be disabled.
                
            
        
        
            
                Periodic interval, in milliseconds, at which the repository
                    should be scanned for changes. A value of less than 1 indicates the
                    repository should only be scanned at initial startup.
                
            
        
        
            
                
                    Controls whether zipped deployment content should be automatically deployed by
                    the scanner without requiring the user to add a .dodeploy marker file.
                
            
        
        
            
                
                    Controls whether exploded deployment content should be automatically deployed by
                    the scanner without requiring the user to add a .dodeploy marker file. Setting
                    this to 'true' is not recommended for anything but basic development scenarios,
                    as there is no way to ensure that deployment will not occur in the middle of
                    changes to the content.
                
            
        
        
            
                
                    Controls whether xml deployment content should be automatically deployed by
                    the scanner without requiring the user to add a .dodeploy marker file.
                
            
        
        
            
                
                   Timout used, in seconds, for deployment operations.  If an individual deployment operation
                   takes longer than this timeout it will be canceled and marked as failed.