[wtp-jsf-dev] RE: [Bug 154954] New: Suggestions for improving JSF Tools

["raghunathan srinivasan" <raghunathan.srinivasan@xxxxxxxxxx>]

Hi Eric,

Thanks for all the suggestions you have made. We will consider them for the 2.0. If there are bugs that you would like to be addressed in near-term, please increase the priority on them.

Thanks
Raghu Srinivasan
Project Lead - JSF Tools Project
Oracle Inc.
-----Original Message-----
From: bugzilla-daemon@xxxxxxxxxxx [mailto:bugzilla-daemon@xxxxxxxxxxx] 
Sent: Wednesday, August 23, 2006 3:45 PM
To: raghunathan.srinivasan@xxxxxxxxxx
Subject: [Bug 154954] New: Suggestions for improving JSF Tools Platform

https://bugs.eclipse.org/bugs/show_bug.cgi?id=154954
Product/Component: Java Server Faces / core

           Summary: Suggestions for improving JSF Tools Platform
           Product: Java Server Faces
           Version: 1.5
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P3
         Component: core
        AssignedTo: jsf.core-inbox@xxxxxxxxxxx
        ReportedBy: enorman@xxxxxxxxxxxxxx


A few thoughts I have had while working with the JSF Tools Platform:

1. Add some mechanism for JSF Component Libraries to be filtered out if they
don't apply to the project.  For example, if a JSF component library contains
code that will only run on a certain server runtime, it should not be visible
to projects that are using a different runtime.  Maybe use a mechanism similiar
to how a server runtime type can declare what facets it supports.

2. Add some mechanism to specify what JSF Libraries are selected by default
(and their deploy flag) when creating a new project.  Currently the selected
libraries are always empty when creating a new project.  Maybe remember the
settings from the last time the wizard was used, or have it be configurable
from a preferences page?

3. Add a mechanism to specify what JSF Impl and Component Libraries should be
selected by default when using the 'presets' and 'templates' extensions from
the 'org.eclipse.wst.common.project.facet.core.facets' extension point.

4. The JSF Libraries that are not deployed to the server should use a
IClasspathContainer instead of adding each individual jar to the classpath.
All the jars really clutter up the package explorer view unless they are
manually filtered out by user settings.

5. Ensure that the faces-config editor works better with pages that are not
implemented as jsp.  Technologies such as facelets or other xml based JSF files
are not handled well in the navigation rules tab (assumtions regarding the file
extensions of the pages).



--
Configure bugzilla e-mail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.