Skip to main content

POI Spreadsheet Manager - Part 2

Part 1 was just laying some foundation. Now it's time to tackle some of the more troublesome bits of managing XLSX through POI. The first challenge I wanted to tackle is how to define Fonts and CellStyles. Every time you create one of these elements, it gets added to the .xlsx file, even if it is a duplicate of something you've already created. Also, there is a maximum number of each, so if you create your cells dynamically, you can run out of room to create new cells. You can get around this by first creating your spreadsheet, and then applying styling to groups of cells. Buy my goal was dynamic reports. I want to write a report without knowing what kind of data is going to be in each row or cell.

The first question I asked myself is how I wanted to define and keep track of CellStyles and Fonts. I used Enums. Here is how I define fonts.

public enum Fonts {
   REPORT_HEADER(20, 700, Color.BLACK, false),
   REPORT_SUBHEADER(14, 700, Color.BLACK, false),
   COLUMN_HEADER(10, 700, Color.BLACK, false),
   DATA(10, 400, Color.BLACK, false),
   TOTAL(10, 700, Color.BLACK, false),
   ERROR(14, 700, Color.RED, false);

   private short fontHeight;
   private short fontWeight;
   private Color color;
   private boolean italic;

   private Fonts(int fontHeight, int fontWeight, Color color, boolean italic)
   {
      this.fontHeight = (short) fontHeight;
      this.fontWeight = (short) fontWeight;
      this.color = color;
      this.italic = italic;
   }

   public short getFontHeight() {
      return fontHeight;
   }

   public short getFontWeight() {
      return fontWeight;
   }

   public XSSFColor getColor() {
      /**
       * Reverse black and white due to bug
       */
      if (color.equals(Color.BLACK)) {
         return new XSSFColor(Color.WHITE);
      } else if (color.equals(Color.WHITE)) {
         return new XSSFColor(Color.BLACK);
      } else {
         return new XSSFColor(color);
      }
   }

   public boolean isItalic() {
      return italic;
   }
}
And now I need a manager class to handle the creation and lookup of fonts. This class takes a Fonts argument, such as Fonts.REPORT_HEADER and returns the existing font if it has already been created, or creates a new one and returns that. In this way, I only ever create a font once.
public class FontManager {
   private final Workbook wb = null;
   private final Map styleMap;

   protected FontManager(Workbook wb) {
      this.wb = wb;
      this.fontMap = new HashMap;
   }

   public Font get(Fonts f) {
      if (!fontMap.containsKey(f)) {
         fontMap.put(f, createFont(f));
      }
      return fontMap.get(f);
   }
   private Font createFont(Fonts f) {
      XSSFFont font = (XSSFFont) wb.createFont();
      font.setBoldweight(f.getFontWeight());
      font.setFontHeightInPoints(f.getFontHeight());
      font.setFontName(Fonts.FONTNAME);
      font.setColor(f.getColor());
      return font;
   }
}
StyleManager works exactly the same and will be in Part 3...

Comments

Popular posts from this blog

XPages Application Framework (Part 1?)

Note: I changed projects and priorities after my last POI article, resulting in a long hiatus. I anticipate using that framework on my current project and will likely refine and complete my related article series. For the past several months, I've been fortunate enough to lead a project overhaul from traditional Domino Webapp to XPages. I had a few goals in mind, but the top three were integrating Bootstrap, embracing MVC principles, and eliminating all SSJS . I imagine the motivation for Bootstrap integration is self-explanatory. There is an OpenNTF project out there called Bootstrap4XPages. I didn't use that for a number of reasons - the main being a policy in the current environment. But you may ask yourself (if you didn't follow that link), why so much hatred for SSJS? I have a litany of reasons. It impacts readability of the XPage source; it hurts maintainability when logic is scattered across dozens of XPages, custom controls, and script libraries; it mixes log...

Killing SSJS - Passing a parameter using Expression Language - Part 2

In part 1, I showed how you can expand the DataObject implementation to allow you to pass a parameter to a method and return the result. It's not a perfectly elegant solution, and it has some limitations, but it's a very solid technique and not at all difficult to implement or maintain. But I kept running into roadblocks. What if I have to compute part of the expression? What if I have to get a value based on another parameterized getter? You can't compute part of an EL expression in your EL. So after some research and experimentation, I created the GetMap. This isn't a new concept - it was developed for JSF 1.1 (which is what XPages is built on) but the rest of the world has moved on to JSF 2.0 and so some of these older techniques can be a little tricky to unearth since this hasn't been an issue in the JSF world for years.

Rows per page selection: Part 2

I was asked to create a control that would allow users to select the number of rows per page in a view/repeat control (the application uses both). It seemed simple at first, but I ran into a few issues that I thought I'd share the solutions to. Problem 2: When the page refreshed, the combobox value always reverted back to the default It turns out that the Integer value stored in the viewScope doesn't get run through the converter back to a string before being compared to options. I needed a way to calculate the option values so that they would be Integers. This is also not the first time I've run into issues where I need a value to be of a different type, and I see questions like this on StackOverflow from time to time. I attempted a few minor things before I realized I needed to break out my old stand-by, the GetMap . The GetMap is just a fake Map implementation that takes the key and transforms it or uses it to look up some other value. In this case, we are doing the f...