We try to maintain our Model-View-Controller environment as much as possible.
Currently, if our users select a page on our web site, the data is pulled using
JavaBeans and displayed using JSPs.
We are designing in the use of PDFs into our application but can't decide where to put
the PDF code.
Options under consideration for PDF pages:
The data is pulled from JavaBeans and the servlet generates the PDF code.
- Since the report pulls from many data sources, many JavaBeans (about
25 of them) are called and the servlet is HUGE because it is organizing all that data.
The data is pulled from JavaBeans and each bean also creates a PDF Fragment,
the servlet organizes the PDF Fragments.
- This makes the servlet look clean, but the Bean (part of the Model)
is now doing a little View work.
- This solution is also extensible -- each bean can then can contain
PDF Fragment method that can be mixed and matched anywhere in the application to
generate a dynamic PDF document.
The data is pulled from the bean, but the servlet calls a set of new classes
that we create just to handle the sections of the PDF
- This makes the servlet clean (it still organizes the different
sections of the document)
- The bean is clean, (it just does model work)
- We have a new series of classes that we need to maintain (again,
about 25 of them) , but that have very little functionality.
Any input is appreciated.
Thanks,
-John
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
iText-questions mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/itext-questions
