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 90668 - There appears to be no way to add new request, session and application scope managed beans
Summary: There appears to be no way to add new request, session and application scope ...
Status: RESOLVED WORKSFORME
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 5.x
Hardware: Other Windows XP
: P3 blocker (vote)
Assignee: _ potingwu
URL:
Keywords:
Depends on: 89693
Blocks:
  Show dependency tree
 
Reported: 2006-12-06 15:24 UTC by rdelaplante
Modified: 2007-01-26 20:36 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
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 rdelaplante 2006-12-06 15:24:25 UTC 
When I right click the "Request Bean", "Managed Bean" or "Session Bean" nodes,
there is no menu option for me to add a new bean.  My only choice is to rename
the existing bean. 

When there are no beans, the entire node dissapears.  For example, if I rename
SessionBean1 to FooBean1 using the refactoring tool, close the IDE and say
answer no to the save prompt for managed-beans.xml, reopen the IDE, the Session
Bean node is missing.  I have to manually edit the managed-beans.xml to fix it.
Comment 1 rdelaplante 2006-12-06 15:35:59 UTC 
I was wrong about being able to make the renamed bean re-appear after manually
fixing managed-beans.xml.   Just now I renamed ApplicationBean1 to FooAppBean,
closed the IDE, saved changes to managed-beans.xml, then re-opened the IDE.  The
"Application Bean" node is now missing. I did not add or change any code in the
original ApplicationBean1. managed-beans.xml shows the correct new name and class.
Comment 2 _ potingwu 2006-12-06 17:10:02 UTC 
You can create a new request, session or application scope managed beans by
using the 'template'. Try right click on the source package node and select
New->File/Folder and choose category Managed Beans, then you will see the template.

For the issue of 'node disappear' after removing the 'root' beans is a known
problem that we will redesign in the next release. Currently removing the root
beans is not allowed.
Comment 3 rdelaplante 2006-12-06 19:02:29 UTC 
Ok thanks.  I created a new Visual Web Application project, went to the sources
folder and did as you described.  I added a new session bean, and the .java file
appeared in the package.  It also appeared in managed-beans.xml.  It did not
appear under the "Session Bean" node. Maybe this is part of the known issue. 

Could you please point me to the ticket(s) related to node dissapear after
removing the root bean so that I can set myself as a CC?  Could you also please
give me an idea when the next version might be availabe?  Thanks.