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 55876 - [Study] [EP-8] Not clear where the home interface is generated
Summary: [Study] [EP-8] Not clear where the home interface is generated
Status: RESOLVED DUPLICATE of bug 56662
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB Project (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Adamek
URL: http://ui.netbeans.org/nonav/usabilit...
Keywords: UI
Depends on: 56662
Blocks:
  Show dependency tree
 
Reported: 2005-03-03 14:37 UTC by jrojcek
Modified: 2005-04-07 09:27 UTC (History)
2 users (show)

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 jrojcek 2005-03-03 14:37:27 UTC
A participant couldn't find the generated home interface. He was 
looking at the session bean node and its contextual menu.

Because of this problem:
2 participants were slowed down during Task 2

Recommendation
Make the interface accessible from the session bean node.
Comment 1 Andrei Badea 2005-03-03 15:08:46 UTC
Maybe by adding actions such as "Open Local Interface", "Open Local
Home Interface" and so on to the bean node?
Comment 2 Jiri Kopsa 2005-03-18 18:54:47 UTC
There are such actions designed in the UI spec.

This issue might be seen as a duplicate of 56662 ("Context menu on the project
explorer out of UI spec"), however that issue is quite wide, so I'm leaving this
opened.

http://j2ee.netbeans.org/nonav/docs/ejb-and-web-service-ui-spec-promoe.html#Node_Individual_Session_Bean

Open
--------------
Add          >
Delete
--------------
Refactor     >
--------------
Go To Source > 

Add >
  Business Method...

Go To Source >
  Bean Implementation
  Remote Interface
  Local Interface
  Remote Home Interface
  Local Home Interface
Comment 3 Andrei Badea 2005-04-07 09:19:38 UTC
Martine, could you look at this issue? I know there has been some work in this
area, has it already been fixed?
Comment 4 Martin Adamek 2005-04-07 09:27:30 UTC
This issue addresed subpart of issue 56662, marking as duplicate.

*** This issue has been marked as a duplicate of 56662 ***