November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15895) Cordova API not working when added widget from jQuery Mobile palette

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-15895: ----------------------------------- Summary: Cordova API not working when added widget from jQuery Mobile palette Key: JBIDE-15895 URL: https://issues.jboss.org/browse/JBIDE-15895 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid Affects Versions: 4.1.1.Beta1 Environment: JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493 Reporter: Vlado Pakan Fix For: 4.1.1.CR1 1. Create Mobile Hybrid Project 2. Add Accelerometer testing page as described on phonegap wep page 3. Run Project on CordovaSim and/or Emulator and/or Android device 4. Open Acceleromer page ASSERT: App is displaying data from Accelerometer 5. Open index.html page add some widget from jQuery Mobile pallete and save 6. Repeat step 3. and 4. ERROR: App is not displaying data from Accelerometer. Even DeviceReady isnot fired When adding widget from jQuery Mobile pallete also this reference to jQuery Mobile java script file is added {noformat} <script src="http://code.jquery.com/mobile/1.3.1/jquery.mobile-1.3.1.min.js"></script> {noformat} and it seems is somehow brealing Cordova API functionality. Once removed from index.html application is displaying data from Acceleromer again -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15887) Application wizard: typing application name is delayed, sluggish, poor responsiveness

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15887?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15887: ------------------------------------------ I also noticed that the multi validators are called 3x whereas I would expect 1x when hitting a key. This is apparently a known issue: http://www.eclipse.org/forums/index.php/t/155446/ > Application wizard: typing application name is delayed, sluggish, poor responsiveness > ------------------------------------------------------------------------------------- > > Key: JBIDE-15887 > URL: https://issues.jboss.org/browse/JBIDE-15887 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.1.CR1 > > Attachments: openshift-jbds7-ga.ogv, openshift-jbds71Beta1b.ogv, openshift.ogv, visual-vm.png > > > If you launch the Application wizard to create a new application you get the first wizard page where you should provide a name for your new application. Typing into this text-field is very slow, the inputs make it to the widget in a very delayed manner. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15887) Application wizard: typing application name is delayed, sluggish, poor responsiveness

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15887?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15887 at 11/7/13 6:01 AM: ------------------------------------------------------------------- I have no clue what is causing this. I tried with a fresh Eclipse IDE and it didnt help. Connecting jvisualvm did not unveils major activity of org.eclipse.core.internal.databinding.beans.BeanPropertyHelper#readProperty right after native GTK (most likely key events) !visual-vm.png! I noticed that when you change the name of the application you trigger 3 MultiValidators: - ApplicationConfigurationWizardPage#NewApplicationNameValidator - ProjectAndServerAdapterSettingsWizardPage#UseExistingOpenProjectValidator - GitCloningSettingsWizardPage#RepoPathValidationStatusProvider This is required since the application name is the name of the new workspace project that the application will get imported into (thus needs to be validated aka made sure no such proj exists). And the application name is also used for the folder that the application is cloned into (and thus needs to get validated, too). The lagging improves a lot as soon as I comment some validators (just the body, not the creation). was (Author: adietish): I have no clue what is causing this. I tried with a fresh Eclipse IDE and it didnt help. Connecting jvisualvm did not unveils major activity of org.eclipse.core.internal.databinding.beans.BeanPropertyHelper#readProperty right after native GTK (most likely key events) !visual-vm.png! > Application wizard: typing application name is delayed, sluggish, poor responsiveness > ------------------------------------------------------------------------------------- > > Key: JBIDE-15887 > URL: https://issues.jboss.org/browse/JBIDE-15887 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.1.CR1 > > Attachments: openshift-jbds7-ga.ogv, openshift-jbds71Beta1b.ogv, openshift.ogv, visual-vm.png > > > If you launch the Application wizard to create a new application you get the first wizard page where you should provide a name for your new application. Typing into this text-field is very slow, the inputs make it to the widget in a very delayed manner. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15887) Application wizard: typing application name is delayed, sluggish, poor responsiveness

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15887?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15887: ------------------------------------------ I have no clue what is causing this. I tried with a fresh Eclipse IDE and it didnt help. Connecting jvisualvm did not unveils major activity of org.eclipse.core.internal.databinding.beans.BeanPropertyHelper#readProperty right after native GTK (most likely key events) !visual-vm.png! > Application wizard: typing application name is delayed, sluggish, poor responsiveness > ------------------------------------------------------------------------------------- > > Key: JBIDE-15887 > URL: https://issues.jboss.org/browse/JBIDE-15887 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.1.CR1 > > Attachments: openshift-jbds7-ga.ogv, openshift-jbds71Beta1b.ogv, openshift.ogv, visual-vm.png > > > If you launch the Application wizard to create a new application you get the first wizard page where you should provide a name for your new application. Typing into this text-field is very slow, the inputs make it to the widget in a very delayed manner. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15887) Application wizard: typing application name is delayed, sluggish, poor responsiveness

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15887?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15887: ------------------------------------- Attachment: visual-vm.png > Application wizard: typing application name is delayed, sluggish, poor responsiveness > ------------------------------------------------------------------------------------- > > Key: JBIDE-15887 > URL: https://issues.jboss.org/browse/JBIDE-15887 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.1.CR1 > > Attachments: openshift-jbds7-ga.ogv, openshift-jbds71Beta1b.ogv, openshift.ogv, visual-vm.png > > > If you launch the Application wizard to create a new application you get the first wizard page where you should provide a name for your new application. Typing into this text-field is very slow, the inputs make it to the widget in a very delayed manner. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15763) Various issues when viewing WFK quickstarts with the internal web browser

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15763?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-15763: ----------------------------------------- It might be possible to specify a different XULRunner installation to use: http://www.eclipse.org/swt/faq.php#specifyxulrunner This however implies that we embed XULRunner somewhere. > Various issues when viewing WFK quickstarts with the internal web browser > ------------------------------------------------------------------------- > > Key: JBIDE-15763 > URL: https://issues.jboss.org/browse/JBIDE-15763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: xulrunner > Affects Versions: 4.1.1.Alpha2 > Reporter: Vineet Reynolds > > Various issues are encountered when viewing some of the WFK quickstarts in the Eclipse internal browser: > * HTML5 elements like header, footer, aside, etc. are not displayed as block elments. since xulrunner 1.9 when used as the internal browser, does not support these elements. This is related to JBIDE-10689. > * Newer JavaScript features provided in EcmaScript5, like Array.isArray or window.getComputedStyle (that are available in browsers supported by WFK) are not available in xulrunner 1.9, leading to non-execution of JavaScript in frameworks like jQueryMobile 1.3.x, Lo-Dash 1.3.1 etc. > We should document that the internal web browser is not recommended as a substitute for a real browser. Given the current situation, > * we should recommend the use of an external browser, or > * we should toggle the default web browser to an external web browser -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15894) EAP 6.1 (instead of 6.1+) string in final stage of new server wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15894?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-15894: ---------------------------------- Attachment: eap-6.1.png > EAP 6.1 (instead of 6.1+) string in final stage of new server wizard > -------------------------------------------------------------------- > > Key: JBIDE-15894 > URL: https://issues.jboss.org/browse/JBIDE-15894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0.Beta1b B493 > Reporter: Martin Malina > Fix For: 4.1.1.CR1 > > Attachments: eap-6.1.png > > > There is still one place where the string wasn't properly updated from EAP 6.1 to 6.1+. > (See JBIDE-15774 and JBIDE-15751 for reference of other jiras dealing with this.) > When you create a server, on the last page where you choose either local or remote server, at the top there is JBoss Enterprise Application Platform 6.1 even though I'm creating EAP 6.2, so it's a bit confusing. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15894) EAP 6.1 (instead of 6.1+) string in final stage of new server wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15894?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-15894: ---------------------------------- Description: There is still one place where the string wasn't properly updated from EAP 6.1 to 6.1+. (See JBIDE-15774 and JBIDE-15751 for reference of other jiras dealing with this.) When you create a server, on the last page where you choose either local or remote server, at the top there is JBoss Enterprise Application Platform 6.1 even though I'm creating EAP 6.2, so it's a bit confusing. !eap-6.1.png! was: There is still one place where the string wasn't properly updated from EAP 6.1 to 6.1+. (See JBIDE-15774 and JBIDE-15751 for reference of other jiras dealing with this.) When you create a server, on the last page where you choose either local or remote server, at the top there is JBoss Enterprise Application Platform 6.1 even though I'm creating EAP 6.2, so it's a bit confusing. > EAP 6.1 (instead of 6.1+) string in final stage of new server wizard > -------------------------------------------------------------------- > > Key: JBIDE-15894 > URL: https://issues.jboss.org/browse/JBIDE-15894 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0.Beta1b B493 > Reporter: Martin Malina > Fix For: 4.1.1.CR1 > > Attachments: eap-6.1.png > > > There is still one place where the string wasn't properly updated from EAP 6.1 to 6.1+. > (See JBIDE-15774 and JBIDE-15751 for reference of other jiras dealing with this.) > When you create a server, on the last page where you choose either local or remote server, at the top there is JBoss Enterprise Application Platform 6.1 even though I'm creating EAP 6.2, so it's a bit confusing. > !eap-6.1.png! -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15894) EAP 6.1 (instead of 6.1+) string in final stage of new server wizard

by Martin Malina (JIRA)

Martin Malina created JBIDE-15894: ------------------------------------- Summary: EAP 6.1 (instead of 6.1+) string in final stage of new server wizard Key: JBIDE-15894 URL: https://issues.jboss.org/browse/JBIDE-15894 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.1.Beta1 Environment: JBDS 7.1.0.Beta1b B493 Reporter: Martin Malina Fix For: 4.1.1.CR1 There is still one place where the string wasn't properly updated from EAP 6.1 to 6.1+. (See JBIDE-15774 and JBIDE-15751 for reference of other jiras dealing with this.) When you create a server, on the last page where you choose either local or remote server, at the top there is JBoss Enterprise Application Platform 6.1 even though I'm creating EAP 6.2, so it's a bit confusing. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15893) Remote server connection requires password even if not needed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15893?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-15893: ---------------------------------- Attachment: enter-password.png Screenshot: !enter-password.png! > Remote server connection requires password even if not needed > ------------------------------------------------------------- > > Key: JBIDE-15893 > URL: https://issues.jboss.org/browse/JBIDE-15893 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0.Beta1b B493 > Reporter: Martin Malina > Fix For: 4.1.1.CR1 > > Attachments: enter-password.png > > > When I create a remote server (EAP 6.1.1) and define the host, in order to browse for the server home directory eclipse needs to connect to the server. > It will ask me for credentials - so far so good. > But the problem is that the password field is required even if I don't want to fill it - I'm using rsa keys to log in to the machine and it has always worked for me - in the past I just left the password field blank and pressed OK and was connected. -- 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

12 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2013