Re: River and Backward Compatibility

Brian Murphy wrote:
> Related to this, for as long as the jsk-* jar files have been
> available, I've been a little surprised by how many people
> have stated on this and similar threads that they still develop
> and/or deploy using jini-core.jar, jini-ext.jar, and sun-util.jar files,
> rather than converting to using jsk-platform.jar, jsk-lib.jar, and
> jsk-dl.jar. I certainly understand that most people still don't read
> the documentation -- in particular, the release notes -- but I
> would have thought that by now most would have made the
> change.

I've used both sets of files from time to time.  I still choose to use the old
files because it 'widens' the platform view where as 'jsk-platform.jar' narrows
that view and I think that the entire set of classes are a more appropriate set
of files for my needs.  I do use jsk-dl.jar in my codebases, because that's
easily done compared to building new -dl.jar files for each JTSK service which
would include all jars.  I don't know the real dependencies for those services,
so I rely on what is built already.  For my services, I don't want to keep
fighting the (ridiculous it seems at time) battle of trying to figure out where
all the Entry objects are and everything else thats not in jsk-platform.jar.

Gregg Wonderly

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html