In <bfm4vv$3pd$1@news.fsu.edu> bellenot@math.fsu.edu (Steve Bellenot) writes:
>In article <3F1E2979.40205@ix.netcom.com>,
>Roy Benjamin <rbbnjmn@ix.netcom.com> wrote:
>>I'm developing a WEB service for Sun ONE deployment (AppServer7).
>>I'm developing on Windows XP Pro though will deploy on Solaris,
>>
>>There is no way to find out what classes Sun is trying to load, their
>>names etc.. or how to stop this from happening.
>
>Actually there is a way to see what files the Sun program is openning.
>One can start the program like `truss -f -o /tmp/truss.out command'
>and look at all system calls in /tmp/truss.out. Truss is a wonderful
>tool and it has many options to taylor its output.

I agree that truss is a thing of joy and beauty for native code, but it's
probably the wrong hammer to use for Java code, particularly since it is
common practice for Java classes to be grouped together in a JAR file
(glorified ZIP file) rather than stored as separate files in a directory
tree.

In this case, to add to the fun, all this is happening inside an app server
(Sun ONE), which if it's like other app servers probably has multiple levels
of classloaders with interesting semantics.


Thomas Maslen
maslen@pobox.com