[news.eclipse.webtools.jsf] Re: How to attach source of JSF implementati

[cameron.bateman@xxxxxxxxxx (Cameron Bateman)]

> I've created a dynamic web app, with JSF 1.2 as one of the facets.  As a 
> result, the JSF implementation (Sun's) is not available as a normal User 
> Library.  I guess it has to be this way in order for the JSF tooling to 

Can you walk me through the "as a result" part?  The JSF 1.2 facet should 
not stop you from having anything that you want on your classpath.  One 
issue that arises with JSF 1.2 is that if you are using a JavaEE 
container, then the JSF runtime is expected to be already there, so in the 
JSF libraries setup you can select "Server Supplied JSF Implementation" to 
indicate you don't want your own on the classpath.  Then you need to be 
sure that your target runtime container is on the classpath.  You can do 
this from the new project wizard or afterward by going to the Project 
Properties menu and going to "Targeted Runtime".  Your selected runtime 
should show up in the Navigator (either right under the project in the 
Package Explorer or under Java Resources/Libraries in the JavaEE Project 
Explorer).

I know this doesn't address your source attachment problem, but hopefully 
goes a little further toward explaining our intent.  Note that in this 
situation, JSF libraries are still useful (your source attachment bug not 
withstanding) for deploying third-party components like Trinidad.


--Cameron