> Like I said, I got the stuff working. In another thread I said I > don't really care if we use Anakia or Cocoon to do the generation. > That really doesn't concern me one way or the other. I am saying > that I don't want <div/> tags in my XML. I want to use a DTD that > we #1 already agreed upon, and #2 represents the semantic intent > of the document better. > > I *know* Anakia can work with the current DTD. If it can't, then > we can supply a stylesheet to make the transformation at build time. > Either way I don't really care how it gets done. I don't want an > unorganized and broken DTD.
Anakia is the idea that you create a DOM tree from an xml document and then put it inside a velocity context, and then you get a list of files to process (project.xml) and a velocity stylesheet and merge the two. This idea has been implemented as an ant task. That's all it is. You can make it validate a DTD by supplying the DTD to Xerces, just like you can turn off validation in cocoon by not supplying the DTD. Because it is so simple and doesn't enforce anything (it'll eat any xml that will not result in a parse error during DOM building, ie any xml that is well-formed), it is also such a pain. I'd argue anakia error messages are worse than cocoon's; as they're not there when they should be. If it really is the only way to get the -1s to stop happening, I'll throw away a weekend or so to build exactly that. - Leo -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
