"RAHMAN,ABDUR (HP-Sunnyvale,ex1)" wrote: > Please let me know if Apache has a solution for this or there > is a third party solution exist for this matter.
No we don't have a solution for this at the time. However, I think that this could be supported in the future by building a DOM document from the XNI DTD callbacks. Here's a completely made-up example: <!ENTITY % string 'CDATA'> <!ELEMENT foo (bar)*> <!ELEMENT bar EMPTY> <!ATTLIST bar baz %string; #REQUIRED> <dtd xmlns='http://xml.apache.org/Xerces2/DTD'> <entityDecl name='%string' value='CDATA'/> <elementDecl name='foo'> <children occurs='*'> <elementRef name='bar'/> </children> </elementDecl> <elementDecl name='bar'/> <attlistDecl element='bar'> <attributeDecl name='baz'> <type name='CDATA'/> <required/> </attributeDecl> </attlistDecl> </dtd> Of course, the breakdown is completely arbitrary but I know that a lot of people will want the separation to be very fine-grained so that they can figure out where parameter entities are expanded in the DTD. For example, in the previous example, there is a parameter entity used for the attribute declaration type. This could translate to a DOM subtree that looks like this (pardon the bizarre syntax): ENTITY_REFERENCE_NODE: name='string', value=null { ELEMENT_NODE: name='type', value=null [ ATTRIBUTE_NODE: name='name', value='CDATA' ] } Your request is relevant to determing the XNI DTD callbacks. You should contribute to the discussion thread "[XNI] DTD Information Set" on the xerces-j-dev mailing list. We could use your feedback. -- Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
