Monica,
I've just had a quick look - the major difference between 2.1 and 2.6 is the use of the xerces namespace. It looks like there are a few places where we haven't been quite clean on the macros, so things are not compiling (the macros should remove namespace usage if the xerces namespace is not defined).
I'll have a look and see what I can do - probably on the weekend. But it would mean you would have to move to a CVS checkout - although we are planning to get a release out in mid Oct.
Cheers,
BerinMonica Lau wrote:
Hi,
I checked the Xerces C++ migration archive, and the DOM reorganization happened in Xerces 2.0.0. Snippet from archive: "The old Java-like DOM is now deprecated, and all the associated files, including the headers and DOMParser files are moved to |src/xercesc/dom/deprecated|. Users of the old Java-like DOM are required to change all their #include lines to pick up the headers." Is this what you're referring to about the old DOM_Node interface? So, I believe 2.1 is using the new interface.
I've included the compilation errors below (compiling XSec 1.0.0 with Xerces 2.1 and OpenSSL 0.9.6b). Please let me know if I need to backtrack to an older version of XSec or upgrade to a higher Xerces version...
Thanks for your help,
Monica
branches 16:57:41 ~/xml-security-c-1.0.0/src $ gmake
mkdir -p ../lib
mkdir -p ../lib/obj
mkdir -p ../bin
mkdir -p ../bin/obj
gmake -C canon includes
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/canon'
mkdir -p ../../include/xsec/canon
cp -p XSECC14n20010315.hpp XSECCanon.hpp ../../include/xsec/canon
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/canon'
gmake -C transformers includes
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/transformers'
mkdir -p ../../include/xsec/transformers
cp -p TXFMBase.hpp TXFMBase64.hpp TXFMC14n.hpp TXFMChain.hpp TXFMDocObject.hpp TXFMEnvelope.hpp TXFMMD5.hpp TXFMOutputFile.hpp TXFMParser.hpp TXFMSB.hpp TXFMSHA1.hpp TXFMURL.hpp TXFMXPath.hpp TXFMXPathFilter.hpp TXFMXSL.hpp ../../include/xsec/transformers
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/transformers'
gmake -C dsig includes
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/dsig'
mkdir -p ../../include/xsec/dsig
cp -p DSIGConstants.hpp DSIGKeyInfo.hpp DSIGKeyInfoList.hpp DSIGKeyInfoMgmtData.hpp DSIGKeyInfoName.hpp DSIGKeyInfoPGPData.hpp DSIGKeyInfoSPKIData.hpp DSIGKeyInfoValue.hpp DSIGKeyInfoX509.hpp DSIGReference.hpp DSIGReferenceList.hpp DSIGSignature.hpp DSIGSignedInfo.hpp DSIGTransform.hpp DSIGTransformBase64.hpp DSIGTransformC14n.hpp DSIGTransformEnvelope.hpp DSIGTransformList.hpp DSIGTransformXPath.hpp DSIGTransformXPathFilter.hpp DSIGTransformXSL.hpp DSIGXPathFilterExpr.hpp DSIGXPathHere.hpp ../../include/xsec/dsig
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/dsig'
gmake -C enc includes
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/enc'
mkdir -p ../../include/xsec/enc
cp -p XSECCryptoBase64.hpp XSECCryptoException.hpp XSECCryptoHash.hpp XSECCryptoKey.hpp XSECCryptoKeyDSA.hpp XSECCryptoKeyHMAC.hpp XSECCryptoKeyRSA.hpp XSECCryptoProvider.hpp XSECCryptoX509.hpp XSECKeyInfoResolver.hpp XSECKeyInfoResolverDefault.hpp ../../include/xsec/enc
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/enc'
gmake -C enc/OpenSSL includes
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/enc/OpenSSL'
mkdir -p ../../../include/xsec/enc/OpenSSL
cp -p OpenSSLCryptoBase64.hpp OpenSSLCryptoHash.hpp OpenSSLCryptoHashHMAC.hpp OpenSSLCryptoKeyDSA.hpp OpenSSLCryptoKeyHMAC.hpp OpenSSLCryptoKeyRSA.hpp OpenSSLCryptoProvider.hpp OpenSSLCryptoX509.hpp ../../../include/xsec/enc/OpenSSL
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/enc/OpenSSL'
gmake -C framework includes
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/framework'
mkdir -p ../../include/xsec/framework
cp -p XSECDefs.hpp XSECError.hpp XSECException.hpp XSECProvider.hpp XSECURIResolver.hpp XSECURIResolverXerces.hpp XSECW32Config.hpp XSECConfig.hpp ../../include/xsec/framework
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/framework'
gmake -C utils includes
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/utils'
mkdir -p ../../include/xsec/utils
cp -p XSECBinTXFMInputStream.hpp XSECDOMUtils.hpp XSECNameSpaceExpander.hpp XSECPlatformUtils.hpp XSECSafeBuffer.hpp XSECSafeBufferFormatter.hpp XSECTXFMInputSource.hpp XSECXPathNodeList.hpp ../../include/xsec/utils
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/utils'
gmake -C utils/unixutils includes
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/utils/unixutils'
mkdir -p ../../../include/xsec/utils/unixutils
cp -p XSECBinHTTPURIInputStream.hpp XSECURIResolverGenericUnix.hpp ../../../include/xsec/utils/unixutils
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/utils/unixutils'
gmake -C canon compile
gmake[1]: Entering directory `/home/mlau/xml-security-c-1.0.0/src/canon'
g++ -O2 -DNDEBUG -Wall -fPIC -DFREEBSD -c -I/usr/local/include -I../../include -o ../../lib/obj/XSECC14n20010315.o XSECC14n20010315.cpp
In file included from /usr/local/include/xsec/canon/XSECC14n20010315.hpp:35,
from XSECC14n20010315.cpp:74:
/usr/local/include/xsec/utils/XSECXPathNodeList.hpp:181: parse error before `::'
XSECC14n20010315.cpp: In method `void XSECC14n20010315::init()':
XSECC14n20010315.cpp:358: `c14ntarget' undeclared (first use this function)
XSECC14n20010315.cpp:358: (Each undeclared identifier is reported only once
XSECC14n20010315.cpp:358: for each function it appears in.)
XSECC14n20010315.cpp:358: parse error before `('
XSECC14n20010315.cpp:359: `formatBuffer' undeclared (first use this function)
XSECC14n20010315.cpp:362: `formatter' undeclared (first use this function)
gmake[1]: *** [../../lib/obj/XSECC14n20010315.o] Error 1
gmake[1]: Leaving directory `/home/mlau/xml-security-c-1.0.0/src/canon'
gmake: *** [compile] Error 2
*/Berin Lautenbach <[EMAIL PROTECTED]>/* wrote:
Monica,
Can you remind me - is 2.1 with the old DOM_Node interface? (Nodes were not pointers, they were objects with reference counts - a kind of Java approach in C++).
If so, the released versions won't support it. (OpenSSL 0.9.6 should be fine.) Early beta code supported 2.1, but you'd need to go back into the CVS to find a version that worked, and it wouldn't be fully functional.
Cheers, Berin
Monica Lau wrote:
> Hi, > > I downloaded XSec 1.1, and it worked great with OpenSSL 0.9.7d and > Xerces 2.5. However, our code base is really out-of-date. We're using > OpenSSL 0.9.6 and Xerces 2.1. We really need to upgrade our code base, > but it might be a huge effort. Are there older versions of XSec that > would work with the above, older OpenSSL and Xerces versions? I tried > 1.0.0, but that didn't compile. > > Thanks for your help in advance! > > Regards, > Monica > > > > ------------------------------------------------------------------------ > Do you Yahoo!? > Yahoo! Mail Address AutoComplete > > - You start. We finish.
------------------------------------------------------------------------ Do you Yahoo!? vote.yahoo.com <http://vote.yahoo.com> - Register online to vote today!
