Hi,
There's no obvious reason why running your code in OrbixWeb would cause
Xerces parsing to fail - unless the ORB had an awful lot of connections
open and had used up all of the FDs. You could check your orbixweb.jar to
make sure there are no incompatable org.w3c.* or org.sax.* packages in
there that are being picked up before your xerces.jar. There shouldn't be
- the ORB itself certainly doesn't use them.
There's not much you can do until you find the underlying runtime
exception. If memory serves correct, OrbixWeb can trace the runtime
exception which forced it to throw the UNKNOWN exception. You need to turn
the ORB's trace level up to the highest level using the correct system
property - something like -DOrbixWeb.Trace=255 . Check your OrbixWeb docs
for the correct syntax. Or you could attach a debugger and wait for the
RuntimeException to be thrown.
j.
John O'Shea,
Phone : + 353 1 8154228 Email : [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
