[jbosstools-issues] [JBoss JIRA] (JBIDE-13837) KB Builder does complete scanning of content of every jar file

Alexey Kazakov (JIRA) jira-events at lists.jboss.org
Wed Mar 27 13:04:43 EDT 2013


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

Alexey Kazakov commented on JBIDE-13837:
----------------------------------------

https://github.com/jbosstools/jbosstools-javaee/pull/66 contains new JUnit tests only. We fixed the bug in master and 4.0.x (JST) but we also added a few additional tests to master for JavaEE module. So there is no need to respin JavaEE for this fix for 4.0.1.
                
> KB Builder does complete scanning of content of every jar file 
> ---------------------------------------------------------------
>
>                 Key: JBIDE-13837
>                 URL: https://issues.jboss.org/browse/JBIDE-13837
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsp/jsf/xml/html source editing
>    Affects Versions: 4.1.0.Alpha1
>            Reporter: Viacheslav Kabanovich
>            Assignee: Viacheslav Kabanovich
>              Labels: respin-b
>             Fix For: 4.0.1.Final, 4.1.0.Alpha2
>
>
> Memory problem were reported https://community.jboss.org/message/804026#804026
> At present, KB builder scans for facelet taglibs everywhere in jar files, not only in META-INF folder. That results in complete loading of model objects for jar content, which otherwise would remain unloaded. Once loaded, it is not easy to release them, since objects are shared by projects referencing the same jar.
> Complete scanning was implemented as fix for https://issues.jboss.org/browse/JBIDE-5764 in February 2010.
> JSF implementation jsf-impl-2.0.1.jar contains facelet tag libraries in /com/sun/faces/metadata/taglib.
> However, it is recommended that facelet taglib xml files be packaged into META-INF folder. It seems that jsf-impl-2.0.1.jar is a special case. I suggest that we stop doing complete scanning of all jars and do it only for JSF 2 implementation jar.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list