-
Bug
-
Resolution: Won't Fix
-
P5
-
None
-
1.4.0
-
generic
-
generic
Currently, a lot of the serialization code assumes that the codebase
will be included in the IOR. However, in the POA case, the server
doesn't have enough information to determine a codebase to send.
The client code should fall back onto the connection's CodeBase
interface.
Also, several places in the code assume that Util.getCodebase(repId)
will return the remote codebase when it only returns the local codebase.
Thus, the downloader must set its javax.rmi.server.codebase variable.
In real situations, the downloader doesn't know that information.
Please contact Tuong Nguyen for a test case, or modify the one in
rip-int's test/src/share/classes/corba/codebase to only give the
javax.rmi.server.codebase property to the sender rather than the
receiver.
will be included in the IOR. However, in the POA case, the server
doesn't have enough information to determine a codebase to send.
The client code should fall back onto the connection's CodeBase
interface.
Also, several places in the code assume that Util.getCodebase(repId)
will return the remote codebase when it only returns the local codebase.
Thus, the downloader must set its javax.rmi.server.codebase variable.
In real situations, the downloader doesn't know that information.
Please contact Tuong Nguyen for a test case, or modify the one in
rip-int's test/src/share/classes/corba/codebase to only give the
javax.rmi.server.codebase property to the sender rather than the
receiver.
- relates to
-
JDK-4490135 RMI-IIOP without POA stub downloading broken (no codebase in IOR)
- Closed
-
JDK-4501598 Valuetype Impl downloading in Javaidl case is broken
- Closed