Re: River and Backward Compatibility
Greg Trasuk <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <1189021518.25074.127.camel@cameron> |
When we talk about the package names changing, we are talking about changing the com.sun.** classes to org.apache.** (at least that's what I'm talking about). Myself, I don't have a lot of references to com.sun.* classes, as they are mostly implementation (same as a servlet application has few references to org.apache.tomcat.* classes). As far as I'm concerned, River doesn't need to change the net.jini.* namespace any more than Tomcat has to change javax.servlet.*. In other words, it shouldn't. Am I mistaken, anyone? Cheers, Greg. On Wed, 2007-09-05 at 15:22, levmatta wrote: > To people FOR compatibility I have a question. > > How is backwards compatibility going to be achieved if the package name is changing? > Doesn't that blow the hole thing into pieces: > - compiling does not work (but this could be a simple refactoring step) > - running does not work, because class lookup will fail > > Realizing that in a production environment, one may not be able to recompile everything!!!! > > Chears > > -------------------------------------------------------------------------- > Getting Started: http://www.jini.org/wiki/Category:Getting_Started > Community Web Site: http://jini.org > jini-users Archive: http://archives.java.sun.com/archives/jini-users.html > Unsubscribing: email "signoff JINI-USERS" to [email protected] -- Greg Trasuk, President StratusCom Manufacturing Systems Inc. - We use information technology to solve business problems on your plant floor. http://stratuscom.com -------------------------------------------------------------------------- Getting Started: http://www.jini.org/wiki/Category:Getting_Started Community Web Site: http://jini.org jini-users Archive: http://archives.java.sun.com/archives/jini-users.html Unsubscribing: email "signoff JINI-USERS" to [email protected]