I am perfectly aware of what JAXP is having written a JAXP compliant parser myself.You can use JAXP which enables you to write code independent of Vendor Parsing API's(Crimson, Xerces...etc)
If JAXP API Impmentations are used.. you can use any parser you want.That is the big if. Just because someone is using a JAXP compliant parser doesn't mean they are using only the JAXP APIs.
However, all of the above is moot if Macromedia only supports Crimson. We were working with Macromedia on integrating one of our products when we discovered that CFMX had a dependency on Crimson, which was problematic for us since our product had a dependency on Xerces. We suggested to Macromedia that if CFMX was to be a platform for web applications then it couldn't enforce dependencies like that on applications it is bundled with. I was told over the phone by Mike Nimer that when Macromedia first released CFMX they allowed any XML parser to be used, but they were having support issues that they determined would be best resolved by forcing CFMX to use Crimson. Thus, as of CFMX for J2EE phase 2, Crimson was required.
Matt Liotta President & CEO Montara Software, Inc. http://www.MontaraSoftware.com (888) 408-0900 x901
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
