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 89693

Summary:	'Bean' nodes redesign, was Netbeans Project File get corrupted
Product:	obsolete	Reporter:	spattabi <spattabi>
Component:	visualweb	Assignee:	_ potingwu <potingwu>
Status:	STARTED ---
Severity:	blocker	CC:	emononen, potingwu, rdelaplante
Priority:	P3
Version:	5.x
Hardware:	All
OS:	Windows XP
Issue Type:	ENHANCEMENT	Exception Reporter:
Bug Depends on:
Bug Blocks:	90668

Description spattabi 2006-11-20 16:37:59 UTC

Hi,
I have multiple instances where a netbeans project file gets corrupted. To 
reproduce, pick the Netbeans visual development pack. Create a web 
project..Create fewpages and deploy. 

Go to the source view, change the default sessuon bean "SessionBean1" 
to "WhateverNameBean" and refactor the rest.
Try building and close open.

Now your project won't show session beans. Also when you try opening the 
Session bean it will give javax.faces.FacesException(Unable to import and Jar 
not found).
Your well working project start functioning strange. You got to throw away the 
project.

I have numerous instances project functioning strange. The best thing I do is 
Just go to eclipse and remain with eclipse. Never Trust Netbeans!!! Beware of 
Netbeans!! This is my inner feeling.

Serious issues are not closed.

Comment 1 Erno Mononen 2006-11-27 12:55:55 UTC

Reassigning to visualweb for further evaluation.

Comment 2 Erno Mononen 2006-11-27 12:57:01 UTC

Some additional info: I was able to reproduce this, the bean does seem to get
renamed correctly, but after renaming the bean and closing/reopening the project
the session beans view has disappeared. I didn't get that exception when opening
it though.

Comment 3 _ potingwu 2006-11-27 18:45:40 UTC

Looks like Visual Web Pack has some code-insync issue when refactoring
session/application/request bean files. When I rename SessionBean1.java to
MySessionBean.java, one page bean file has the following codes:
    protected SessionBean1 getSessionBean1() {
        return (MySessionBean)getBean("SessionBean1");
    }

However, I don't see any exceptions! And The bean node is still visible. The
Beans view will be redesign for the future release anyway.

The issue is the refactoring for bean files. The workaround to fix your project
is to manually change all 'SessionBean1' to 'MySessionBean'.

Comment 4 _ sandipchitale 2006-11-29 17:12:15 UTC

I was not able to reproduce the Session bean accessor not getting renamed 
problem. The SessionBean1 disappearing after being renamed to MySessionBean 
has something to do with project code looking for names starting with 
SessionBean*. Also the javax.faces.FacesException seems like a problem with 
JSF library being removed from the project. Was the App server changed?

Comment 5 _ potingwu 2006-12-04 17:58:45 UTC

Refactoring issue has been fixed and will be in the final release. The root node
disappear issue will be redesigned in the next release.

Comment 6 _ potingwu 2006-12-07 18:47:49 UTC

Because VWP allows to add new request, session and application scope managed
beans, we may need to change the 'Bean' node to a folder because we don't want
to mess up the project root view.