- This topic has 3 replies, 2 voices, and was last updated 19 years, 10 months ago by
.
-
Posts
-
I am running Windows XP SP2, Eclipse 3.0.1 and have recently upgraded from ME 3.8.2 to ME 3.8.3.
Everything tested and working fine.
My project is using MyFaces 1.0.7, JSTL 1.1.2, Tiles-EL (Struts-EL 1.2.4).
commons-beanutils-1.6.1.jar commons-codec-1.2.jar commons-collections-3.0.jar commons-digester-1.5.jar commons-el.jar commons-fileupload-1.0.jar commons-logging.jar commons-validator.jar jakarta-oro.jar myfaces-components.jar myfaces-jsf-api.jar myfaces.jar jstl.jar standard.jar struts.jar struts-el.jarI want to make use of the User Libraries to avoid having to place MyFaces jars in the WEB-INF/lib folder.
After several attempts, everything compiles and deploys fine.
BUT, JSP code-assitance no longer works and squiggly orange lines underline all MyFaces, JSTL & Tiles tags.
If I place the jars in the WEB-INF/lib folder everything works.
If I place them in a User Library, everything compiles and deploys, but JSP code-assistance no longer works and validation errors are everywhere.Please Help!!!
Thanks,
James.James,
The addition of deployment of jars contained in user libraries was recently added in version 3.8.3. The intent was to provide support for common, internal libraries that are used across projects. We didn’t think of using them as a manual replacement for the automatic setup of libraries containing taglibs that we perform on project creation or when adding capabilities. As a result, at the present time the taglib location logic doesn’t look inside of all the jars included in all the user libraries since this could be quite time consuming and was outside the original usage intent. I’ve entered an enhancement request for this, but don’t have a timeline on it.
As a workaround you’ll need to place any jar that includes taglibs in your WEB-INF/lib directory and rebuild your project. If the reason you created a user library in the first place is that you didn’t like seeing all the jar’s listed at the top level in the Package Explorer View, you can remove them from the view by selecting Filters > Name filter patterns (matching names will be hidden) and entering *.jar in the text box below.
We apologize for the inconvenience that this may cause you.
