[JamesWoodward]

Hi,

Is there a way that I can get JSP Content Assist to function without needing to have the JARs in the WEB-INF/lib folder of my project?

Alternatively, is there a way I can have the JARs in my project’s WEB-INF/lib folder so Content Assist works, but exclude them from being deployed to the WAR file?

The reason I ask is that JBoss 4.0.3 includes the MyFaces JARs in the jboss-4.0.3/server/all/deploy/jbossweb-tomcat55.sar/jsf-libs folder. This folder allows you to share any JARs deployed here between multiple applications. If you also edit jboss-4.0.3/server/all/deploy/jbossweb-tomcat55.sar/conf/web.xml to add more tagLibJarN initParams you can deploy shared Taglibs such as JSTL and ADF Faces JARs here too.

<init-param>
         <description>MyFaces TLDs</description>
         <param-name>tagLibJar0</param-name>
         <param-value>jsf-libs/myfaces-impl.jar</param-value>
      </init-param>
      <init-param>
         <description>JSTL TLDs</description>
         <param-name>tagLibJar1</param-name>
         <param-value>jsf-libs/standard.jar</param-value>
      </init-param>
      <init-param>
         <description>ADF Faces TLDs</description>
         <param-name>tagLibJar2</param-name>
         <param-value>jsf-libs/adf-faces-impl-ea19.jar</param-value>
      </init-param>

I have deployed JSTL and ADF Faces JARs once to this folder instead of bundling them in each application’s WAR file. So I now have 9KB EARs instead of 6MB EARs. Unfortunately this means I no longer have JSP Content Assist.

adf-faces-api-ea19.jar
adf-faces-impl-ea19.jar
adfshare-3218.jar
commons-beanutils.jar
commons-codec-1.2.jar
commons-collections.jar
commons-digester-1.6.jar
jboss-seam.jar
jstl.jar
myfaces-api.jar
myfaces-impl.jar
standard.jar

[Riyad Kalla]

Is there a way that I can get JSP Content Assist to function without needing to have the JARs in the WEB-INF/lib folder of my project?

Yes, they just need to be in your build path.

Alternatively, is there a way I can have the JARs in my project’s WEB-INF/lib folder so Content Assist works, but exclude them from being deployed to the WAR file?

No, whatever is in /lib get’s deployed. You can try creating a /lib dir right off the root of your project and moving the libs there and adding them to your build path instead.

I have deployed JSTL and ADF Faces JARs once to this folder instead of bundling them in each application’s WAR file. So I now have 9KB EARs instead of 6MB EARs. Unfortunately this means I no longer have JSP Content Assist.

That shouldn’t effect autocomplete as long as the JARs are in your build path. What kind of project is this that you don’t have autocomplete with? Are the JARs still in your build path? What kind of autocomplete are you having trouble with? Classes in scriplets or taglibs? Have you tried restarting MyEclipse and rebuilding your project?

[JamesWoodward]

Hi, many thanks for that. I was beginning to despair and was shoe horning the WTP JSP Editor into MyEclipse. What you suggested works great!

It is a Web Project, and it was the Taglib JSP Content Assist that was not working. It would be nice if the JSP Editor was able to pick taglibs from External Jars and User Libraries.

But I have it working now, I created a linked folder /jsf-libs under the root of the project that points to the jboss-4.0.3/server/all/deploy/jbossweb-tomcat55.sar/jsf-libs folder. Then add the JARs to the build path.

Thanks for your help!

[Riyad Kalla]

It would be nice if the JSP Editor was able to pick taglibs from External Jars and User Libraries.

Aye, we tried to for the 3.8.0 release but it turns out that the Eclipse platform treats files physically inside a project and physically outside a project quite different. We were unable to hook the resources outside the project into the parsing/indexing routine for taglibs.

Thanks for your help!

Glad it’s working.

I was beginning to despair and was shoe horning the WTP JSP Editor into MyEclipse.

Just a heads up, we build on WTP, so if you installed WTP independently under your Eclipse install, you most likely will start to run into strange behaviors, editor problems, etc. If you do, check your log file, if you notice the problems comming from SSE or WTP, then we suggest removing the WTP plugins under your eclipse dir and using -clean to restart to try and get rid of the old plugin cached data.

[klowtherjr]

This message has not been recovered.

[Riyad Kalla]

This message has not been recovered.

[Author]

Posts