G
glunk
Hi. As you can tell from my rapid posts, I am struggling with a design
issue. I am not happy with the design (or lack thereof) which has occured in
the subsystem that I am working on. No one has yet tried to use this
subsystem, so I do not have to worry about changing the interface. So I am
trying to fix it. But since I am new to Java, when to use what is confusing
to me.
I have a class called PdfDocWriter. It has a bunch of instance variables for
things that are needed to create the PDF (pdfOutputFileName, templateName,
acribatVersion...) There are 3 methods that I want, writeDocToPrint(),
writeDocToImaging() and a private deleteFdF.
This is all the info necessary to create the PDF except for the name and
value for each field on the acrobat form.
I need a structure for an indeterminant number of name / value pairs. When
an application (application form for applying for loans) is created, they
will be able to use the class I am designing simply by giving the instance
vars their info and supplying this name / value pair thing.
I am planning to have a class for PdfValues with 2 attributes. Then for the
ConsolidationApplicationPdf class, I will use a collection of the PdfValues.
Does this seem a good way to go?
I am sorry if I am asking for basic info or if it seems like I am asking you
to solve my business problems for me. I wish I had someone around here on
whom I could bounce around ideas. But I do not.
Thanks
S
issue. I am not happy with the design (or lack thereof) which has occured in
the subsystem that I am working on. No one has yet tried to use this
subsystem, so I do not have to worry about changing the interface. So I am
trying to fix it. But since I am new to Java, when to use what is confusing
to me.
I have a class called PdfDocWriter. It has a bunch of instance variables for
things that are needed to create the PDF (pdfOutputFileName, templateName,
acribatVersion...) There are 3 methods that I want, writeDocToPrint(),
writeDocToImaging() and a private deleteFdF.
This is all the info necessary to create the PDF except for the name and
value for each field on the acrobat form.
I need a structure for an indeterminant number of name / value pairs. When
an application (application form for applying for loans) is created, they
will be able to use the class I am designing simply by giving the instance
vars their info and supplying this name / value pair thing.
I am planning to have a class for PdfValues with 2 attributes. Then for the
ConsolidationApplicationPdf class, I will use a collection of the PdfValues.
Does this seem a good way to go?
I am sorry if I am asking for basic info or if it seems like I am asking you
to solve my business problems for me. I wish I had someone around here on
whom I could bounce around ideas. But I do not.
Thanks
S