deployment problem - due to XML parser ?

["Jozef Aerts - Comp.Chem.Cons. - XML4Pharma" <co...@hotmail.com>]

Hi,

I made an application to sign XML documents.
When running in my IDE (JDeveloper with j2sdk1.4.1) everything works fine.
After deployment however, when verifying a signed document, sometimes the 
signature (enveloped) is defined as being valid, in other cases, it is not 
(seems to be more or less random).
I already noticed however that in the deployed version, my DOM document is 
given as a org.apache.crimson.tree.XmlDocument, whereas this is not the case 
when running in the IDE.
I presume (but I am not sure) this is the cause of the problems. Could I be 
right ?
How can I tell the application NOT to use Crimson (I also deployed 
Xerces.jar and XercesImpl.jar from the xml-security distribution) ?
Or should I more strictly define every instance of a DOM document ?

Anybody having good advice for me ?

Sincerely

Jozef Aerts
Computer Chemistry Consultancy - XML4Pharma
Switzerland





_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE* 
http://join.msn.com/?page=features/junkmail

Re: deployment problem - due to XML parser ?

[Harmeet Bedi <ha...@kodemuse.com>]

----- Original Message -----
From: "Jozef Aerts - Comp.Chem.Cons. - XML4Pharma"
> After deployment however, when verifying a signed document, sometimes the
> signature (enveloped) is defined as being valid, in other cases, it is not
> (seems to be more or less random).

Random nature of failure indicates to me that this problem is not related to
xml parser - xerces or crimson. It may be something to do with data.

Possibly a silly advice, but one thing to try out may be - remove any
unnecessary white spaces(tab, line feed etc) in the original and signed xml
doc.
I believe you can control this at the time of xml document serialzation. I
think the option is javax.xml.transform.OutputKeys.INDENT

Harmeet