- This topic has 2 replies, 1 voice, and was last updated 17 years, 3 months ago by
.
-
Posts
-
My department recently purchased OC4J and I am trying to get our applications configured properly to run on the new app server.
There are two files that I need to add to our deployments, orion-application.xml and orion-web.xml. I have added these files to my project but Eclipse is indicating that there are errors in the files.
In the orion-application.xml file there is an attribute that Oracle adds to the file when it generates the initial file. That attribute is “component-classification”. This attribute is not in the schema http://xmlns.oracle.com/oracleas/schema/orion-application-10_0.xsd. So Eclipse is complaining that the file is not valid.
In the orion-web.xml file there are two errors. The most critical one is that the referenced schema http://xmlns.oracle.com/oracleas/schema/orion-web-10_0.xsd contains errors. I am not sure what errors it does contain. There is also an attribute named “context-root” that does not appear in the schema.
Has anybody else, using OC4J, experienced these particular problems? Is there anything that I can do to suppress validation on these particular files? I still wnat validation turned on in general.
Well at least I figured something out on this, the only problem now is how to correct it. I was wondering why Oracle would be generating invalid XML so I started looking through the OAS folders to find XSD bundled with the OAS. I found a jar file named oc4j-schemas and had me a ganders.
Oooo.. what fun was inside. The schemas in this file are different then the ones available online. These schemas include the missing attributes and do not contain errors.
So now my question is how to tell Eclipse to use the schemas in this jar file for validation rather than using the URLs in the XML documents. Any ideas?
