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 92963 - Root methods Selection problem for compound projects
Summary: Root methods Selection problem for compound projects
Status: STARTED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Petr Cyhelsky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-22 15:02 UTC by Alexander Kouznetsov
Modified: 2012-08-01 08:33 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-01-22 15:02:07 UTC 
Profiler 070122
NetBeans IDE Dev (Build 200701211900)
1.5.0_10; Java HotSpot(TM) Client VM 1.5.0_10-b03
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251
Sun Java System Application Server Enterprise Edition 9.1 (build b28)

Steps to reproduce:
- Open OrderSystem Sample Application
(http://www.netbeans.org/nonav/issues/showattachment.cgi/37566/order_system.zip).
As any general Enterprise Application it includes EJB module and Web module
projects as part of it.
- Open org.shop.OrderBean of its web module
- Navigate to save() method
- Right-click it and select Profiling > Add As a Profiling Root Method

ISSUE: User wants to select this method for the whole application project, but
it is added only for Web Module Project. Moreover, in Select Settings
Configuration dialog there is no information what project is going to be
affected. This could be misleading. There is no way to specify OrderSystem
Project instead of its web-module's project.
Comment 1 J Bachorik 2007-02-15 12:55:27 UTC 
reassigning
Comment 2 J Bachorik 2007-02-15 12:56:14 UTC 
starting
Comment 3 J Bachorik 2007-02-15 20:36:20 UTC 
The org.shop.OrderBean class belongs to the EJB module. The fact that you can
access the class from the encompassing enterprise app project doesn't make it
belonging to the enterprise app projest. Thus adding the root method to the EJB
module is completely valid.
What we would need to have here is to propagate the root methods defined in all
subproject to the top enterprise application when it's run. This would better
reflect the nature of the enterprise app project - being a pure container for
other j2ee modules.
Based on these facts changing this issue from DEFECT to ENHANCEMENT as
Comment 4 Alexander Kouznetsov 2007-03-28 21:29:03 UTC 
I believe this is fixed, at least partially, isn't it?
Comment 5 Alexander Kouznetsov 2007-03-28 21:31:13 UTC 
Oops, sorry. Don't take my previous comment into account. This issue has not
been fixed yet.
Comment 6 Alexander Kouznetsov 2007-07-05 17:27:48 UTC 
Since Issue 98978 is fixed it seems to be logical to fix this issue in the same manner as well. Just my 2 cents.
Comment 7 Tomas Hurka 2009-04-08 10:12:27 UTC 
Target milestone cleanup.
Comment 8 Tomas Hurka 2009-04-08 12:55:30 UTC 
Milestone cleanup: future->next
Comment 9 J Bachorik 2012-08-01 08:33:59 UTC 
changing owner