On 1/3/2011 5:24 PM, Dennis Reedy wrote:
If jsk-lib.jar is in the classpath (and by inclusion jsk-platform.jar), why do
we
> need jsk-dl.jar? Unless I'm mistaken all of the classes that are in
jsk-dl.jar are
> already in jsk-lib.jar, why is it needed?
The simple answer is that because jsk-lib.jar is optional, jsk-dl.jar needs to
be in the codebase of any service providing Entry and other classes that are in
jsk-lib.jar since a client may not use jsk-lib.jar. We can, of course argue
about how a client would make use of Entry objects in jsk-dl.jar if it did not
have jsk-lib in its classpath.
But, in the end, clients are only required to have jsk-platform.jar and so
jsk-dl.jar needs to be in the codebase of services that use jsk-lib.jar so that
the service's proxy classes will all resolve.
Gregg Wonderly
