|
 Comparing POI
to OfficeWriter
|
 |
|
There's no arguing the importance of open source projects
like Jakarta's POI within the Java™ community. But, like many complex
open source projects, there are key limitations when using
POI as part of your Web reporting application.
|
|
Here are just a few pros and cons to keep in mind when choosing
between POI and generating native Excel and Word reports with OfficeWriter from your front-end Java™ web application.
FEATURES | CODE
COMPLEXITY | EASE
OF USE | SUPPORT
Features
Code Complexity
| OfficeWriter |
POI |
| As few as five
lines of code, yet flexible |
Dozens
of lines of code for simple tasks |
| Handles data translation
automatically with type safety |
Requires manual translation
of data types:
Database Type -> Java™ Type -> Excel Type |
| Excel/Word is your
design tool |
The spreadsheet or
document is designed in code which you must compile
and run to see every graphical change |
|
Ease Of Use
| OfficeWriter |
POI |
| Template
driven development, only a few lines of code required |
Must use a programmatic
style - each row, cell, formula, etc. must be written
in code |
| End users easily design
reports via Excel and Word |
Developers design
reports in code via a complex object model |
Responsive:
- No need to recompile code for simple
layout and format changes
- Updates rapidly and immediately
- End users can easily modify report design
|
|
Inflexible:
- Recompilation required to view every
minor design change
- Every change requires access to the code
|
|
| Includes comprehensive
documentation and samples, in addition to JavaDocs |
JavaDocs only |
|
Support
|
| | | | |
|
