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 90010 - Unify different JSF project options
Summary: Unify different JSF project options
Status: RESOLVED WONTFIX
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Alexey Butenko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-24 13:41 UTC by jfurmankiewicz
Modified: 2016-07-07 08:55 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
Wizard panel mockup (24.02 KB, image/jpeg)
2006-11-24 13:41 UTC, jfurmankiewicz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jfurmankiewicz 2006-11-24 13:41:14 UTC
Right now, the JSF development options in NetBeans are in danger of getting
confusing (e.g. ability to create either a JSF vanilla or JSF Facelets project,
or an ICEFaces JSF project via an externa plugin). Soon we could have the
incoherent mess that is more typical of Eclipse plugins.

I thing it would be useful to have only ONE JSF web app wizard and instead keep
adding to it (and maybe expose this is an API that other vendors / module
developers can plug in to), so that there is always a consistent set of logic
for creating JSF apps. I suspect it would need to provide an option for view
(JSP or JSP/Tiles or Facelets), Components (JSF RI or Apache MyFaces), AJAX
options (Ajax4JSF or DynaFaces) and optionally a way to add support for 3rd
party JSF component libraries (MyFaces Tomahawk, ICEFaces, etc.)

I am imagining something like in the screenshot attached below (would replace
the current JSF wizard panel when creating a new web app).
Comment 1 jfurmankiewicz 2006-11-24 13:41:40 UTC
Created attachment 36267 [details]
Wizard panel mockup
Comment 2 Petr Pisl 2006-11-27 07:36:39 UTC
Thanks for the suggesting solution. I want to solve the problem for NetBeans
6.0. My idea was that the solution should be done through NetBeans web API.
Frameworks api is a part of this.
Comment 3 jfurmankiewicz 2006-11-27 13:41:09 UTC
You're welcome. I'm glad you guys are aware of this issue, we would want NB to
keep its consistent, easy-to-use-out-of-the-box experience. Cheers, Jacek
Comment 4 Petr Jiricka 2010-07-12 15:16:36 UTC
With JSF 2.0, what part of this is still valid? "AJAX Options" is probably not needed, and the JSP vs. Facelets option is already handled. Probably the main missing part is the 3rd party  component libraries, right?
Comment 5 Martin Balin 2016-07-07 08:55:54 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss