[JBoss JIRA] (JBIDE-13799) Source Lookup enhancements
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-13799:
---------------------------------------
JBoss Java Project Source Container (Debugging Arquillian tests)
When debugging an Arquillian test using a remote container, we usually do the following steps:
- create a project
- add the Arquillian support
- create a test
- configure Maven profiles
- create a JBoss server
- start the server in the debug mode
- start the test in the debug mode
We can debug the classes from the project's source by adding the Eclipse Java Project source container to the Source Lookup.
However, if we want to debug some Arquillian code in a server (remote) JVM, adding the Eclipse container won't be enough. The Arquillian classes aren't included in a JBoss server and the Java Project source container searches only the project's source folders.
If we can deploy the project, the JBoss Source Lookup plugin will solve all the classes from a mavenized archive so that we can debug the classes from such a project.
If we can't (or don't want to) deploy the project, we can use the JBoss Java Project Source Container from the arquillian eclipse plugin.
The JBoss Java Project Source Container is similar to the Java Project source container. The differ is that it searches classes from the project's classpath. The container solves source files for all the classes from a mavenized library included in the classpath.
The project can, but doesn't have to be a Maven project.
Test case:
- create a JBoss AS Server
- import the JBoss Central Java EE project (don't deploy it)
- set a breakpoint in the org.jboss.arquillian.junit.Arquillian.methodInvoker(FrameworkMethod, Object) method (at line 270 in Arquillian 1.0.3)
- start the server in the debug mode from JBT/JBDS
- debug MemberRegistrationTest
The Eclipse won't open the Arquillian source file, which happens because this method is called from within the server's JVM that doesn't know anything about the Java EE project.
Adding the Eclipse Java Project source container won't help because it adds only source folders.
The Remote Debug feature also won't help because we have started the server from JBT/JBDS so that we are already connected to the JVM.
- install/update the Source Lookup plugin from http://snjeza.github.com/jbosstools-central
- add the JBoss Java Project Source Container to the Source Lookup
You will be able to debug any class from the project.
It is possible to create different helper projects and add the container to different remote launch configurations.
The JBoss Java Project Source Container isn't related to the arquillian-eclipse feature and/or JBoss servers and can be added to any launch configuration. The container probably has to be moved to the JBoss Source Lookup plugin.
See http://screencast.com/t/fHTO6ZP5dFh
> Source Lookup enhancements
> --------------------------
>
> Key: JBIDE-13799
> URL: https://issues.jboss.org/browse/JBIDE-13799
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
>
> The PR includes the following enhancements:
> - AS 7.2/EAP 6.1 are now recognized correctly
> - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
> - the fix for the ConcurrentModificationException exception
> - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
> - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
> - JBoss Java Project Source Container
> See http://screencast.com/t/39LHqYx5m
> Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.
> Note:
> You have to have some deployment on the servers in order the WeldBootstrap class to be created.
> You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
> The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).
--
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-13799) Source Lookup enhancements
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13799?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-13799:
----------------------------------
Description:
The PR includes the following enhancements:
- AS 7.2/EAP 6.1 are now recognized correctly
- the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
- the fix for the ConcurrentModificationException exception
- included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
- JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
- JBoss Java Project Source Container
See http://screencast.com/t/39LHqYx5m
Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.
Note:
You have to have some deployment on the servers in order the WeldBootstrap class to be created.
You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).
was:
The PR includes the following enhancements:
- AS 7.2/EAP 6.1 are now recognized correctly
- the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
- the fix for the ConcurrentModificationException exception
- included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
- JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
See http://screencast.com/t/39LHqYx5m
Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.
Note:
You have to have some deployment on the servers in order the WeldBootstrap class to be created.
You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).
> Source Lookup enhancements
> --------------------------
>
> Key: JBIDE-13799
> URL: https://issues.jboss.org/browse/JBIDE-13799
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
>
> The PR includes the following enhancements:
> - AS 7.2/EAP 6.1 are now recognized correctly
> - the fix for the issue caused by changing the editor ID for ClassFileEdtor in 3.8/4.2
> - the fix for the ConcurrentModificationException exception
> - included libraries can be filtered - jsf 1.2 and hibernate 3 will be excluded by default for JBoss AS Container
> - JBoss Runtimes now can be included in the Java Search (this feature has been implemented in a similar way to adding PDE plugins to the Java Search)
> - JBoss Java Project Source Container
> See http://screencast.com/t/39LHqYx5m
> Screenshot shows debugging the WeldBootstrap class in JBoss AS 7.1 and JBoss AS 7.2.
> Note:
> You have to have some deployment on the servers in order the WeldBootstrap class to be created.
> You can add more JBoss servers to the Java Search, but it is the best to use only one at a time because of the performance reason.
> The "Automatically add the JBoss Maven source container to all JBoss AS launch configurations" and "Include the following JBoss Servers in the Java Search" checkboxes aren't related. The first checkbox adds the source container that enables finding a Java source file when debugging, the second enables finding a Java source file using the Java Search (using the "Open type" command, for instance).
--
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 <b>jQuery</b>, <b>jQuery Mobile</b> JS and CSS to <code><head></code>
*Syntax:*
{code}
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
</head>
{code}
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.
*Syntax:*
{code}
<div data-role="page" id="page-1">
<div data-role="header">
<h1>Page Title</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
{code}
3. Dialog
Any page can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
*Syntax:*
{code}
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>Dialog</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
{code}
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.
*Syntax:*
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
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.
*Syntax:*
{code}
<div class="ui-grid-b">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
</div>
{code}
6. Field Container
*Syntax:*
{code}
<div data-role="fieldcontain">
</div>
{code}
7. Panel
*Syntax:*
{code}
<div data-role="panel" id="mypanel">
<!-- panel content goes here -->
</div><!-- /panel -->
{code}
8. Table
*Syntax:*
{code}
<table data-role="table" id="my-table" data-mode="reflow">
<thead>
<tr>
<th>Header 1</th>
<th>Header 2</th>
</tr>
</thead>
<tbody>
<tr>
<th>1</th>
<td>Item 1</td>
<td>Item 2</td>
</tr>
</tbody>
</table>
{code}
9. Collapsible
*Syntax:*
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
10. Collapsible Set
*Syntax:*
{code}
<div data-role="collapsible-set">
</div>
{code}
11. Header Bar
*Syntax:*
{code}
<div data-role="header">
<a href="#" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="#" data-icon="check">Save</a>
</div>
{code}
12. Footer Bar
*Syntax:*
{code}
<div data-role="footer" class="ui-bar">
<a href="#" data-icon="plus">Add</a>
<a href="#" data-icon="arrow-u">Up</a>
<a href="#" data-icon="arrow-d">Down</a>
</div>
{code}
13. Navbar
*Syntax:*
{code}
<div data-role="navbar">
<ul>
<li><a href="#">A</a></li>
<li><a href="#">B</a></li>
<li><a href="#">C</a></li>
</ul>
</div>
{code}
14. Select
*Syntax:*
{code}
<label for="select-choice-0" class="select">Shipping method:</label>
<select name="select-choice-0" id="select-choice-0">
<option value="standard">Standard: 7 day</option>
<option value="rush">Rush: 3 days</option>
<option value="express">Express: next day</option>
<option value="overnight">Overnight</option>
</select>
{code}
15. Listview
*Syntax:*
{code}
<ul data-role="listview">
<li><a href="item1.html">Item 1</a></li>
<li><a href="item2.html">Item 2</a></li>
</ul>
{code}
16. Button
*Syntax:*
{code}
<a href="" data-role="button">Link button</a>
{code}
17. Buttons
*Syntax:*
{code}
<div data-role="controlgroup">
<a href="index.html" data-role="button">Yes</a>
<a href="index.html" data-role="button">No</a>
<a href="index.html" data-role="button">Maybe</a>
</div>
{code}
18. Link
*Syntax:*
{code}
<a href="">Link</a>
{code}
19. Toggle
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="flip-1">Switch:</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
{code}
20. Radio
*Syntax:*
{code}
<fieldset data-role="controlgroup">
<legend>Choose a pet:</legend>
<input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
<label for="radio-choice-1">Cat</label>
<input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
<label for="radio-choice-2">Dog</label>
<input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
<label for="radio-choice-3">Hamster</label>
</fieldset>
{code}
21. Checkbox
*Syntax:*
{code}
<label><input type="checkbox" name="checkbox-1"/>I agree</label>
{code}
22. Checkboxes
*Syntax:*
{code}
<div data-role="fieldcontain">
<fieldset data-role="controlgroup">
<legend>Choose as many snacks as you'd like:</legend>
<input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
<label for="checkbox-1a">Cheetos</label>
<input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
<label for="checkbox-2a">Doritos</label>
<input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
<label for="checkbox-3a">Fritos</label>
</fieldset>
</div>
{code}
23. Slider
*Syntax:*
{code}
<label for="range-1">Slider:</label>
<input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
{code}
24. Text Input
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="text-1">Input:</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
</div>
{code}
was:
We need to have palette elements descriptions and we need to show them in tooltips.
1. JS/CSS
Add references to <b>jQuery</b>, <b>jQuery Mobile</b> JS and CSS to <head>
*Syntax:*
{code}
<head>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
<script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
<script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
</head>
{code}
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.
*Syntax:*
{code}
<div data-role="page" id="page-1">
<div data-role="header">
<h1>Page Title</h1>
</div>
<div data-role="content">
<p>Page content goes here.</p>
</div>
<div data-role="footer">
<h4>Page Footer</h4>
</div>
{code}
3. Dialog
Any page can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
*Syntax:*
{code}
<div data-role="dialog" id="dialog-1">
<div data-role="header">
<h1>Dialog</h1>
</div>
<div data-role="content">
<h6>Dialog content.</h6>
<a href="#dialog-1" data-role="button" data-rel="back">OK</a>
</div>
</div>
{code}
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.
*Syntax:*
{code}
<a href="#popupBasic" data-rel="popup">Open Popup</a>
<div data-role="popup" id="popupBasic">
<p>This is a completely basic popup, no options set.<p>
</div>
{code}
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.
*Syntax:*
{code}
<div class="ui-grid-b">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
<div class="ui-block-c"></div>
</div>
{code}
6. Field Container
*Syntax:*
{code}
<div data-role="fieldcontain">
</div>
{code}
7. Panel
*Syntax:*
{code}
<div data-role="panel" id="mypanel">
<!-- panel content goes here -->
</div><!-- /panel -->
{code}
8. Table
*Syntax:*
{code}
<table data-role="table" id="my-table" data-mode="reflow">
<thead>
<tr>
<th>Header 1</th>
<th>Header 2</th>
</tr>
</thead>
<tbody>
<tr>
<th>1</th>
<td>Item 1</td>
<td>Item 2</td>
</tr>
</tbody>
</table>
{code}
9. Collapsible
*Syntax:*
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
10. Collapsible Set
*Syntax:*
{code}
<div data-role="collapsible-set">
</div>
{code}
11. Header Bar
*Syntax:*
{code}
<div data-role="header">
<a href="#" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="#" data-icon="check">Save</a>
</div>
{code}
12. Footer Bar
*Syntax:*
{code}
<div data-role="footer" class="ui-bar">
<a href="#" data-icon="plus">Add</a>
<a href="#" data-icon="arrow-u">Up</a>
<a href="#" data-icon="arrow-d">Down</a>
</div>
{code}
13. Navbar
*Syntax:*
{code}
<div data-role="navbar">
<ul>
<li><a href="#">A</a></li>
<li><a href="#">B</a></li>
<li><a href="#">C</a></li>
</ul>
</div>
{code}
14. Select
*Syntax:*
{code}
<label for="select-choice-0" class="select">Shipping method:</label>
<select name="select-choice-0" id="select-choice-0">
<option value="standard">Standard: 7 day</option>
<option value="rush">Rush: 3 days</option>
<option value="express">Express: next day</option>
<option value="overnight">Overnight</option>
</select>
{code}
15. Listview
*Syntax:*
{code}
<ul data-role="listview">
<li><a href="item1.html">Item 1</a></li>
<li><a href="item2.html">Item 2</a></li>
</ul>
{code}
16. Button
*Syntax:*
{code}
<a href="" data-role="button">Link button</a>
{code}
17. Buttons
*Syntax:*
{code}
<div data-role="controlgroup">
<a href="index.html" data-role="button">Yes</a>
<a href="index.html" data-role="button">No</a>
<a href="index.html" data-role="button">Maybe</a>
</div>
{code}
18. Link
*Syntax:*
{code}
<a href="">Link</a>
{code}
19. Toggle
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="flip-1">Switch:</label>
<select name="flip-1" id="flip-1" data-role="slider">
<option value="off">Off</option>
<option value="on">On</option>
</select>
</div>
{code}
20. Radio
*Syntax:*
{code}
<fieldset data-role="controlgroup">
<legend>Choose a pet:</legend>
<input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
<label for="radio-choice-1">Cat</label>
<input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
<label for="radio-choice-2">Dog</label>
<input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
<label for="radio-choice-3">Hamster</label>
</fieldset>
{code}
21. Checkbox
*Syntax:*
{code}
<label><input type="checkbox" name="checkbox-1"/>I agree</label>
{code}
22. Checkboxes
*Syntax:*
{code}
<div data-role="fieldcontain">
<fieldset data-role="controlgroup">
<legend>Choose as many snacks as you'd like:</legend>
<input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
<label for="checkbox-1a">Cheetos</label>
<input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
<label for="checkbox-2a">Doritos</label>
<input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
<label for="checkbox-3a">Fritos</label>
</fieldset>
</div>
{code}
23. Slider
*Syntax:*
{code}
<label for="range-1">Slider:</label>
<input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
{code}
24. Text Input
*Syntax:*
{code}
<div data-role="fieldcontain">
<label for="text-1">Input:</label>
<input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
</div>
{code}
> 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 <b>jQuery</b>, <b>jQuery Mobile</b> JS and CSS to <code><head></code>
> *Syntax:*
> {code}
> <head>
> <meta name="viewport" content="width=device-width, initial-scale=1">
> <link rel="stylesheet" href="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.css" />
> <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script>
> <script src="http://code.jquery.com/mobile/1.3.0/jquery.mobile-1.3.0.min.js"></script>
> </head>
> {code}
> 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.
> *Syntax:*
> {code}
> <div data-role="page" id="page-1">
> <div data-role="header">
> <h1>Page Title</h1>
> </div>
> <div data-role="content">
> <p>Page content goes here.</p>
> </div>
> <div data-role="footer">
> <h4>Page Footer</h4>
> </div>
> {code}
> 3. Dialog
> Any page can be presented as a modal dialog that appears to be suspended above the page by adding an attribute to the link that leads to the dialog page.
> *Syntax:*
> {code}
> <div data-role="dialog" id="dialog-1">
> <div data-role="header">
> <h1>Dialog</h1>
> </div>
> <div data-role="content">
> <h6>Dialog content.</h6>
> <a href="#dialog-1" data-role="button" data-rel="back">OK</a>
> </div>
> </div>
> {code}
> 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.
> *Syntax:*
> {code}
> <a href="#popupBasic" data-rel="popup">Open Popup</a>
> <div data-role="popup" id="popupBasic">
> <p>This is a completely basic popup, no options set.<p>
> </div>
> {code}
> 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.
> *Syntax:*
> {code}
> <div class="ui-grid-b">
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> <div class="ui-block-a"></div>
> <div class="ui-block-b"></div>
> <div class="ui-block-c"></div>
> </div>
> {code}
> 6. Field Container
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> </div>
> {code}
> 7. Panel
> *Syntax:*
> {code}
> <div data-role="panel" id="mypanel">
> <!-- panel content goes here -->
>
> </div><!-- /panel -->
> {code}
> 8. Table
> *Syntax:*
> {code}
> <table data-role="table" id="my-table" data-mode="reflow">
> <thead>
> <tr>
> <th>Header 1</th>
> <th>Header 2</th>
> </tr>
> </thead>
> <tbody>
> <tr>
> <th>1</th>
> <td>Item 1</td>
> <td>Item 2</td>
> </tr>
> </tbody>
> </table>
> {code}
> 9. Collapsible
> *Syntax:*
> {code}
> <div data-role="collapsible">
> <h3>I'm a header</h3>
> <p>I'm the collapsible content.</p>
>
> </div>
> {code}
> 10. Collapsible Set
> *Syntax:*
> {code}
> <div data-role="collapsible-set">
>
> </div>
> {code}
> 11. Header Bar
> *Syntax:*
> {code}
> <div data-role="header">
> <a href="#" data-icon="delete">Cancel</a>
> <h1>Edit Contact</h1>
> <a href="#" data-icon="check">Save</a>
> </div>
> {code}
> 12. Footer Bar
> *Syntax:*
> {code}
> <div data-role="footer" class="ui-bar">
> <a href="#" data-icon="plus">Add</a>
> <a href="#" data-icon="arrow-u">Up</a>
> <a href="#" data-icon="arrow-d">Down</a>
> </div>
> {code}
> 13. Navbar
> *Syntax:*
> {code}
> <div data-role="navbar">
> <ul>
> <li><a href="#">A</a></li>
> <li><a href="#">B</a></li>
> <li><a href="#">C</a></li>
> </ul>
> </div>
> {code}
> 14. Select
> *Syntax:*
> {code}
> <label for="select-choice-0" class="select">Shipping method:</label>
> <select name="select-choice-0" id="select-choice-0">
> <option value="standard">Standard: 7 day</option>
> <option value="rush">Rush: 3 days</option>
> <option value="express">Express: next day</option>
> <option value="overnight">Overnight</option>
> </select>
> {code}
> 15. Listview
> *Syntax:*
> {code}
> <ul data-role="listview">
> <li><a href="item1.html">Item 1</a></li>
> <li><a href="item2.html">Item 2</a></li>
> </ul>
> {code}
> 16. Button
> *Syntax:*
> {code}
> <a href="" data-role="button">Link button</a>
> {code}
> 17. Buttons
> *Syntax:*
> {code}
> <div data-role="controlgroup">
> <a href="index.html" data-role="button">Yes</a>
> <a href="index.html" data-role="button">No</a>
> <a href="index.html" data-role="button">Maybe</a>
> </div>
> {code}
> 18. Link
> *Syntax:*
> {code}
> <a href="">Link</a>
> {code}
> 19. Toggle
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <label for="flip-1">Switch:</label>
> <select name="flip-1" id="flip-1" data-role="slider">
> <option value="off">Off</option>
> <option value="on">On</option>
> </select>
> </div>
> {code}
> 20. Radio
> *Syntax:*
> {code}
> <fieldset data-role="controlgroup">
> <legend>Choose a pet:</legend>
> <input type="radio" name="radio-choice" id="radio-choice-1" value="choice-1" checked="checked" />
> <label for="radio-choice-1">Cat</label>
> <input type="radio" name="radio-choice" id="radio-choice-2" value="choice-2" />
> <label for="radio-choice-2">Dog</label>
> <input type="radio" name="radio-choice" id="radio-choice-3" value="choice-3" />
> <label for="radio-choice-3">Hamster</label>
> </fieldset>
> {code}
> 21. Checkbox
> *Syntax:*
> {code}
> <label><input type="checkbox" name="checkbox-1"/>I agree</label>
> {code}
> 22. Checkboxes
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <fieldset data-role="controlgroup">
> <legend>Choose as many snacks as you'd like:</legend>
> <input type="checkbox" name="checkbox-1a" id="checkbox-1a" class="custom" />
> <label for="checkbox-1a">Cheetos</label>
> <input type="checkbox" name="checkbox-2a" id="checkbox-2a" class="custom" />
> <label for="checkbox-2a">Doritos</label>
>
> <input type="checkbox" name="checkbox-3a" id="checkbox-3a" class="custom" />
> <label for="checkbox-3a">Fritos</label>
> </fieldset>
> </div>
> {code}
> 23. Slider
> *Syntax:*
> {code}
> <label for="range-1">Slider:</label>
> <input name="range-1" id="range-1" data-highlight="true" min="0" max="100" value="40" type="range"/>
> {code}
> 24. Text Input
> *Syntax:*
> {code}
> <div data-role="fieldcontain">
> <label for="text-1">Input:</label>
> <input name="text-1" id="text-1" data-clear-btn="true" value="" type="text"/>
> </div>
> {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-13808) Test failures and timeouts in JSF tests
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13808?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-13808:
--------------------------------------
Assignee: Yahor Radtsevich (was: Alexey Kazakov)
There was a fatal error outside JVM when running org.jboss.tools.jsf.text.ext.test
I have no idea why.
{code}
Running org.jboss.tools.jsf.text.ext.test.JsfTextExtAllTests
jsf_core.tld
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000003140608c5b, pid=10820, tid=47524590430528
#
# JRE version: 6.0_43-b01
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [ld-linux-x86-64.so.2+0x8c5b]
#
# An error report file with more information is saved as:
# /mnt/hudson_workspace/workspace/jbosstools-4.0_stable_branch.component--javaee/sources/jsf/tests/org.jboss.tools.jsf.text.ext.test/hs_err_pid10820.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
{code}
The rest of failing tests of javaee are VPE tests:
{code}
[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]
{code}
Assigning to Yahor.
> 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.1.Final
>
>
> {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-13808) Test failures and timeouts in JSF tests
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13808?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13808:
-----------------------------------
Component/s: Visual Page Editor core
> 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: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.0.1.Final
>
>
> {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