4 # SAX version of XML::Template. Advantages over DOM: Doesn't have to load
5 # the entire thing into memory, and you can chain filters. Disadvantages:
6 # Slightly kludgier interface, and you won't get a DOM tree out.
8 # Differences from the DOM version:
10 # - There is no process(). Instead, it works as a SAX filter, so you put it
11 # in the stream, usually between a parser and a writer (ie.
12 # parser -> XML::TemplateSAX::Handler -> writer). process_file works as
13 # before, but it returns a _string_, not a DOM tree.
14 # - You can no longer insert a DOM tree, naturally. Instead, you can set up
15 # an XML::TemplateSAX::Buffer, let it gobble up your data, and send it
16 # in the way you'd insert a DOM tree. process_file_to_buffer does this
17 # transparently for you, returning a buffer you can give in.
24 use XML::TemplateSAX::Buffer;
25 use XML::TemplateSAX::Cleaner;
26 use XML::TemplateSAX::Handler;
28 package XML::TemplateSAX;
30 sub process_file_to_handler {
31 my ($filename, $handler, $obj, $clean) = @_;
32 $clean = 1 unless (defined($clean));
34 my ($cleaner, $filter, $parser);
38 $cleaner = XML::TemplateSAX::Cleaner->new(Handler => $handler);
39 $filter = XML::TemplateSAX::Handler->new(Handler => $cleaner, Content => $obj);
41 $filter = XML::TemplateSAX::Handler->new(Handler => $handler, Content => $obj);
44 # FIXME: hardcoding expat = not good?
45 $parser = XML::SAX::Expat->new(Handler => $filter);
46 $parser->parse_file($filename);
52 my ($filename, $obj, $clean) = @_;
55 my $writer = XML::SAX::Writer->new(Output => \$str);
57 process_file_to_handler($filename, $writer, $obj, $clean);
62 sub process_file_to_buffer {
63 my ($filename, $obj, $clean) = @_;
65 my $buffer = XML::TemplateSAX::Buffer->new;
66 process_file_to_handler($filename, $buffer, $obj, $clean);
72 my ($tag, $array, @elems) = @_;
75 my $num = scalar @elems;
77 for my $ref (@$array) {
79 $ref->{$tag} = $elems[$i++ % $num];