anonymous wrote : I do love the idea of the PDF templating using facelets in Seam for
doing up quick documents and e-mails -- but the idea of adding Excel support then leads to
the plethora of other output formats that you can think of.. and does all that fluff (and
re-inventing of the wheel) really belong in Seam?
It's not like this stuff needs to be deeply integrated into the Seam core, its just an
add-on jar, no big deal. That doesn't count as bloat, IMO.
anonymous wrote : I think most people who need a large variety of output formats will
settle on a more full-featured reporting framework anyway.
The trouble is that reporting tools like these are kindof a world unto themselves, and its
difficult to seamlessly integrate their capabilities into the flow and look and feel of
your application. Plus its a totally alien programming model to learn. (Usually, done by
some "reporting guy" on the project.) I think its highly useful to have some
limited set of reporting capabilities available in the web framework.
View the original post :
Reply to the post :