Hi Danilo and gjoseph, thanks for your help! I am using Magnolia 4.4.4. I am using the "empty war" version, directly downloaded from the magnolia web site. It has no repository or logs directory, and the only change I make is in the config of the repository so it uses Oracle instead of Derby.
I am working in a pre-production environment and have full admins rights to linux, tomcat and oracle. Each time I try to install I start from scratch: 1. Stop tomcat 2. Delete magnolia directory from webapps, created by deploying WAR. Leave WAR in webapps. 3. Drop cascade and re-create oracle user (thus deleting all tables, sequences, triggers, etc.) 4. Start tomcat Doing it like that re-creates a clean magnolia directory within webapps each time, with no repositories. The install process starts, the database tables are created, etc. But it fails with that xalan error. I just downloaded the empty 4.4.4 WAR and you're right, there's not xalan jar in WEB-INF/lib. How the heck did it get in mine? I'll try removing it from the WAR and re-deploying. But if it's an unnecessary jar, why does its presence mess everything up? Is it over-riding some other xml parser that Magnolia needs, just by being present? Thanks again! -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=3edb24e9-40ec-43c4-ad1e-ed1ef4d5f789 ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
