Sorry Daniel, I have to disagree.
My view of POI is that it simply (???) exposes the .xls file to an application.
If it were to function as you suggest then it would be making assumptions on
the part of the user - the application in this case - and your requirements may
differ from mine. Surely it is our role as developers to decide how to handle
the information POI exposes. I would argue that you could create a layer to sit
over the API that makes these types of decisions - after all that is what we
would do if coding an application that uses a large relational database for
example.
Daniel Noll <[EMAIL PROTECTED]> wrote: On Friday 02 May 2008 20:56:02 Nick
Burch wrote:
> If you wanted to set all of those cells to hold the value 42.0, you'd do:
>
> row.getCell(0).setCellValue(42.0)
> row.getCell(1).setCellValue(42.0)
> row.getCell(2).setCellValue(42.0)
> row.createCell(3).setCellValue(42.0)
> row.getCell(4).setCellValue(42.0)
>
> So a blank cell really is different from a null cell, as you can just
> write straight into a blank cell, while a null cell needs to be created
> first
This is still exposing the underlying details if you ask me. In an ideal
world, getCell(int) would, for a null cell, either create the cell for us, or
return something with the same interface which creates the real thing if you
set something on it.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
