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 113015 - RFE: Change the Visual Web design time system to not require bindings for every tag and component in the JSP
Summary: RFE: Change the Visual Web design time system to not require bindings for eve...
Status: NEW
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker with 1 vote (vote)
Assignee: Mark Dey
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-16 15:39 UTC by rdelaplante
Modified: 2007-08-16 15:39 UTC (History)
1 user (show)

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 rdelaplante 2007-08-16 15:39:03 UTC 
Many developers I've talked to who have used Visual Web Pack (including myself) do not like how it binds every component
and tag on the page.  This is not required by JSF. It causes a lot of bloat in our JSPs and code.  This is especially
troublesome when I want to copy/paste sections of HTML from one page into another.  I have to re-create all of the
components (such as 20 StaticText components) and do a bunch of fiddling with the raw JSP.  

I understand that the VWP design time system requires bindings to work, and think that it needs to change.  There should
be no bindings for any tag or component by default.  If a developer wants a binding so that (s)he can access it from
code, then provide a way for the developer to have VWP create a binding.  The developer might right click the component
or tag from the outline pane, or right click a selected component from the visual designer.  Clicking on a "Create
binding" context menu item would create the binding.

When thinking of ways to find the corresponding component from the tag itself (via tld and faces-config.xml), instead of
the getters/setters for the component, keep in mind the changes coming in JSF 2.0.