Skip to main content

Guava: Some useful IO utilities

Guava IO package provides very useful utility classes for input/ouput stream, byte stream, file handling and many more.

Here are few example which show case how these utilities can make your code much cleaner, modular and more readable.


Copy “InputStream” to “OutputStream


        InputStream is = CopyStreams.class.getResourceAsStream("test.txt");
        OutputStream os = System.out;
        ByteStreams.copy(is, os);


Changing InputStream to “byte[]”


        InputStream is = CopyStreams.class.getResourceAsStream("test.txt");

        byte[] isBytes = ByteStreams.toByteArray(is);      

 // Now if you want to get base64 encoded string then it will be like this  
        String isBase64Str = new sun.misc.BASE64Encoder().encode(isBytes);


Combining two files in one


        File input1 = new File("c:\\testio\\AWords.txt");
        File input2 = new File("c:\\testio\\BWords.txt");
        File output = new File("c:\\testio\\ABWords.txt");
        InputSupplier<InputStreamReader> rs1 = Files.newReaderSupplier(input1, Charsets.UTF_8);
        InputSupplier<InputStreamReader> rs2 = Files.newReaderSupplier(input2, Charsets.UTF_8);        
        InputSupplier<Reader> combined = CharStreams.join(rs1, rs2);
        OutputSupplier<OutputStreamWriter> ws = Files.newWriterSupplier(output, Charsets.UTF_8, false);
        CharStreams.copy(combined, ws);


Processing the file


public class IOTest {
    public static LineProcessor<List<String>> collectWordsStartWithZ = 
        new LineProcessor<List<String>>() {
            List<String> collector = Lists.newArrayList();
            final static String PREFIX = "z";
            public boolean processLine(String line) {
                String line_ = Strings.nullToEmpty(line).trim().toLowerCase();
                if (!line_.isEmpty() && line_.startsWith(PREFIX)) {
                return true;
            public List<String> getResult() {
                return collector;

    public static void main(String[] args) throws IOException {
        URL resource = IOTest.class.getResource("test.txt");
        List<String> lines = Resources.readLines(resource, Charsets.UTF_8, collectWordsStartWithZ);

        for (String line : lines) {


Popular posts from this blog

ERROR: Ignored call to 'alert()'. The document is sandboxed, and the 'allow-modals' keyword is not set.

Recently I found this issue while writing code snippet in "JSFiddle". And after searching, found this was happening because of new feature added in "Chrome 46+". But at the same time Chrome doesn't have support for "allow-modals" property in "sandbox" attribute.

Chromium issue for above behavior:

To make it work you have to add "allow-scripts allow-modals" in "sandbox" attribute, and use "window.alert" instead of "alert".

<!-- Sandbox frame will execute javascript and show modal dialogs --> <iframe sandbox="allow-scripts allow-modals" src="iframe.html"> </iframe>

Feature added: Block modal dialog inside a sandboxed iframe.

Feature working Demo page:

CSS Specificity

Many time different CSS rules overlap on one or more element. And some people always get confuse about, which rule will take higher priority then other and why? CSS Specificity is the answer of all these kind of questions.
As the name suggest, the CSS rule which is more specific to the element will take higher priority then other. Means something like “#some_id{}” will always take higher priority then “*{}” universal selector.  And if duplicate rules are define then the last rule will be applied to the element.

The following list of selectors is by increasing specificity:
Type selector (e.g., div) and pseudo-elements in selector (e.g., :after) Class selectors (e.g., .some_class), attributes selectors (e.g., [type=”radio”]) and pseudo-class selector (e.g., :hover) Id selectors (e.g., #some_id)

ID takes higher priority then Class, Type and Universal selector (Note: Universal selector has no effect on specificity, see below special conditions). 

If duplicate rules are given, then last…

JavaScript [ExtJs3]: EditorGridPanel Read-Only (dynamically)

Many time we face the scenerio where we have to make the editor grid read-only dynamically.

Ext.override(Ext.ux.grid.CheckColumn, { editable: true, onMouseDown: function (e, t) { if ( { e.stopEvent(); var me = this, grid = me.grid, view = grid.getView(), index = view.findRowIndex(t), colindex = view.findCellIndex(t), record =; if (!grid.isReadOnly && grid.colModel.isCellEditable(colindex, index)) { record.set(me.dataIndex, ![me.dataIndex]); } } } }); var grid = new Ext.grid.EditorGridPanel({ ... isReadOnly: true, //set to flag to make check column readonly ... }); //to make other column readonly grid.on('beforeedit', function () { return false; });