[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4647) new JSF Project on tomcat 6.0.20 generates doubled el-api.jar and causes LinkageError

[Denis Golovin (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12481791#action_12481791 ] 

Denis Golovin commented on JBIDE-4647:
--------------------------------------

there is such option but referenced libraries are hidden by default in Java Package Explorer view, it can be done from Navigator view where there is no such restriction

> new JSF Project on tomcat 6.0.20 generates doubled el-api.jar and causes LinkageError
> -------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4647
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4647
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JSF
>    Affects Versions: 3.1.0.M2
>         Environment: eclipse galileo 20090621-0832, Vista
>            Reporter: Tomasz Bartczak
>            Assignee: Denis Golovin
>
> Created a new JSF Project with FaceletsKickStartRI and chosen a fresh tomcat 6.0.20. 
> java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.addELResolver(Ljavax/el/ELResolver;)V" the class loader (instance of org/apache/catalina/loader/WebappClassLoader) of the current class, com/sun/faces/config/ConfigureListener, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ELResolver used in the signature
> when starting server and this app. 
> and i cannot see an option of removing el-api.jar from web app libraries. instead i had to remove jar from tomcat
> when I did that I had class not found ! 
> java.lang.NoClassDefFoundError: javax/el/ExpressionFactory
> I think because of tomcat needs it on its internal classpath...
> so there is no solution!

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira