Sir / Madam, There is a problem with Xerces in that it is confusing the use of Element tag-names and the Element Type name. I originally saw this in the 1.0.3 release.
I started to debug this, and found the right area, but did not have time to fine the "How" to fix it. Then of course a lot of work has been done in the XML Schema validiation part of the sources, so I started pulling down snap shots from the CVS. Initially, there were other problems, but now it seems like it is still there. To complicate the issue I am still on the December draft of the XML Schema specs. It appears that the new code in the Xerces repository is heading for the April draft. I can move, but I am finding a real mix of XML Schema grammer support that is making me crasy... Have kind of been waiting for this bug to be fixed for me, but I don't see it. The problem as to do with the copyAtts() not associated the attribute information with all Element names associated with certain Element Type name. It only assoicates it with the first Element name, which is less then useful. If I have a nested element, with a different name, but of the same Type, no Schema validation is ever done because the differently named Element is never connected to the Type attributes that are connected with the original top-level Element of said Type. I have updated from the repository just now and will attempt to re-debug this issue. It is causing me problems when tools like the new XMLInstance and XMLAutority products that are built on xerces. As well as any other tool using xerces as a basis. If there is anyone else out there that is aware of this problem or knows this area of the code and could help I would appreciate it. I have a running Java Object to XML data binding the uses the XML Schema to define the map (along with a type-tag to Java Class/Interface map) that allows me to easily serialize Java object into XML as well as activate XML data into Java Objects. My big problem right now is that although I can validiate my schemas, none of my XML data is being validated against the schema because of the above mentioned problem. This was OK for development, but we will be deploying a web based product soon build on this layer and I need to get this bug fixed quickly. Nearly all of the data in the system (short of the database layer to the EJBs) moves through my Java/XML data binding layer. All of the XML for the display layer (via XSL) all of the configuration, external JMS event bodies, all of the input data validation... You get the point. Please, if there is someone out there that could help with this fix, it would be greatly appreciated! Sincerely, Cheri McKeown Senior Java Architect Solant Inc. 303 583 3136
