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.

Bug 232168 - F1 help topic "Exported Services" has no map id
Summary: F1 help topic "Exported Services" has no map id
Status: RESOLVED FIXED
Alias: None
Product: usersguide
Classification: Unclassified
Component: Mobility (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: AlyonaStashkova
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-02 18:35 UTC by jlawless3
Modified: 2013-07-09 10:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jlawless3 2013-07-02 18:35:10 UTC
In org/netbeans/modules/mobility/project/docs/ui in org-netbeans-modules-mobility-javahelp.jar, the file, wizard_wcwexportedservices.html is not mapped.

Topic is titled: Java ME Wireless Connection Wizard Exported Services.
User is to told to access this page by:
1. Select a mobile project
2. Choose File > New File
3. Select MIDP category and then Mobile Enterprise > Wireless Connection Wizard.

First, there is no MIDP category. Category is now labeled CLDC. There is no
Mobile Enterprise subcategory.

This wizard page lets user generate client-side classes and a servlet that delegates client request to enterprise services. Specifically, user selects enterprise methods to export to a MIDP client.

If this wizard page is obsolete, I will delete the file. If this page is still valid, it needs a map id and I need someone to tell me how to access it.

Discovered in NetBeans build nbms-and-javadoc-11189-on-20130624 on June 24, 2013.
Comment 1 Kenneth Ganfield 2013-07-04 15:08:26 UTC
Alyona,
can you evaluate this and see if this topic is still applicable to 7.4.
If it is, please assign it to a suitable engineer
Comment 2 AlyonaStashkova 2013-07-08 08:51:39 UTC
Help id requested.
Comment 3 AlyonaStashkova 2013-07-09 10:32:08 UTC
The dev confirmed that the topic is outdated and can be deleted.
Closing the issue as fixed.