This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
1) The Module doesn't create an "RMI-IIOP Stub Compiler". 2) All RMI Projects/servers use the RMI Stub Compiler by default, even if you've created an RMI-IIOP server in the wizard. 3) Better support for RMI-IIOP clients. I'd suggest the module create an RMI-IIOP Stub Compiler. This being the same as the vanilla RMI Compiler but with the additional -iiop flag. This flag is needed to generate code compatible with the tnameserv server. I'd suggest that if the system knows it's creating an RMI-IIOP server that it, not only generate correct server code, but that it use this new compiler (to compile Stubs) which will generate the proper stub and tie files. As it is now the module tries to compile RMI-IIOP stubs with the RMI stub compiler. The compilation works, but the user will get run time errors trying to register with the JNDI registry. There error is something like, "only objects of type org.omg.CORBA.Object can be exported". Generally enhance support for RMI-IIOP or JNDI clients. Support for clients using the standard RMI registry looks good. But there is no support (I could find) for Java clients connecting to an RMI-IIOP server. Sure it's easy enough to cut and paste relevant code from the server Impl to the client and add the line or two of JNDI client code, but this is confusing for beginning users. And more work for other users, who would like the IDE to do this for me. :)
Target milestone -> 3.3
1) and 2) fixed in main trunk (will be available in Release 3.3) 3) it is already possible to use JNDI browser which allows to copy/paste lookup code
verified
Resolved for 3.4.x or earlier, no new info since then -> closing.