[JBoss JIRA] (JBIDE-13840) Progress bar is running weird when downloading runtime
by Petr Suchý (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13840?page=com.atlassian.jira.plugi... ]
Petr Suchý updated JBIDE-13840:
-------------------------------
Summary: Progress bar is running weird when downloading runtime (was: Progress bar goes weird when downloading runtime)
> Progress bar is running weird when downloading runtime
> ------------------------------------------------------
>
> Key: JBIDE-13840
> URL: https://issues.jboss.org/browse/JBIDE-13840
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
> Reporter: Petr Suchý
> Assignee: Snjezana Peco
> Priority: Minor
> Fix For: 4.0.2.Final, 4.1.0.Alpha2
>
>
> When I am downloading runtime, the progress is running to the ~half of the bar (in progress view) and then starts again from the beginning. Runtime is always successfully downloaded, the problem is only with the bar.
> Tried on MS Windows and Linux.
--
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
13 years
[JBoss JIRA] (JBIDE-13840) Progress bar goes weird when downloading runtime
by Petr Suchý (JIRA)
Petr Suchý created JBIDE-13840:
----------------------------------
Summary: Progress bar goes weird when downloading runtime
Key: JBIDE-13840
URL: https://issues.jboss.org/browse/JBIDE-13840
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.1.0.Alpha1, 4.0.1.Final
Reporter: Petr Suchý
Assignee: Snjezana Peco
Priority: Minor
Fix For: 4.0.2.Final, 4.1.0.Alpha2
When I am downloading runtime, the progress is running to the ~half of the bar (in progress view) and then starts again from the beginning. Runtime is always successfully downloaded, the problem is only with the bar.
Tried on MS Windows and Linux.
--
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
13 years
[JBoss JIRA] (JBIDE-13736) TP should Support Servlet 3 and Jetty 8
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13736?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13736:
----------------------------------------
> 1) why was this added in before being announced on mailing list with a PR that list added/changed units + known sideeffects ?
Nick has announced upcoming changes.
I also think that the process of announce/wait for feedback/do is not very productive compared to do and then gather feedback. Especially for this change that is totally backward compatible: we still have Servlet 2.1 and Jetty 7 in the TP.
> 2) wasn't this addition preventing some other 3rd party (i.e. atlassian in failing to be installed? Should linked to releted jira/change request made or planned to be made for atlassian.
The addition is not preventing from anything. This issue is linked to JBIDE-13712, which is the one describing potentially breaking changes.
> TP should Support Servlet 3 and Jetty 8
> ---------------------------------------
>
> Key: JBIDE-13736
> URL: https://issues.jboss.org/browse/JBIDE-13736
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.1.0.Alpha1
> Reporter: Xavier Coulon
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha2
>
>
> The org.eclipse.jetty.websocket bundle is required by the upcoming livereload tooling (will be certainly part of the VPE component)
> Also, older version of Jetty should be removed from TP if they're not useful.
--
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
13 years
[JBoss JIRA] (JBIDE-13839) Adding runtimes through runtime-detection does not work properly
by Petr Suchý (JIRA)
Petr Suchý created JBIDE-13839:
----------------------------------
Summary: Adding runtimes through runtime-detection does not work properly
Key: JBIDE-13839
URL: https://issues.jboss.org/browse/JBIDE-13839
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.1.0.Alpha1
Reporter: Petr Suchý
Assignee: Snjezana Peco
Fix For: 4.1.0.Alpha2
When I add runtime (i.e. SOA-P 5.2) through runtime-detection, then I remove it from Servers view and then I add different runtime but with the same name (i.e. SOA-P 5.3, again through runtime-detection), this new runtime is not added.
--
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
13 years
[JBoss JIRA] (JBIDE-13778) Descriptions for jQuery Widget Palette elements
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13778?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-13778:
----------------------------------
Description:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
2. Page
*Page:*
<div data-role="page">
...
</div>
3. Dialog
*Dialog:*
<div data-role="dialog">
...
</div>
4. Popup
*Popup:*
<a href="#popupBasic" data-rel="popup">...</a>
<div data-role="popup" id="popupBasic">
...
</div>
5. Grid
*Grid:*
<div class="ui-grid-b">
...
</div>
6. Field Container
*Field Container:*
<div data-role="fieldcontain">
...
</div>
7. Panel
*Panel:*
<div data-role="panel">
...
</div>
8. Table
*Table:*
<table data-role="table"></code><br>
...
</table>
9. Collapsible
*Collapsible:*
<div data-role="collapsible">
...
</div>
10. Collapsible Set
*Collapsible Set:*
<div data-role="collapsible-set">
...
</div>
11. Header Bar
*Header Bar:*
<div data-role="header">
...
</div>
12. Footer Bar
*Footer Bar:*
<div data-role="footer">
...
</div>
13. Navbar
*Navbar:*
<div data-role="navbar">
...
</div>
14. Select
*Select menu:*
<label for="select-choice-0" class="select">...</label>
<select name="select-choice-0">
...
</select>
15. Listview
*Listview:*
<ul data-role="listview">
...
</ul>
16. Button
*Button:*
<a href="..." data-role="button">...</a>
17. Buttons
*Grouped buttons:*
<div data-role="controlgroup">
...
</div>
18. Link
*Link:*
<a href="...">...</a>
19. Toggle
*Flip toggle switch:*
<div data-role="fieldcontain">
<label for="flip-1">...</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
20. Radio
*Radio button:*
<fieldset data-role="controlgroup">
<legend></legend>
<input name="radio-choice-1" id="radio-choice-1a" value="A" type="radio"/>
<label for="radio-choice-1a">...</label>
</fieldset>
21. Checkbox
*Checkbox:*
<label>
<input type="checkbox" name="checkbox-1"/>
...
</label>
22. Checkboxes
*Grouped checkboxes:*
<fieldset data-role="controlgroup">
<legend></legend>
<input name="checkbox-1a" id="checkbox-1a" type="checkbox"/>
<label for="checkbox-1a">...</label>
</fieldset>
23. Slider
*Slider/Range slider:*
<label for="range-1">...</label>
<input name="range-1" data-highlight="true" type="range"/>
24. Text Input
*Text Input:*
<div data-role="fieldcontain">
<label for="text-1">...</label>
<input name="text-1" id="text-1" type="text"/>
</div>
was:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
2. Page
The *page* is the primary unit of interaction in *jQuery Mobile* and is used to group content into logical views that can be animated in and out of view with page transitions. A *HTML* document may start with a single "page" and the *AJAX* navigation system will load additional pages on demand into the *DOM* as users navigate around. Alternatively, a *HTML* document can be built with multiple "pages" inside it and the framework will transition between these local views with no need to request content from the server.
3. Dialog
Any *page* can be presented as a *modal dialog* by adding the *data-rel="dialog"* attribute to the page anchor link.
4. Popup
To create a *popup*, add the *data-role="popup"* attribute to a div with the popup contents. Then create a link with the href set to the id of the popup div, and add the attribute *data-rel="popup"* to tell the framework to open the popup when the link is tapped. A popup div has to be nested inside the same page as the link.
5. Grid
*Grids* are 100% width, completely invisible (no borders or backgrounds) and don't have padding or margins, so they shouldn't interfere with the styles of elements placed inside them. Within the grid container, child elements are assigned ui-block-a/b/c/d/e in a sequential manner which makes each "block" element float side-by-side, forming the grid.
6. Field Container
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element.
7. Panel
Flexible by design, *panels* can be used for navigation, forms, inspectors and more.
8. Table
The *reflow table* mode works by collapsing the table columns into a stacked presentation that looks like blocks of label/data pairs for each row.
9. Collapsible
*Collapsibles* are simple widgets that allow you to expand or collapse content when tapped and are useful in mobile to provide a compact presentation of content.
10. Collapsible Set
*Collapsible sets* start with the exact same markup as individual *collapsibles*. By adding a parent wrapper with a *data-role="collapsible-set"* attribute around a number of *collapsibles*, the framework will style these to looks like a visually grouped widget and make it behave like an accordion so only one section can be open at a time.
11. Header Bar
The *header* is a toolbar at the top of the page that usually contains the page title text and optional buttons positioned to the left and/or right of the title for navigation or actions.
12. Footer Bar
The *footer* is a toolbar at the bottom of the page that can contain a wide range of content, from for elements to *navbars*.
13. Navbar
*Navbar* widget is useful for providing up to 5 buttons with optional icons in a bar.
14. Select
The *select menu* is based on a native select element, which is hidden from view and replaced with a custom-styled select button. Tapping it opens the native menu.
15. Listview
A *listview* is coded as a simple *unordered list (ul)* or *ordered list (ol)* with a *data-role="listview"* attribute and has a wide range of features.
16. Button
*Buttons* are core widgets in *jQuery Mobile* and are used within a wide range of other plugins. The *button* markup is flexible and can be created from links or form buttons.
17. Buttons
*Controlgroups* are used to visually group a set of buttons to form a single block that looks contained like a navigation component.
18. Link
You can *link* pages and assets as you normally would, and *jQuery Mobile* will automatically handle *page* requests in a single-page model, using *AJAX* when possible. When *AJAX* isn't possible (such as a non-same-domain url, or if specified using certain attributes on the link), a normal http request is used instead.
19. Toggle
*Flip switches* are used for boolean style inputs like true/false or on/off in a compact UI element.
20. Radio
*Radio buttons* are used to provide a list of options where only a single option can be selected.
21. Checkbox
*Checkboxes* are used to provide a list of options where more than one can be selected.
22. Checkboxes
To improve the styling of labels and form elements on wider screens, wrap a div or fieldset with the *data-role="fieldcontain"* attribute around each label/form element.
23. Slider
*Sliders* are used to enter numeric values along a continuum and can also be dual *handle range sliders* or *flip switches*.
24. Text Input
*Text inputs* and *textareas* are coded with standard HTML elements, then enhanced by *jQuery Mobile* to make them more attractive and useable on a mobile device.
> Descriptions for jQuery Widget Palette elements
> -----------------------------------------------
>
> Key: JBIDE-13778
> URL: https://issues.jboss.org/browse/JBIDE-13778
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Daniel Azarov
> Assignee: Daniel Azarov
> Fix For: 4.1.0.Alpha2
>
>
> We need to have palette elements descriptions and we need to show them in tooltips.
> 1. JS/CSS
> Add references to *jQuery*, *jQuery Mobile* JS and CSS to <head>
> 2. Page
> *Page:*
> <div data-role="page">
> ...
> </div>
> 3. Dialog
> *Dialog:*
> <div data-role="dialog">
> ...
> </div>
> 4. Popup
> *Popup:*
> <a href="#popupBasic" data-rel="popup">...</a>
> <div data-role="popup" id="popupBasic">
> ...
> </div>
> 5. Grid
> *Grid:*
> <div class="ui-grid-b">
> ...
> </div>
> 6. Field Container
> *Field Container:*
> <div data-role="fieldcontain">
> ...
> </div>
> 7. Panel
> *Panel:*
> <div data-role="panel">
> ...
> </div>
> 8. Table
> *Table:*
> <table data-role="table"></code><br>
> ...
> </table>
> 9. Collapsible
> *Collapsible:*
> <div data-role="collapsible">
> ...
> </div>
> 10. Collapsible Set
> *Collapsible Set:*
> <div data-role="collapsible-set">
> ...
> </div>
> 11. Header Bar
> *Header Bar:*
> <div data-role="header">
> ...
> </div>
> 12. Footer Bar
> *Footer Bar:*
> <div data-role="footer">
> ...
> </div>
> 13. Navbar
> *Navbar:*
> <div data-role="navbar">
> ...
> </div>
> 14. Select
> *Select menu:*
> <label for="select-choice-0" class="select">...</label>
> <select name="select-choice-0">
> ...
> </select>
> 15. Listview
> *Listview:*
> <ul data-role="listview">
> ...
> </ul>
> 16. Button
> *Button:*
> <a href="..." data-role="button">...</a>
> 17. Buttons
> *Grouped buttons:*
> <div data-role="controlgroup">
> ...
> </div>
> 18. Link
> *Link:*
> <a href="...">...</a>
> 19. Toggle
> *Flip toggle switch:*
> <div data-role="fieldcontain">
> <label for="flip-1">...</label>
> <select name="flip-1" id="flip-1" data-role="slider">
> <option value="off">Off</option>
> <option value="on">On</option>
> </select>
> </div>
> 20. Radio
> *Radio button:*
> <fieldset data-role="controlgroup">
> <legend></legend>
> <input name="radio-choice-1" id="radio-choice-1a" value="A" type="radio"/>
> <label for="radio-choice-1a">...</label>
> </fieldset>
> 21. Checkbox
> *Checkbox:*
> <label>
> <input type="checkbox" name="checkbox-1"/>
> ...
> </label>
> 22. Checkboxes
> *Grouped checkboxes:*
> <fieldset data-role="controlgroup">
> <legend></legend>
> <input name="checkbox-1a" id="checkbox-1a" type="checkbox"/>
> <label for="checkbox-1a">...</label>
> </fieldset>
> 23. Slider
> *Slider/Range slider:*
> <label for="range-1">...</label>
> <input name="range-1" data-highlight="true" type="range"/>
> 24. Text Input
> *Text Input:*
> <div data-role="fieldcontain">
> <label for="text-1">...</label>
> <input name="text-1" id="text-1" type="text"/>
> </div>
--
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
13 years
[JBoss JIRA] (JBIDE-13808) Test failures and timeouts in JSF tests
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13808?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13808:
----------------------------------
Fix Version/s: 4.0.x
(was: 4.0.1.Final)
> Test failures and timeouts in JSF tests
> ---------------------------------------
>
> Key: JBIDE-13808
> URL: https://issues.jboss.org/browse/JBIDE-13808
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF, Visual Page Editor core
> Affects Versions: 4.0.1.Final
> Reporter: Nick Boldt
> Assignee: Yahor Radtsevich
> Priority: Blocker
> Fix For: 4.0.x
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--javaee/146/console}
> [INFO] org.jboss.tools.jsf.text.ext.test ................. FAILURE [1:20.290s]
> [INFO] org.jboss.tools.jsf.vpe.facelets.test ............. FAILURE [1:00:28.012s]
> [INFO] org.jboss.tools.jsf.vpe.jbpm.test ................. FAILURE [1:00:24.806s]
> [INFO] org.jboss.tools.jsf.vpe.jstl.test ................. FAILURE [1:00:25.978s]
> [INFO] org.jboss.tools.jsf.vpe.seam.test ................. FAILURE [1:00:28.143s]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.text.ext.test: An unexpected error occured (return code 134). See log for details. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.facelets.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.jbpm.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.jstl.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.jsf.vpe.seam.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 2]
--
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
13 years
[JBoss JIRA] (JBIDE-13807) yet more timeouts running vpe tests
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13807?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13807:
----------------------------------
Fix Version/s: 4.0.x
(was: 4.0.1.Final)
> yet more timeouts running vpe tests
> -----------------------------------
>
> Key: JBIDE-13807
> URL: https://issues.jboss.org/browse/JBIDE-13807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.0.1.Final
> Reporter: Nick Boldt
> Assignee: Yahor Radtsevich
> Priority: Blocker
> Fix For: 4.0.x
>
>
> Another series of slow-running tests that take longer than their allotted time limit of 1hr each:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.component--vpe/108/console}
> [INFO] vpe.tests ......................................... SUCCESS [1.023s]
> [INFO] org.jboss.tools.vpe.base.test ..................... SUCCESS [1.898s]
> [INFO] org.jboss.tools.vpe.docbook.test .................. FAILURE [1:00:27.929s]
> [INFO] org.jboss.tools.vpe.ui.test ....................... SUCCESS [51.907s]
> [INFO] org.jboss.tools.vpe.html.test ..................... FAILURE [1:00:19.956s]
> [INFO] org.jboss.tools.vpe.spring.test ................... FAILURE [1:00:20.025s]
> [INFO] org.jboss.tools.vpe.jsp.test ...................... SUCCESS [1:04.495s]
> [INFO] org.jboss.tools.vpe.test .......................... SUCCESS [31.253s]
> [INFO] org.jboss.tools.vpe.xulrunner.test ................ SUCCESS [22.797s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.vpe.docbook.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.vpe.html.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.16.0:test (default-test) on project org.jboss.tools.vpe.spring.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 3600 seconds -> [Help 1]
> {code}
--
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
13 years
[JBoss JIRA] (JBIDE-13837) KB Builder does complete scanning of content of every jar file
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-13837:
-----------------------------------------------
JSF 2 specification in section 10.3.2 Facelet Tag Library mechanism defines facelet taglib discovery as follows:
The run time must support two modes of discovery for Facelet tag library descriptors
1. Via declaration in the web.xml, as specified in Section 11.1.3 “Application Configuration Parameters”
2. Via auto discovery by placing the tag library discriptor file within a jar on the web application classpath, naming the
file so that it ends with “.taglib.xml”, without the quotes, and placing the file in the META-INF directory in the
jar file.
That proves that facelet tag libraries in jsf-impl.jar make a special case. Still, we should support it as jsf-impl-2.1.5.jar and jsf-impl-2.2.0.jar include these files. I think that we may just check that jar file name starts with jsf-impl.
> 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
> Fix For: 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
13 years
[JBoss JIRA] (JBIDE-13837) KB Builder does complete scanning of content of every jar file
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13837?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-13837:
------------------------------------------
Description:
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.
> 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
> Fix For: 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
13 years