-
Bug
-
Resolution: Fixed
-
P4
-
1.2.0, 1.3.0
-
fcs
-
x86, sparc
-
solaris_7, windows_nt
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2028271 | 1.3.0 | Ken Cavanaugh | P4 | Resolved | Fixed | fcs |
Name: rlT66838 Date: 07/26/99
The idlj compiler associated with RMI/IIOP generates stubs that
form requests that always require a response, even if the
IDL for the operation specified that it was a oneway.
This appears to be a simple oversight that should be easy
to correct in the IDL compiler's code generation.
(Review ID: 88419)
======================================================================
Name: krT82822 Date: 09/09/99
Using idlj IDL-to-Java compiler, version
IDL-to-Java compiler (portable), version "3.0"
produces the same java code output for any two method signatures of the form:
void <method_name>(<args>);
and
oneway void <method_name>(<args>)
. The result is that when calling a method declared as oneway, the calling program waits for the supposedly oneway method to finish before continuing.
I assume this bug is platform-independent but have only tested it on Intel platforms (both Win95 and Win NT)
(Review ID: 95047)
======================================================================
- backported by
-
JDK-2028271 RMI-IIOP idlj compiler generates bad code for oneway operations
-
- Resolved
-