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

Pass data between XPages and existing LS scripts

I'm working on modernizing a fairly hefty application with a lot of existing script libraries which we want to leverage within the XPages environment. Here is a technique that works very well. First, create an in-memory document in SSJS. We can set any input values needed for the back end. Then we pass that document to a LS Agent which can work it's magic using the values set in SSJS and use the same document to return values back to the XPage. Here is how it works in detail:

Fixing FontAwesome for Windows 10

I ran into an issue with FontAwesome a few months back, where a NoCache header was being injected at the server and FA was broken for any partial refresh. I convinced the admin to reverse that setting and all was well until last week... We had some users who were not getting any icons to appear. Ever. We tracked it down to a new Windows 10 setting for IE11 which disallows untrusted fonts. Since we do not set security protocols for our users, and there is no chance of ever convincing those admins to change this policy that they explicitly turned on, I had to find a new solution. I did some searching and it turned out to not be too difficult. First, here is the original implementation. The theme: <control> <name>Icon.Search</name> <property mode="override"> <name>tagName</name> <value>i</value> </property> <property mode="concat"> <name>styleClass</name> <value>fa fa-search...

XPages Application Framework (Part 2 of ?)

In my last post, I offered a very rough overview of the framework I've been building and adapting. Full credit where it's due, I've been borrowing and adapting from Jesse Gallagher's XPages Scaffolding - an awesome project that I've learned a great deal dissecting. This is one of those projects that, if you make the effort to truly understand it, will give you entirely new tools and approaches for problems. As usual, I've learned the most changin g things and breaking them. My project differ s f rom Jesse's mostly in that it supports 8.5.3 and doesn't require any relaxed security permissions - bec ause I'm on 8.5.3 and because the admins h ere will not grant any relaxed permissions.