i've seen issues with Crimson on the client-side and require all my
clients to use xerces or else. in fact i specifically remember a bizare
xml-sig bug that immediately went away when i got xerces in my
client-side classpath.
Shawn McKinney wrote:
--- "Dittmann, Werner" wrote:
I see two problems here...
- first your server uses the Crimson XML Parse
In this case, the Crimson parser was on the
client-side, but that probably wasn't clear from how I
presented the info.
the stack trace shows that the Merlin class cannot
be
instantiated, this is usually due to that fact that
some resource cannot be found, most often the
keystore is not on a path (classpath, or relative
file system path) that is searched.
Yup, exactly right in that case - It was classloader
issue. I moved server-side keystore to new location
and problem fixed.
Thanks for the help Werner,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
