On Sat, 3 Nov 2001 22:31, Stefano Mazzocchi wrote: > I simply do not and for the reason above: IoC means that you ask for a > resource to Cocoon and it knows what to do.
in this context I agree > > This is a design pattern that must not be altered in any way, under any > circumstance or Cocoon will be nothing different from > Xerces+Xalan+FOP+Batik. > > I hope you guys understand my strong feelings about IoC. I am not sure I fully understand them in this case. So heres my opinion and you can tell me how it fits into your model ;) I think the transaformation pipeline (and possibly serializers) should be completely internal to the proposed cocoon block. However it should be be fair game for the block to have parameters passed in. One of these parameters would of course designate the transformation pipeline. But the question is could one of the parameters passed in be the source to be transformed/processed? Im not sure. In a web application it would of course be out of the question but in other cases ... not so sure. -- Cheers, Pete *---------------------------------------------------------* | Programming today is a race between software engineers | | striving to build bigger and better idiot-proof | | programs,and the universe trying to produce bigger and | | better idiots. So far, the universe is winning. | | - Richard Cook | *---------------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
