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.
Web services needs a way to programatically turn off the detect rmi option. Otherwise users get prompted to set RMI; if they do this it causes problems with deployment. I logged this as a P1 because the out of the box web service experience is broken by rmi. This needs to be resolved. Here is an email trail on the topic. Hi Rico, I think that you have discovered quite serious issue. As both RMI and JAXRPC use the same model, eg. interface described by an extension of java.rmi.Remote and its implementation, there should be a common model that would provide unified UI and allow user to choose an implementation or another application would generate appropriate implementation. Such model definitely requires deep cooperation between NetBeans team that is responsible for RMI module and your team. However, your request is coming very late in the release cycle - I'm not sure whether we are able to create such model. Regarding your request to disable a feature - there may be serious consequences caused by disabling a feature : - other features may be affected - documentation should be updated - testsuites should be updated - additional testing should be done .... I think it is unacceptable to disable any module. Regards, -Martin Lark observed there is an option to turn off RMI file detection in the RMI module configuration. This seems to address this issue in a satisfactory way. Unless you know of an issue with this approach, we will recommend that web service developers turn off the detection hook in the install guide/release notes and figure something more definitive out for Dublin. OK? Peter Technically, it is possible. However, the feature is documented in help as turned on by default. I don't know how much users use this feature but I seen several bug reports after the feature had accidentaly been turned of in one of the development build of NetBeans so I would expect similar bug reports if we disabled it in Sierra. Also, validation kits should be updated. I don't know what else might be affected - I think that correct process would be to take it to Sierra p-team and get an approval from it. Regards, -Martin Hi all, I absolutely support that what Martin suggests. Just a summary of possibilities we discussed with Tomas and Dusan: 1. Create service type which will allow other modules to cooperate on RMI object recognition. (cca 1 developer/month) 2. Other modules can use RMISettings to disable the functionality for the current (JAXRPC) project. (should be relatively easy, but resulting in limited RMI functionality in this project) 4. Disable the function in the global settings. FUNCTIONALITY LOST!!!!!!! 5. Disable RMI module as such. RMI is a base for the all parts of Sun Network Architecture (J2EE (EJB), J2EE CORBA, JINI)!!!!! Let me know what option you would prefer? Daniel We were proposing to recommend in the release notes that web services developers manually turn RMI detection off. We were not suggesting trying to turn it off automatically. As far as a longer term solution, one recommendation would be to have the .rmi file include an "off" or "on" keyword...this way we could just deposit a .rmi file with the word "off" in it when we create the servant. Peter
Changed to enhancement. Actually, this functionality is likely to be changed in NB 4.0 but it still requires close cooperation between rmi developers and s1s web services team.
This issue needs to come back to the forground. For performance reasons RMI was going to be removed from EE's next release. It is no longer clear to me that this will still happen. If it does not this issue needs to be dealt with in a way that allows web service customers to use the product with out disabling RMI detection.