The xerces problem in Sun ONE

Question

I'm developing a WEB service for Sun ONE deployment (AppServer7).
I'm developing on Windows XP Pro though will deploy on Solaris,
Sun AppServer7 includes a XercesImpl.jar in share/lib. 2 kb
different than the one I usually use (xerces-2_1_0).
If I compile all my code against the Sun xerces implementation, I get a
class-def-not-found-error when trying to write any XML output.
java.lang.NoClassDefFoundError: org/apache/xml/serialize/XMLSerializer
com.accelere.server.kernel.subscriber.FileSubscriber.write(FileSubscriber.java:123)
com.accelere.server.kernel.subscriber.FileSubscriber.process(FileSubscriber.java:100)
com.accelere.server.kernel.subscriber.AbstractSubscriber.run(AbstractSubscriber.java:155)
its really curious since I have no trouble with this running -outside-
of Sun ONE. I've tried everything I can imagine to try to get this to
work. I've put the real xercesImpl.jar in my WEB-INF/lib dir. I've
put Sun's there. I've put mine in place of Sun's.. you name it...
I've even blended the two jars together... Of course, both jars **do**
in fact contain a complete set of xerces classes, including the
XMLSerializer.
If I compile my our code against the normal xerces distribution I can't
load/read any XML in the AppServer 7 environment. This occurs because of
a class-def-not-found-error when trying to parse -any- XML input.
Documentbase not found... Sun sets the property.. then doesn't set
it back. I have no clue or idea of how to find outr which jar I'd
need of theirs to have their mystery class in my path.... Of course,
If I could create an instance of DOMParser I could query it for its
proerties, but these methods are not static.. and I through a class
not found exception when trying to make one.
There is no way to find out what classes Sun is trying to load, their
names etc.. or how to stop this from happening.
Does any one have a clue of how to work around this problem? Of course
Tomcat works fine.... but its not what the customer has specified.

Answer 1

The directory server reports all connections, requests and results in the logs/access file (under the instance directory).
All errors are reported in the logs/errors file.
Additional messages can be generated by changing the errorlog level and infolog levels via the Console, or via LDAP. Please refer to the Administration Guide and the Reference Manual for the details.
Regards,
Ludovic.