Hi Rick, I had the same problem with the xmldsig Schema while I was trying to generatie source code for XML digital signatures handling. There seems to be no easy fix to the source generator as you would have to test specifically for the "Object" tag in many places. What I did was change the source generator to have an explicit "java.lang.Object" import in all generated classes. After that, I need to manually edit the three classes related to the tag "Object" handling. I submitted the same message to the mailing list, but I'm still waiting for a response... Regards, Francis Vermeulen
-----Original Message----- From: Rick Hogge [mailto:[EMAIL PROTECTED]] Sent: Saturday, January 19, 2002 1:15 AM To: [EMAIL PROTECTED] Subject: [castor-dev] DTD with element called Object causes problems in generated source. I downloaded the xmldsig DTD (8/2001) from w3c and found that there is an element defined with the name Object. <!ELEMENT Object (#PCDATA|Signature|SignatureProperties|Manifest %Object.ANY;)* > <!ATTLIST Object Id ID #IMPLIED MimeType CDATA #IMPLIED Encoding CDATA #IMPLIED > Obviously, this is causing me problems in the source code that is generated. I looked at the Castor source and I believe that I can fix this by modifying the code in the org.exolab.castor.builder package to use the string java.lang.Object instead of Object. I am fairly new to Castor, so I was wondering if anyone had an easy solution for me or should I proceed with these changes? Thanks in advance Rick Hogge ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
