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 108092 - Creating a project with visual web framework creates a non visual JSP page
Summary: Creating a project with visual web framework creates a non visual JSP page
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Quy Nguyen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-26 00:24 UTC by Jayashri Visvanathan
Modified: 2007-07-26 00:03 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
screenshot of the problem (528.93 KB, image/png)
2007-06-26 00:26 UTC, Jayashri Visvanathan 		Details
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 Jayashri Visvanathan 2007-06-26 00:24:20 UTC 
Filing this issue on behalf of Octavian:
Create NetBeans Web project and add Visual Web Framework. You get a non visual page 
by default, Page1.jsp. You cannot switch to the design view of this page.
Comment 1 Jayashri Visvanathan 2007-06-26 00:26:34 UTC 
Created attachment 44383 [details]
screenshot of the problem
Comment 2 _ potingwu 2007-06-26 00:32:55 UTC 
I also see it sometimes. It's a JSF loader issue.
Comment 3 Quy Nguyen 2007-07-17 09:44:34 UTC 
I have not been able to reproduce this problem.  Is it still occurring?
Comment 4 _ potingwu 2007-07-17 16:01:15 UTC 
I no longer seeing this issue neither.
Comment 5 Quy Nguyen 2007-07-24 08:46:51 UTC 
Closing as no one has been able to reproduce this issue recently.
Comment 6 Quy Nguyen 2007-07-25 19:13:10 UTC 
I was able to reproduce this today.  It appears that the order in which the files are generated differs between creation
of a web project with the visual web framework and the addition of the visual web framework to an existing project.
Comment 7 Quy Nguyen 2007-07-26 00:03:28 UTC 
This was caused by a jsf project API changing its implementation to read the project.xml file to determine if a given
file belongs to a visual web JSF project.  This appears to have caused a race condition, since the project.xml file is
modified during the addition of the framework, and this modification may not have been completed before the data loader
acts.

This was fixed by adding a FileObject attribute to the generated jsp/java files, so the loader does not need to read the
project.xml file.

Checking in src/org/netbeans/modules/visualweb/project/jsfloader/JsfJavaDataLoader.java;
/cvs/visualweb/project/jsfloader/src/org/netbeans/modules/visualweb/project/jsfloader/JsfJavaDataLoader.java,v  <-- 
JsfJavaDataLoader.java
new revision: 1.5; previous revision: 1.4
done
Checking in src/org/netbeans/modules/visualweb/project/jsfloader/JsfJavaDataObject.java;
/cvs/visualweb/project/jsfloader/src/org/netbeans/modules/visualweb/project/jsfloader/JsfJavaDataObject.java,v  <-- 
JsfJavaDataObject.java
new revision: 1.4; previous revision: 1.3
done
Checking in src/org/netbeans/modules/visualweb/project/jsfloader/JsfJspDataLoader.java;
/cvs/visualweb/project/jsfloader/src/org/netbeans/modules/visualweb/project/jsfloader/JsfJspDataLoader.java,v  <-- 
JsfJspDataLoader.java
new revision: 1.7; previous revision: 1.6
done
Checking in src/org/netbeans/modules/visualweb/project/jsfloader/JsfJspDataObject.java;
/cvs/visualweb/project/jsfloader/src/org/netbeans/modules/visualweb/project/jsfloader/JsfJspDataObject.java,v  <--
JsfJspDataObject.java
new revision: 1.7; previous revision: 1.6
done
Checking in src/org/netbeans/modules/visualweb/project/jsfloader/Utils.java;
/cvs/visualweb/project/jsfloader/src/org/netbeans/modules/visualweb/project/jsfloader/Utils.java,v  <--  Utils.java
new revision: 1.3; previous revision: 1.2
done