Naming.rebind("ABC",new MyImpl()) creates a registry entry
called "BC", because RMI Naming always assume the '/' must be removed.
==========
In kestrel build H the method java.net.URL.getFile() when invoked on a URL created as follows:
new URL((URL("http:"), "ABC")
will return, "/ABC" however, in build kestrel build L, then same method will return, "ABC". Because of the behavior in Naming.java described above (a preceding slash is always assumed), remote object names in Naming URLs can be corrupted (as above, the first character of remote object names is removed).
In question here is what is the correct behavior? Should the URL file name always start with a '/'. If not, then the latest URL fix is correct but apparently not backwards compatible.
lairdd@east 1999-07-16
called "BC", because RMI Naming always assume the '/' must be removed.
==========
In kestrel build H the method java.net.URL.getFile() when invoked on a URL created as follows:
new URL((URL("http:"), "ABC")
will return, "/ABC" however, in build kestrel build L, then same method will return, "ABC". Because of the behavior in Naming.java described above (a preceding slash is always assumed), remote object names in Naming URLs can be corrupted (as above, the first character of remote object names is removed).
In question here is what is the correct behavior? Should the URL file name always start with a '/'. If not, then the latest URL fix is correct but apparently not backwards compatible.
lairdd@east 1999-07-16
- relates to
-
JDK-4251878 java.rmi.Naming shouldn't rely upon the parsing functionality of java.net.URL
- Resolved