Examples of FileHandler

altn8.filechooser.FileHandler
Handler for processing files in {@link AlternateFilePopupChooser}
de.axxeed.animosy.tools.FileHandler
FileHandler.java Created 27.12.2007 10:05:13 @author Markus J. Luzius
de.innovationgate.wgpublisher.lucene.analysis.FileHandler
interface for lucene filehandler implementations filehandlers are mapped to fileextensions and used by LuceneManager to extract text of fileattachments from content-documents
de.uniol.informatik.vlba.prototype.packaging.FileHandler
@author ammarThis class is responsible for communicating with other applications through reading and writing files, can be optimized using virtual RAM disk.
de.uniol.informatik.vlba.purplebee.p2p.FileHandler
@author ammarThis class is responsible for communicating with other applications through reading and writing files, can be optimized using virtual RAM disk.
eu.planets_project.ifr.core.storage.common.FileHandler
@author CFwilson
java.util.logging.FileHandler
Simple file logging Handler.
The FileHandler can either write to a specified file, or it can write to a rotating set of files.
For a rotating set of files, as each file reaches a given size limit, it is closed, rotated out, and a new file opened. Successively older files are named by adding "0", "1", "2", etc into the base filename.
By default buffering is enabled in the IO libraries but each log record is flushed out when it is complete.
By default the XMLFormatter class is used for formatting.
Configuration: By default each FileHandler is initialized using the following LogManager configuration properties. If properties are not defined (or have invalid values) then the specified default values are used.
- java.util.logging.FileHandler.level specifies the default level for the Handler (defaults to Level.ALL).
- java.util.logging.FileHandler.filter specifies the name of a Filter class to use (defaults to no Filter).
- java.util.logging.FileHandler.formatter specifies the name of a Formatter class to use (defaults to java.util.logging.XMLFormatter)
- java.util.logging.FileHandler.encoding the name of the character set encoding to use (defaults to the default platform encoding).
- java.util.logging.FileHandler.limit specifies an approximate maximum amount to write (in bytes) to any one file. If this is zero, then there is no limit. (Defaults to no limit).
- java.util.logging.FileHandler.count specifies how many output files to cycle through (defaults to 1).
- java.util.logging.FileHandler.pattern specifies a pattern for generating the output file name. See below for details. (Defaults to "%h/java%u.log").
- java.util.logging.FileHandler.append specifies whether the FileHandler should append onto any existing files (defaults to false).
A pattern consists of a string that includes the following special components that will be replaced at runtime:
- "/" the local pathname separator
- "%t" the system temporary directory
- "%h" the value of the "user.home" system property
- "%g" the generation number to distinguish rotated logs
- "%u" a unique number to resolve conflicts
- "%%" translates to a single percent sign "%"
If no "%g" field has been specified and the file count is greater than one, then the generation number will be added to the end of the generated filename, after a dot.
Thus for example a pattern of "%t/java%g.log" with a count of 2 would typically cause log files to be written on Solaris to /var/tmp/java0.log and /var/tmp/java1.log whereas on Windows 95 they would be typically written to C:\TEMP\java0.log and C:\TEMP\java1.log
Generation numbers follow the sequence 0, 1, 2, etc.
Normally the "%u" unique field is set to 0. However, if the FileHandler tries to open the filename and finds the file is currently in use by another process it will increment the unique number field and try again. This will be repeated until FileHandler finds a file name that is not currently in use. If there is a conflict and no "%u" field has been specified, it will be added at the end of the filename after a dot. (This will be after any automatically added generation number.)
Thus if three processes were all trying to log to fred%u.%g.txt then they might end up using fred0.0.txt, fred1.0.txt, fred2.0.txt as the first file in their rotating sequences.
Note that the use of unique ids to avoid conflicts is only guaranteed to work reliably when using a local disk file system. @version 1.36, 04/07/06 @since 1.4
net.sourceforge.marathon.util.FileHandler
org.apache.commons.configuration.io.FileHandler
A class that manages persistence of an associated {@link FileBased} object.

Instances of this class can be used to load and save arbitrary objects implementing the {@code FileBased} interface in a convenient way from and tovarious locations. At construction time the {@code FileBased} object tomanage is passed in. Basically, this object is assigned a location from which it is loaded and to which it can be saved. The following possibilities exist to specify such a location:
- URLs: With the method {@code setURL()} a full URL to the configurationsource can be specified. This is the most flexible way. Note that the {@code save()} methods support only file: URLs.
- Files: The {@code setFile()} method allows to specify the configurationsource as a file. This can be either a relative or an absolute file. In the former case the file is resolved based on the current directory.
- As file paths in string form: With the {@code setPath()} method a fullpath to a configuration file can be provided as a string.
- Separated as base path and file name: The base path is a string defining either a local directory or a URL. It can be set using the {@code setBasePath()} method. The file name, non surprisingly, defines thename of the configuration file.
An instance stores a location. The {@code load()} and {@code save()} methodsthat do not take an argument make use of this internal location. Alternatively, it is also possible to use overloaded variants of {@code load()} and {@code save()} which expect a location. In these cases thelocation specified takes precedence over the internal one; the internal location is not changed.

The actual position of the file to be loaded is determined by a {@link FileLocationStrategy} based on the location information that has beenprovided. By providing a custom location strategy the algorithm for searching files can be adapted. Save operations require more explicit information. They cannot rely on a location strategy because the file to be written may not yet exist. So there may be some differences in the way location information is interpreted by load and save operations. In order to avoid this, the following approach is recommended:
- Use the desired {@code setXXX()} methods to define the location of thefile to be loaded.
- Call the {@code locate()} method. This method resolves the referencedfile (if possible) and fills out all supported location information.
- Later on, {@code save()} can be called. This method now has sufficientinformation to store the file at the correct location.
When loading or saving a {@code FileBased} object some additionalfunctionality is performed if the object implements one of the following interfaces:
- {@code FileLocatorAware}: In this case an object with the current file location is injected before the load or save operation is executed. This is useful for {@code FileBased} objects that depend on their current location,e.g. to resolve relative path names.
- {@code SynchronizerSupport}: If this interface is implemented, load and save operations obtain a write lock on the {@code FileBased} object beforethey access it. (In case of a save operation, a read lock would probably be sufficient, but because of the possible injection of a {@link FileLocator}object it is not allowed to perform multiple save operations in parallel; therefore, by obtaining a write lock, we are on the safe side.)
This class is thread-safe.
@version $Id: FileHandler.java 1606588 2014-06-29 19:45:14Z oheger $ @since 2.0
org.apache.commons.configuration2.io.FileHandler
A class that manages persistence of an associated {@link FileBased} object.

Instances of this class can be used to load and save arbitrary objects implementing the {@code FileBased} interface in a convenient way from and tovarious locations. At construction time the {@code FileBased} object tomanage is passed in. Basically, this object is assigned a location from which it is loaded and to which it can be saved. The following possibilities exist to specify such a location:
- URLs: With the method {@code setURL()} a full URL to the configurationsource can be specified. This is the most flexible way. Note that the {@code save()} methods support only file: URLs.
- Files: The {@code setFile()} method allows to specify the configurationsource as a file. This can be either a relative or an absolute file. In the former case the file is resolved based on the current directory.
- As file paths in string form: With the {@code setPath()} method a fullpath to a configuration file can be provided as a string.
- Separated as base path and file name: The base path is a string defining either a local directory or a URL. It can be set using the {@code setBasePath()} method. The file name, non surprisingly, defines thename of the configuration file.
An instance stores a location. The {@code load()} and {@code save()} methodsthat do not take an argument make use of this internal location. Alternatively, it is also possible to use overloaded variants of {@code load()} and {@code save()} which expect a location. In these cases thelocation specified takes precedence over the internal one; the internal location is not changed.

The actual position of the file to be loaded is determined by a {@link FileLocationStrategy} based on the location information that has beenprovided. By providing a custom location strategy the algorithm for searching files can be adapted. Save operations require more explicit information. They cannot rely on a location strategy because the file to be written may not yet exist. So there may be some differences in the way location information is interpreted by load and save operations. In order to avoid this, the following approach is recommended:
- Use the desired {@code setXXX()} methods to define the location of thefile to be loaded.
- Call the {@code locate()} method. This method resolves the referencedfile (if possible) and fills out all supported location information.
- Later on, {@code save()} can be called. This method now has sufficientinformation to store the file at the correct location.
When loading or saving a {@code FileBased} object some additionalfunctionality is performed if the object implements one of the following interfaces:
- {@code FileLocatorAware}: In this case an object with the current file location is injected before the load or save operation is executed. This is useful for {@code FileBased} objects that depend on their current location,e.g. to resolve relative path names.
- {@code SynchronizerSupport}: If this interface is implemented, load and save operations obtain a write lock on the {@code FileBased} object beforethey access it. (In case of a save operation, a read lock would probably be sufficient, but because of the possible injection of a {@link FileLocator}object it is not allowed to perform multiple save operations in parallel; therefore, by obtaining a write lock, we are on the safe side.)
This class is thread-safe.
@version $Id: FileHandler.java 1624601 2014-09-12 18:04:36Z oheger $ @since 2.0
org.apache.turbine.util.upload.FileHandler
This class is used to upload files from a client to the server (any types and any number of fields is supported) and download files from the server to the client. @author Oleg M. Podolsky @author Neeme Praks @deprecated Use TurbineUploadService counterpart FileItem.
org.auto.io.scanner.FileHandler
文件处理器 @author XiaohangHu
org.jboss.internal.soa.esb.couriers.helpers.FileHandler
org.jboss.logmanager.handlers.FileHandler
org.owasp.jbrofuzz.io.FileHandler

Class responsible for generating all the file I/O required for an instance of JBroFuzz to function correctly.
@author subere@uncon.org @version 2.0 @since 1.2
org.richfaces.photoalbum.util.FileHandler
A wrapper class for handling two different classes: RichFaces' UploadedFile and java.io.File UploadedFile is created from a local file when using rich:fileUploader File is created from a remote file when downloading a file from an URL @author mpetrov
tv.ustream.yolo.handler.FileHandler
@author bandesz

Examples of java.util.logging.FileHandler

    logger.setLevel(level);
    try {
      SimpleDateFormat sdf = new SimpleDateFormat("yyyy-MM-dd hh-mma");
      Date currentTime_1 = new Date();
      String dateTime = sdf.format(currentTime_1);
      fileTxt = new FileHandler(dateTime + " log.txt");
    } catch (SecurityException e) {
      e.printStackTrace();
    } catch (IOException e) {
      e.printStackTrace();
    }

View Full Code Here

Examples of java.util.logging.FileHandler

            commandLog.setLevel(Level.ALL);


            log.log(Level.INFO, "Logging WorldEdit commands to " + file.getAbsolutePath());


            try {
                dynamicHandler.setHandler(new FileHandler(file.getAbsolutePath(), true));
            } catch (IOException e) {
                log.log(Level.WARNING, "Could not use command log file " + path + ": " + e.getMessage());
            }
        }

View Full Code Here

Examples of java.util.logging.FileHandler

                }
            }
            else if(logFile.isDirectory()) {
                logFile = new File(logFile.getAbsolutePath()+ Config.getPathSeparator()+"aesh.log");
            }
            logHandler = new FileHandler(logFile.getAbsolutePath());
            logHandler.setFormatter(new SimpleFormatter());
        }
        catch (IOException e) {
            e.printStackTrace();
        }

View Full Code Here

Examples of java.util.logging.FileHandler

    fLoggers.add(logger);
  }
  
  private void createFileHandler() throws AppException {
    try {
      fHandler = new FileHandler(getFileName(), MAX_BYTES, NUM_FILES, APPEND_TO_EXISTING);
      fHandler.setLevel(Level.FINEST);
      fHandler.setFormatter(new TimeSensitiveFormatter());
    }
    catch (IOException ex){
      throw new AppException("Cannot create FileHandler: " + ex.toString() , ex);

View Full Code Here

Examples of java.util.logging.FileHandler

        initProps();
        File file = new File(TEMPPATH + SEP + "log");
        file.mkdir();
        manager.readConfiguration(EnvironmentHelper
                .PropertiesToInputStream(props));
        handler = new FileHandler();
        r = new LogRecord(Level.CONFIG, "msg");
        errSubstituteStream = new NullOutputStream();
        System.setErr(new PrintStream(errSubstituteStream));
    }

View Full Code Here

Examples of java.util.logging.FileHandler

    }


    public void testLock() throws Exception {
        FileOutputStream output = new FileOutputStream(TEMPPATH + SEP + "log"
                + SEP + "java1.test.0");
        FileHandler h = new FileHandler();
        h.publish(r);
        h.close();
        assertFileContent(TEMPPATH + SEP + "log", "java1.test.0", h
                .getFormatter(), "UTF-8");
        output.close();
    }

View Full Code Here

Examples of java.util.logging.FileHandler

        handler.publish(r);
        handler.close();
        // output 3 times, and all records left
        // append mode is true
        for (int i = 0; i < 3; i++) {
            handler = new FileHandler();
            handler.publish(r);
            handler.close();
        }
        assertFileContent(TEMPPATH + SEP + "log", "java0.test.0",
                new LogRecord[] { r, null, r, null, r, null, r },

View Full Code Here

Examples of java.util.logging.FileHandler

        handler.publish(r);
        handler.close();
        props.clear();
        manager.readConfiguration(EnvironmentHelper
                .PropertiesToInputStream(props));
        handler = new FileHandler();
        assertNull(handler.getEncoding());
        assertNull(handler.getFilter());
        assertTrue(handler.getFormatter() instanceof XMLFormatter);
        assertEquals(handler.getLevel(), Level.ALL);
        assertNotNull(handler.getErrorManager());
        handler.publish(r);
        handler.close();
        // output 3 times, and only one record left
        // default append mode is false
        for (int i = 0; i < 3; i++) {
            handler = new FileHandler();
            handler.publish(r);
            handler.close();
        }
        assertFileContent(HOMEPATH, "java0.log", new XMLFormatter(), null);
    }

View Full Code Here

Examples of java.util.logging.FileHandler

    public void testLimitAndCount() throws Exception {
        handler.close();
        // very small limit value, count=2
        // output, rename current output file to the second generation file
        // close it and open a new file as rotation output
        handler = new FileHandler("%t/testLimitCount%g", 1, 2, false);
        handler.publish(r);
        handler.close();
        assertFileContent(TEMPPATH, "testLimitCount1", handler.getFormatter(), "UTF-8");


        // very small limit value, count=1
        // output once, rotate(equals to nothing output)
        handler = new FileHandler("%t/testLimitCount%g", 1, 1, false);
        handler.publish(r);
        handler.close();
        assertFileContent(TEMPPATH, "testLimitCount0", new LogRecord[0],
                handler.getFormatter(), "UTF-8");


        // normal case, limit is 60(>2*msg length <3*msg length), append is
        // false
        handler = new FileHandler("%t/testLimitCount%u", 60, 3, false);
        LogRecord[] rs = new LogRecord[10];
        // batch output twice to test the append mode
        for (int i = 0; i < 5; i++) {
            rs[i] = new LogRecord(Level.SEVERE, "msg" + i);
            handler.publish(rs[i]);
        }
        handler.close();
        handler = new FileHandler("%t/testLimitCount%u", 60, 3, false);
        for (int i = 5; i < 10; i++) {
            rs[i] = new LogRecord(Level.SEVERE, "msg" + i);
            handler.publish(rs[i]);
        }


        assertFileContent(TEMPPATH, "testLimitCount0.1", new LogRecord[] {
                rs[5], rs[6], rs[7] }, handler.getFormatter(), "UTF-8");
        assertFileContent(TEMPPATH, "testLimitCount0.0", new LogRecord[] {
                rs[8], rs[9] }, handler.getFormatter(), "UTF-8");


        // normal case, limit is 60(>2*msg length <3*msg length), append is true
        handler = new FileHandler("%t/testLimitCount%u", 60, 3, false);
        // batch output twice to test the append mode
        for (int i = 0; i < 5; i++) {
            rs[i] = new LogRecord(Level.SEVERE, "msg" + i);
            handler.publish(rs[i]);
        }
        handler.close();
        handler = new FileHandler("%t/testLimitCount%u", 60, 3, true);
        for (int i = 5; i < 10; i++) {
            rs[i] = new LogRecord(Level.SEVERE, "msg" + i);
            handler.publish(rs[i]);
        }
        handler.close();
        assertFileContent(TEMPPATH, "testLimitCount0.2", new LogRecord[] {
                rs[3], rs[4], null, rs[5] }, handler.getFormatter(), "UTF-8");
        assertFileContent(TEMPPATH, "testLimitCount0.1", new LogRecord[] {
                rs[6], rs[7], rs[8] }, handler.getFormatter(), "UTF-8");
        assertFileContent(TEMPPATH, "testLimitCount0.0",
                new LogRecord[] { rs[9] }, handler.getFormatter(), "UTF-8");


        FileHandler h1 = null;
        FileHandler h2 = null;
        try {
            File logDir = new File("log");
            reset("log", "");
            logDir.mkdir();
            h1 = new FileHandler("log/a", 0, 1);
            assertNotNull(h1);
            h2 = new FileHandler("log/a", 0, 1, false);
            assertNotNull(h2);
        } finally {
            try {
                h1.close();
            } catch (Exception e) {
            }
            try {
                h2.close();
            } catch (Exception e) {
            }
            reset("log", "");
        }
    }

View Full Code Here

Examples of java.util.logging.FileHandler

            } catch (SecurityException e) {
            }


            handler.publish(new LogRecord(Level.SEVERE, "msg"));
            try {
                handler = new FileHandler();
                fail("should throw security exception");
            } catch (SecurityException e) {
            }


            try {
                handler = new FileHandler("pattern1");
                fail("should throw security exception");
            } catch (SecurityException e) {
            }
            try {
                handler = new FileHandler("pattern2", true);
                fail("should throw security exception");
            } catch (SecurityException e) {
            }
            try {
                handler = new FileHandler("pattern3", 1000, 1);
                fail("should throw security exception");
            } catch (SecurityException e) {
            }
            try {
                handler = new FileHandler("pattern4", 1000, 1, true);
                fail("should throw security exception");
            } catch (SecurityException e) {
            }
        } finally {
            System.setSecurityManager(currentManager);

View Full Code Here

0 1 2 3 4 5 6

TOP

All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.