RE: Replacement for QNameHelper.updateWellKnownPrefixes?

[Pantvaidya, Vishwajit]

Hello Cezar,   Thanks for your reply.   I investigated this further and here is a quick summary of my findings: - the library I am using bundles xmlbeans 1.0.2 and some beans generated from that - the library also makes calls to Apache XML Security library classes like XMLSignature and SignedInfo which use DOM for xml operations - SignedInfo class makes the call Element.getAttributeNS(null, Constants._ATT_ALGORITHM)             - this works with the xmlbeans 1.0.2 version that the library uses - but we use xmlbeans version 1.0.3/1.0.4 and so when I try to run with this xbeans jar it returns empty/null even though the element has the algorithm attribute   This seems strange because when I debug in eclipse, I do not see any different in the contents of Element object between xmlbeans 1.0.2 and 1.0.4 – so why does the DOM call made by SignedInfo return different results in each case?   Any suggestions? It is probably not a good idea anyway to use beans generated by 1.0.2 with 1.0.4 bean library – but it just seems strange that the xml seems to be correct in both cases, but the 1.0.4 xmlbean libs do not work. Even stranger - that the call that is failing is actually a DOM call and not an XMLbeans api call.   Thanks,   Vish.   From: Cezar Andrei [mailto:[EMAIL PROTECTED] Sent: Friday, April 28, 2006 1:17 PM To: user@xmlbeans.apache.org Subject: RE: Replacement for QNameHelper.updateWellKnownPrefixes?   Did you try XmlOptions’ setSaveSuggestedPrefixes() ?   From: Pantvaidya, Vishwajit [mailto:[EMAIL PROTECTED] Sent: Friday, April 28, 2006 1:30 PM To: user@xmlbeans.apache.org Subject: Replacement for QNameHelper.updateWellKnownPrefixes?   I have some old code that uses 1.0.2 xmlbeans – it has a call to QNameHelper.updateWellKnownPrefixes to update some prefixes. I see that the call updates the prefixes into the WELL_KNOWN_PREFIXES map. But this method no longer exists – is there another suggested way to achieve the same goal?   - Vish. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.