IAM
======
Name:		Netbeans Visual Web 6.0
Submitter:	Chau Nguyen
Owner:		Joelle Lam
Interest:	mark.dey@sun.com, Jayashri.Visvanathan@Sun.COM, ch.nguyen@sun.com
Status:         closed approved fast-track 09/04/2007
Exposure:	open
Comment:	dependencies can be found: http://jupiter.czech.sun.com/wiki/view/Netbeans/NB6ARCCases


SUMMARY
=======
	  The NetBeans Visual Web project enables Java developers
	  to rapidly build standards-based web applications in
	  NetBeans by dragging and dropping components and data
	  sources on the WYSIWYG Visual Editor.  It provides a
	  comprehensive library of JavaServer Faces components and
	  deploys your projects as a Web Archive (WAR) to Java
	  Enterprise Edition containers like Java System Application
	  Server, JBoss, BEA WebLogic, IBM WebSphere, Tomcat, and
	  others.

	  Visual Web in NB 6.0 is a continuation of Visual Web pack
	  (VWP) in NB 5.5 or 5.5.1 to bring over the missing features
	  which already exist in the Creator product.  This is one
	  of the neccessary steps to migrate Creator users to NB.
	  The project team is planning to EOL Creator product and
	  will submit a different case for that in the near future.


ISSUES
======
2007/428 Visual Web

csk-04: What is the current status of the Design Time (JSR 273) API impl?
        Is that JSR final?

	This TSR is stagnant.  How are you using API and how is it exposed to users?

ANSWER:	We use the API during Design Time for users when inside IDE you 
	drag/drop componenets. It plays the appropriate set of components for 
	that set of projects.

JL:	Who consumes Design Time? 
ANSWER:	Visual Web projects consume Design TIme.
	Design time API is consumed by Component authors.
	 can create bean info to exhibit certain kinds of behavior. 
	This includes code generation. 
	JSR 273 was an intiative to get Design Time standardized.
	It is not finalized.
	
CK:	What role does Design TIme play when done with IDE?
ANSWER:	Supporting Design TIme behavior in IDE.

EDH:	Can a 3rd party developer create a module via JSR 273?
ANSWER:	Plan is to support JSR 273 for backwards compatibility.


csk-05: In the exported interface table several interfaces (Data Provider, 
        jsfcl, Application Model, Webui Components, etc) do not provide
        a specification.  The comments have this note: "same as in 
        Creator / VWP 5.5".  

ANSWER:	They have not changed.

        Does this mean these interfaces are being over from Creator/ VWP
        unchanged?  The interfaces are identical to what was in Creator/
        VWP 5.5?
	

csk-06: The exported interface table has something called "Error Handler".
        With this comment: "Internally used by Visualweb only but being 
        bundled in the users' apps."   So is this interface available
        for external use or it is really private to our implementation?

ANSWER:	This API is internal. Not designed for external use. 

csk:	Is it documented? How will they know it exists?

ANSWER:	This API is used for debug / error reporting during deployment.
	Customers should not be concerned with it.
	It will be replaced in NetBeans.
	Change to private interface.

edh:	Woodstock components may have changed from 5.x to 6.0. Have they changed in a compatible way?
ANSWER:	Components are compatible. Some changes to scheming.


THE NEXT STEP
=============
csk-06: "Error Handler" Change to private interface.
Approved.