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.
Summary: | Copy Client Binding Code and generated path problem | ||
---|---|---|---|
Product: | obsolete | Reporter: | David Kaspar <dkaspar> |
Component: | corba | Assignee: | issues@obsolete <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | non_migrated_user |
Priority: | P2 | ||
Version: | -S1S- | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
David Kaspar
2003-04-14 14:52:53 UTC
The bug is not going to be fixed for Nevada/NB 3.5. The bug is non-destructive and an easy clear workaround exists - the user has to fill the path in the code manually. The bug should be fixed for next release and is a good candidate for a Nevada patch. I'm not sure that this belongs in relnotes since the module is not a part of any standard distro at the moment. Nonetheless, I'll craft this relnote in case we do use it (Tonda and David, please verify): "In the CORBA module (only available from the Update Center), the Copy Client Binding Code command does not generate the correct path. Workaround: Fill in the missing path manually in the Source Editor." This issue affect Client Java source file generation, when you generate it using CORBA Wizard. Please, add following comment too: This affects generation of Client Java source file from CORBA Wizard. Workaround: Fill in the missing path manually in the Source Editor of Client Java source file. Problem occurs also when you generate Server source file using CORBA wizard with Naming Server binding method. Fixed in Nevada Patch 1 and in Arrow. removing RELNOTE keyword. BTW, is this also fixed in trunk? I don't think it is fixed in trunk. AFAIK corba module development is discontinued thus the fixes were not front-ported to trunk. CCing ftsust@netbeans.org for sustaining to be able to follow up on this if needed. |