Bug 90090 - Give more control over backing bean creation
Give more control over backing bean creation
Status: STARTED
Product: obsolete
Classification: Unclassified
Component: visualweb
5.x
All Windows XP
: P2 with 6 votes (vote)
: 6.x
Assigned To: _ potingwu
issues@obsolete
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-27 13:47 UTC by jfurmankiewicz
Modified: 2007-10-18 18:16 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jfurmankiewicz 2006-11-27 13:47:04 UTC
It would be great to allow more control over how the backing bean is created for
a new page in the visual web pack.

Right now it automatically creates a backing bean in ASP.Net style that
represents the actual physical content of the page.

This makes it unusable for a more business-flow-oriented approach, like JBoss
Seam or the upcoming Web Beans (JSR 299).

I believe when creating a new Visual JSF page, NB should prompt whether to
create an automatic backing bean (like it does now) or let you hook up your own
custom one behind it. That would immediately open a whole new range of
opportunities for using the Visual Web Pack with more process oriented web
frameworks.
Comment 1 ken_ 2006-12-05 17:27:46 UTC
Integration with SEAM would make me switch from back from IDEA to NetBeans!
Comment 2 gsteyn 2007-10-18 02:38:14 UTC
It would be nice to not automatically have every component bound to a backing bean.  Possibly allow the user to select
the option to use at page creation time, similar to JDeveloper 11g.  Binding all columns and static text fields to a
backing bean for a read-only table is overkill and makes the backing bean code large.
Comment 3 gsteyn 2007-10-18 02:39:03 UTC
It would be nice to not automatically have every component bound to a backing bean.  Possibly allow the user to select
the option to use at page creation time, similar to JDeveloper 11g.  Binding all columns and static text fields to a
backing bean for a read-only table is overkill and makes the backing bean code large.
Comment 4 _ potingwu 2007-10-18 18:16:28 UTC
Will plan for post NetBeans 6.0.


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo