OK, so it turns out that the spurious pre in the first blog post is due to a spurious backquote in import.sql:
insert into blogentry (blog_name, id, title, excerpt, body, date) values ('JBoss Seam Blog', 'seamtext', 'Introducing Seam Text', ...+'<table style="border:1px solid blue;"><tr><td>Foo</td><td>Bar</td></tr></table>`', '2007-01-18 4:00')
Take out that final backquote, and the bad pre tag vanishes.
So the question is, should SeamText be smart enough to close dangling elements? And is it a bug that the main index.xhtml page isn't being served as application/xhtml+xml under Firefox?
I fixed the test data. It's probably possible (but very difficult) to get the ANTLR parser to close off dangling elements resulting from broken wikitext markup, but its much better if we just find a good way to indicate to the user that their markup is broken.
Any suggestions on that? I could look into patching that if we can come up with a reasonably simple plan. Since I'm actually planning to build a production-quality blogging app with Seam, broken markup would be a big drag, so I'm incented to fix it.
Also, can you confirm (or not) the issue with index.xml not producing a closing /feed tag?
Welcome back, by the way :-) Cheers!