title: Unreadable output from SuperCSV?
body: <p>I have a utility class I created for my Spring controller to invoke to generate a CSV from a collection of beans using the SuperCSV library ( <a href="http://supercsv.sourceforge.net/" rel="nofollow">http://supercsv.sourceforge.net/</a> )</p>
  
  <p>The utility class is pretty basic:  </p>
  
  <pre><code>public static void export2CSV(HttpServletResponse response,
          String[] header, String filePrefix, List&lt;? extends Object&gt; dataObjs) {
      try{
          response.setContentType("text/csv;charset=utf-8"); 
          response.setHeader("Content-Disposition","attachment; filename="+filePrefix+"_Data.csv");
  
          OutputStream fout= response.getOutputStream();  
          OutputStream bos = new BufferedOutputStream(fout);   
          OutputStreamWriter outputwriter = new OutputStreamWriter(bos); 
  
          ICsvBeanWriter writer = new CsvBeanWriter(outputwriter, CsvPreference.EXCEL_PREFERENCE);
  
          // the actual writing
          writer.writeHeader(header);
  
          for(Object anObj : dataObjs){
              writer.write(anObj, header);                                
          }
      }catch (Exception e){
          e.printStackTrace();
      }
  };
  </code></pre>
  
  <p>The catch is, I'm getting different behaviors out of this operation and I don't know why.  When I invoke it from one controller (we'll call it 'A'), I get the expected output of data.</p>
  
  <p>When I invoke it from the other controller ('B'), I get a tiny blurb of unrecognizable binary data that cannot be opened by OO Calc.  Opening it in Notepad++ yields an unreadable line of gibberish that I can only assume is an attempt by the reader to show me a binary stream.</p>
  
  <p>Controller 'A' invocation (the one that works)</p>
  
  <pre><code>@RequestMapping(value="/getFullReqData.html", method = RequestMethod.GET)
  public void getFullData(HttpSession session, HttpServletRequest request, HttpServletResponse response) throws IOException{
      logger.info("INFO:  ******************************Received request for full Req data dump");
      String projName=  (String)session.getAttribute("currentProject");
      int projectID = ProjectService.getProjectID(projName);
      List&lt;Requirement&gt; allRecords = reqService.getFullDataSet(projectID);
  
        final String[] header = new String[] { 
                "ColumnA", 
                "ColumnB",                  
                "ColumnC",
                "ColumnD",
                "ColumnE"
                };
  
        CSVExporter.export2CSV(response, header, projName+"_reqs_", allRecords);
  
  
  };
  </code></pre>
  
  <p>...and here's the Controller 'B' invocation (the one that fails):</p>
  
  <pre><code>@RequestMapping(value="/getFullTCData.html", method = RequestMethod.GET)
  public void getFullData(HttpSession session, HttpServletRequest request, HttpServletResponse response) throws IOException{
      logger.info("INFO:  Received request for full TCD data dump");
      String projName=  (String)session.getAttribute("currentProject");
      int projectID = ProjectService.getProjectID(projName);
      List&lt;TestCase&gt; allRecords = testService.getFullTestCaseList(projectID);
  
      final String[] header = new String[] { 
              "ColumnW", 
              "ColumnX",
              "ColumnY",                
              "ColumnZ"
           };
  
      CSVExporter.export2CSV(response, header, projName+"_tcs_", allRecords);
  }
  </code></pre>
  
  <p>Observations:</p>
  
  <ul>
  <li>Which controller I invoke first is irrelevant.  'A' always works and 'B' always produces gibberish</li>
  <li>Both calls to this function have a list of header columns that are a subset of the total set of operations defined in the bean being passed in to CSVWriter</li>
  <li>The simple Exception printStackTrace is working to detect when a bean's reflection field doesn't match the definition (i.e., can't find get() to get the value programmatically) suggesting that all column/variable matchups are succeeding.</li>
  <li>In the debugger, I've verified the writer.write(Object, header) call is being hit the expected number of times based on the number of objects being passed and that these objects have the expected data </li>
  </ul>
  
  <p>Any suggestions or insights would be greatly appreciated.  I'm really stumped how to better isolate the issue...</p>