[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-13413 at 1/29/13 12:44 AM:
------------------------------------------------------------------
1. *Page* (http://jquerymobile.com/test/docs/pages/page-anatomy.html)
!NewPage.png|thumbnail!
Result:
{code}
<div data-role="page">
<div data-role="header">
<h1>Page Title</h1>
</div><!-- /header -->
<div data-role="content">
<p>Page content goes here.</p>
</div><!-- /content -->
<div data-role="footer">
<h4>Page Footer</h4>
</div><!-- /footer -->
</div><!-- /page -->
{code}
2. *Dialog* (http://jquerymobile.com/test/docs/pages/dialog/index.html)
!NewDialog.png|thumbnail!
Result:
{code}
<a href="foo.html" data-rel="dialog" data-transition="pop" data-close-btn="none">Open dialog</a>
{code}
3. *Popup* (http://jquerymobile.com/test/docs/pages/popup/index.html)
!NewPopup.png|thumbnail!
Result:
{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}
4. *Header Bar* (http://jquerymobile.com/test/docs/toolbars/docs-headers.html)
!NewHeaderBar.png|thumbnail!
Result:
{code}
<div data-role="header">
<a href="index.html" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="index.html" data-icon="check" data-theme="b">Save</a>
</div>
{code}
5. *Footer Bar* (http://jquerymobile.com/test/docs/toolbars/docs-footers.html)
No wizard.
Result:
{code}
<div data-role="footer" class="ui-bar">
</div>
{code}
6. *Navbar* (http://jquerymobile.com/test/docs/toolbars/docs-navbar.html)
!NewNavbar.png|thumbnail!
Result:
{code}
<div data-role="navbar">
<ul>
<li><a href="a.html">One</a></li>
<li><a href="b.html">Two</a></li>
</ul>
</div><!-- /navbar -->
{code}
7. *Button* (http://jquerymobile.com/test/docs/buttons/buttons-types.html)
!NewButton.png|thumbnail!
Result:
{code}
<a href="index.html" data-role="button" data-mini="true">Link button</a>
{code}
8. *Grouped Buttons* (http://jquerymobile.com/test/docs/buttons/buttons-grouped.html)
No Wizard.
Result:
{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}
9. *Grid* (http://jquerymobile.com/test/docs/content/content-grids.html)
!NewGrid.png|thumbnail!
Result:
{code}
<div class="ui-grid-a">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
</div><!-- /grid-a -->
{code}
10. *Collapsible Content Block* (http://jquerymobile.com/test/docs/content/content-collapsible.html)
!NewBlock.png|thumbnail!
Result:
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
11. *Collapsible Set* (http://jquerymobile.com/test/docs/content/content-collapsible-set.html)
No Wizard.
Result:
{code}
<div data-role="collapsible-set">
</div>
{code}
12. *Field Container* (http://jquerymobile.com/test/docs/forms/slider/)
No Wizard.
Result:
{code}
<div data-role="fieldcontain">
</div>
{code}
13. *Flip Toggle Switch*
14. *Radio Button*
15. *Check Box*
16. *Grouped Check Boxes*
17. *Select Menu*
18. *Listview*
19. *Panel*
20. *Table*
was (Author: akazakov):
1. *Page* (http://jquerymobile.com/test/docs/pages/page-anatomy.html)
!NewPage.png|thumbnail!
Result:
{code}
<div data-role="page">
<div data-role="header">
<h1>Page Title</h1>
</div><!-- /header -->
<div data-role="content">
<p>Page content goes here.</p>
</div><!-- /content -->
<div data-role="footer">
<h4>Page Footer</h4>
</div><!-- /footer -->
</div><!-- /page -->
{code}
2. *Dialog* (http://jquerymobile.com/test/docs/pages/dialog/index.html)
!NewDialog.png|thumbnail!
Result:
{code}
<a href="foo.html" data-rel="dialog" data-transition="pop" data-close-btn="none">Open dialog</a>
{code}
3. *Popup* (http://jquerymobile.com/test/docs/pages/popup/index.html)
!NewPopup.png|thumbnail!
Result:
{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}
4. *Header Bar* (http://jquerymobile.com/test/docs/toolbars/docs-headers.html)
!NewHeaderBar.png|thumbnail!
Result:
{code}
<div data-role="header">
<a href="index.html" data-icon="delete">Cancel</a>
<h1>Edit Contact</h1>
<a href="index.html" data-icon="check" data-theme="b">Save</a>
</div>
{code}
5. *Footer Bar* (http://jquerymobile.com/test/docs/toolbars/docs-footers.html)
No wizard.
Result:
{code}
<div data-role="footer" class="ui-bar">
</div>
{code}
6. *Navbar* (http://jquerymobile.com/test/docs/toolbars/docs-navbar.html)
!NewNavbar.png|thumbnail!
Result:
{code}
<div data-role="navbar">
<ul>
<li><a href="a.html">One</a></li>
<li><a href="b.html">Two</a></li>
</ul>
</div><!-- /navbar -->
{code}
7. *Button* (http://jquerymobile.com/test/docs/buttons/buttons-types.html)
!NewButton.png|thumbnail!
Result:
{code}
<a href="index.html" data-role="button" data-mini="true">Link button</a>
{code}
8. *Grouped Buttons* (http://jquerymobile.com/test/docs/buttons/buttons-grouped.html)
No Wizard.
Result:
{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}
9. *Grid* (http://jquerymobile.com/test/docs/content/content-grids.html)
!NewGrid.png|thumbnail!
Result:
{code}
<div class="ui-grid-a">
<div class="ui-block-a"></div>
<div class="ui-block-b"></div>
</div><!-- /grid-a -->
{code}
10. *Collapsible Content Block* (http://jquerymobile.com/test/docs/content/content-collapsible.html)
!NewBlock.png|thumbnail!
Result:
{code}
<div data-role="collapsible">
<h3>I'm a header</h3>
<p>I'm the collapsible content.</p>
</div>
{code}
11. *Collapsible Set*
12. *Field Container*
13. *Flip Toggle Switch*
14. *Radio Button*
15. *Check Box*
16. *Grouped Check Boxes*
17. *Select Menu*
18. *Listview*
19. *Panel*
20. *Table*
> jQuery Mobile Widget Palette
> ----------------------------
>
> Key: JBIDE-13413
> URL: https://issues.jboss.org/browse/JBIDE-13413
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.x
>
> Attachments: NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewGrid.bmml, NewGrid.png, NewHeaderBar.bmml, NewHeaderBar.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png
>
>
> http://jquerymobile.com/test/
--
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, 2 months
[JBoss JIRA] (JBIDE-12361) PRoblem with WorkspaceFIlesetVirtualComponent, publish using fileset virtual component
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12361?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-12361:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Writer: mmurray
> PRoblem with WorkspaceFIlesetVirtualComponent, publish using fileset virtual component
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-12361
> URL: https://issues.jboss.org/browse/JBIDE-12361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 3.3.2, 4.0.0.Alpha1
>
> Attachments: JBIDE-12361.33x.patch, JBIDE-12361.33x.v2.patch
>
>
> Steps to reproduce:
> 1) Create a dynamic web project
> 2) Create a POJP
> 3) Inside POJP, make some file structure (foldera, foldera/file1.txt, foldera/file2.txt, folderb, folderb/b1.txt, etc)
> 4) Right-click web project, go to deployment assembly page
> 5) click add
> 6) click 'fileset'
> 7) set root to /pojp
> 8) set includes pattern to **/file1*
> 9) finish
> 10) publish this to some server
> You will note that matching files inside a subdirectory that is not explicitly included in the includes pattern does not get included. In this case, foldera/file1.txt will not be included, and folder 'foldera' will also not be created in the deployment. This is a bug.
> Part of this commit has been made over at JBIDE-12360 by accident
--
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, 2 months
[JBoss JIRA] (JBIDE-11990) When as7 server fails to start correctly but process is running it fails to stop the process after reaching time out
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11990?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-11990:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Writer: mmurray
> When as7 server fails to start correctly but process is running it fails to stop the process after reaching time out
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11990
> URL: https://issues.jboss.org/browse/JBIDE-11990
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 3.3.0.CR1
> Environment: JBT 3.3 nightly 2012-05-24
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 3.3.2, 4.0.0.Alpha1
>
>
> As a consequence of hitting JBIDE-11989 I found another problem. If for whatever reason the server fails to start properly (e.g. -Djboss.bind.address.management set to null) this is what happens:
> 1. The process keeps running on the remote host
> 2. The server is in Starting state until it reaches time out
> 3. This is where remote and local servers differ, but both behave wrongly
> 3.a - remote server: When time out is reached, server stops, but the process keeps running - you have to kill it manually
> 3.b - local server: When time out is reached, server tries to stop, but fails doing so. So you have to force stop and then it stops and the process is killed.
> The the bigger problem is with remote servers - you have no way of stopping the server other than sshing to the server and killing the process.
> In the case of local server, it is not so bad, but still after the time out the tools should be able to stop the server on first attempt.
--
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, 2 months
[JBoss JIRA] (JBDS-2437) Cannot deploy BPEL project
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2437?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2437:
----------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Writer: mmurray
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBDS-2437
> URL: https://issues.jboss.org/browse/JBDS-2437
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.2.GA
> Environment: JBDS 5.0.2.CR1 H235 + SOA-P 5.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 5.0.2.GA
>
> Attachments: deploy_error.png, jbosstools-diagnostics-20130109091445.zip
>
>
> Cannot deploy a bpel project.
--
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, 2 months
[JBoss JIRA] (JBIDE-13368) When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13368?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-13368:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Writer: mmurray
Description:
When a SOA-P 5.2 server is started in JBDS 5.0.2 and 5.0.1 - this exception is raised:
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
at org.jboss.Main.boot(Main.java:218)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 6 more
The root problem from EAP side is that this stacktrace occurs because it is launched with Java 7, same actually happens from command line.
Now, the question is why does Java 7 get selected when the server is setup to run with Java Execution Environment 1.6 - that is the tooling bug here and which Rob made a patch for.
To describe in cases:
1) Thus if the user have only Java 6 configured in Eclipse this issue should not occur.
2) If the user has only Java 7 configured in Eclipse this error is expected
3) If the user has both Java 6 and Java 7 configured and server adapter is configured to use Java 1.6 Execution Environment (which it is by default) then one would expect it to pick Java 6.
Case 1 and 2 works - its case 3 that is failing.
was:
When a SOA-P 5.2 server is started in JBDS 5.0.2 and 5.0.1 - this exception is raised:
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
at org.jboss.Main.boot(Main.java:218)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 6 more
The root problem from EAP side is that this stacktrace occurs because it is launched with Java 7, same actually happens from command line.
Now, the question is why does Java 7 get selected when the server is setup to run with Java Execution Environment 1.6 - that is the tooling bug here and which Rob made a patch for.
To describe in cases:
1) Thus if the user have only Java 6 configured in Eclipse this issue should not occur.
2) If the user has only Java 7 configured in Eclipse this error is expected
3) If the user has both Java 6 and Java 7 configured and server adapter is configured to use Java 1.6 Execution Environment (which it is by default) then one would expect it to pick Java 6.
Case 1 and 2 works - its case 3 that is failing.
> When having Java 7 and Java 6 installed EAP servers are not choosing Java 6 and fails to launch
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13368
> URL: https://issues.jboss.org/browse/JBIDE-13368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Environment: Version: 5.0.2.GA
> Build id: v20130103-0154-H238-GA
> Build date: 20130103-0154
> SOA-P 5.2.GA
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: JBIDE-13368.3.3.x.patch, Screenshot-1.png
>
>
> When a SOA-P 5.2 server is started in JBDS 5.0.2 and 5.0.1 - this exception is raised:
> Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
> at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
> at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
> at org.jboss.Main.boot(Main.java:218)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
> at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more
> The root problem from EAP side is that this stacktrace occurs because it is launched with Java 7, same actually happens from command line.
> Now, the question is why does Java 7 get selected when the server is setup to run with Java Execution Environment 1.6 - that is the tooling bug here and which Rob made a patch for.
> To describe in cases:
> 1) Thus if the user have only Java 6 configured in Eclipse this issue should not occur.
> 2) If the user has only Java 7 configured in Eclipse this error is expected
> 3) If the user has both Java 6 and Java 7 configured and server adapter is configured to use Java 1.6 Execution Environment (which it is by default) then one would expect it to pick Java 6.
> Case 1 and 2 works - its case 3 that is failing.
--
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, 2 months
[JBoss JIRA] (JBIDE-12403) Cannot start a server with JBT on eclipse Juno
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12403?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-12403:
------------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Writer: mmurray
Release Notes Text: Servers failed to start, with error messages stating an invalid -server option was being used. This issue occurred because the -server option was mistakenly added to the program arguments when a server was starting. It is now correctly added to the JVM arguments and servers start successfully. (was: Servers were failing to start and error messages stated an invalid -server option was being used. This issue occurred because the -server option was mistakenly added to the program arguments when a server was starting. It is now correctly added to the JVM arguments and servers start successfully. )
> Cannot start a server with JBT on eclipse Juno
> ----------------------------------------------
>
> Key: JBIDE-12403
> URL: https://issues.jboss.org/browse/JBIDE-12403
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Alpha1
> Environment: RHEL6
> java -version
> java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (rhel-1.48.1.11.3.el6_2-x86_64)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
> eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz
> http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
> http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 3.3.2, 4.0.0.Alpha1
>
>
> To recreate:
> 1) Install eclipse Juno (eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz)
> 2) Help->Install New Software - install JBoss tools:
> http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0...
> http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> 3) Create a new SOA-P 5.3 server runtime
> 4) Create a new SOA-P server - accept defaults for run config:
> "-Dprogram.name=JBossTools: JBossTools: SOA-5.3" -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/redhat_svn/jbds/jbosstools/esb/tests/org.jboss.tools.esb.ui.bot.test/target/requirements/jboss-soa-p-5/jboss-as/lib/endorsed"
> 5) Attempt to start the server - this error is returned:
> JBossTools: JBossTools: SOA-5.3: invalid option -- s
--
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, 2 months