Community
Participate
Working Groups
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).
One more for the list: It would be nice if there was some action in the UI that would copy the jars from a set of JSF component libraries to the 'shared' jars folder of the target server runtime to make it easier to use component libraries that are not deployed inside each war file.
On behalf of kiril mitov from a post regarding JSF library in jsf newsgroup. Here is the link of original post. http://www.eclipse.org/newsportal/article.php?id=364&group=eclipse.webtools.jsf#364 -------------- Following the tutorial: http://www.eclipse.org/webtools/jsf/dev_resource/JSFTutorial-RC3/JSFTools_tutorial.html I can set the apache commons, jsf and jstl tag libraries. I would like to provide the user with a product of mine that includes the jsf plugins along with my own. The commons libraries can be found in org.eclipse.tomcat plugin so i prefer not to make the user download them but to rather specify those libraries in the JSF Libraries preference page. What I would like to do is my application to have this settings preconfigured. I mean that my application is just a zip file. The user extracts it lets say at /home/kiril, the eclipse directory is created and when the user starts /home/kiril/eclipse/eclipse the commons libraries that are located in /home/kiril/eclipse/plugins/org.eclispe.tomcat/ are automaticaly located and put in the preference page. Another user lets say can extract the zip file in c:\work\ so the preference page must show the commons libraries located in c:\work\eclipse\plugins\org.eclipse.tomcat\ So I would like in some way make the location (that is specified in the JSF Libraries preference page) relative to the install location of the platform I have looked at the workspace/.metadata/.plugins/org.eclipse.jst.jsf.core/JSFLibraryRegistry.xml file and it seems that this file specifies the location of the libraries. I have tried setting the "SourceLocation" as: SourceLocation="./plugins/org.eclipse.tomcat_4.1.130.v20060601/commons-collections.jar" but this does not seem to work. I noticed the "RelativeToWorkspace" attribute. Is there an attribute that can do the same but make the location "RelativeToEclipseHome"? Or is there another way to achive the desired functionality?
review
Deferred due to lack of resources. Contributions from the community would be welcomed.
