I just wanted to post some of my experience dealing with axis producing malformed XML (duplicate and empty namespace declarations) in the server-config.wsdd under certain circumstances. Basically using OC4J, I would deploy services fine from the deployment tool, but when I stopped and restarted the server it could not parse the server-config.wsdd that had been produced previously. Reading through the mail archive it seemed several people had had this problem mainly with Resin, but someone had it with OC4J as well.
As usual the culprit is the XML parser the container uses. I cannot speak for Resin, but OC4J uses an oracle xml parser library which I guess behaves differently in some subtle way when generating XML. The problem goes away if you force OC4J to find xerces.jar before it's own implementation (I could do this by using -Xbootclasspath/a:<path to xerces.jar or other "good" xml parser> when running OC4J to force oc4j to use xerces first). Unfortunately there does not seem to be a way to do this change locally, i.e. just for the web application running Axis.
Anyway, I thought I would mention my experience since I did not find any replies to the previous posts mentioning this problem.
Thanks to all the developers for their hard work on such a great piece of software.
Regards,
-- Ali Ibrahim Vecna Technologies Email: [EMAIL PROTECTED] W: (301)864-7253
