Mariano Kamp wrote: > > Hello Berin, > > your explanations are quite helpful. Just one little question: > > >[..] > > > 2) Generator: A generator performs XML generation from some external > > source, whether it is a stream, an object, or database. It must send SAX > > events to the next component in a chain. A Generator is always the first > > component in a chain. Due to the SAX implementation, it cannot be > > ThreadSafe--but can be Pooled. > > >[..] > > > 4) Serializer: A serializer receives XML from a chain, and converts it to > > an external stream. A Serializer is the last element in a stream. > > Again, it has the same constraints placed upon it as Generator due to the > > same issues. > > I guess you are referring to the need to use instance variables? What I don't > get is that there is no setup method in Serializer. I was already asking this > once, but Giacomo just replied: "It is the way it is designed." Could you > probably cast some light into the schadow? I was refering to the SAX methods. In regular use, it receives multiple SAX events, so it does not have a single entry point, or a document scoping method. > So my real question is: If a serializer needs to have instance variables > why shouldn't has it a setup() Method? The absence of the Setup method is due to the lack of runtime behavior modification ability. A serializer should function the same way every time it is used, regardless of runtime parameters. That is the main reason it does not have a setup() method. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
