On Wed, June 7, 2006 2:16 am, Craig McClanahan wrote: > I didn't make it clear in my previous comment ... but I totally agree with > Martin that actually *building* an anything->PDF converter as part of > Struts > is out of scope. > > But that's a different thing from providing a PdfResult interface that has > a > strategy pattern plugin to configure an adapter for your favorite PDF > generation tool ... perhaps with an example application that has an > implementation for one particular PDF generation library (i.e. the > implementation itself is a demo, not part of the core of Struts). That > kind > of approach would be perfectly reasonable to me. As would some eventual > commitment for the Struts project to support some small number of adapters > to particular PDF generation libraries where we had committers willing to > maintain the adapters in response to API changes in the underlying > generators. > > Frank, does that difference in viewpoint help you see the scoping issue > here?
Yes, it does... I actually understood what Martin was saying from his last reply, but you re-state it very clearly, which never hurts :) As you put it here, I certainly don't disagree at all. Well, I have some playing to do :) > -- >> Martin Cooper > > > Craig Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
