September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18404) InAppBrowser struggles with POST

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18404?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18404: ------------------------------------- +1 to apply > InAppBrowser struggles with POST > -------------------------------- > > Key: JBIDE-18404 > URL: https://issues.jboss.org/browse/JBIDE-18404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.2.0.CR2 > > > The following inAppBrowserSamle doesn't work properly - > https://github.com/ibuziuk/google-api-oauth-phonegap -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-16066: ------------------------------------------- is this a new test? I don't recall ever seeing this particular combination run. Does anybody actually use this part of the WS functionality? > Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-16066 > URL: https://issues.jboss.org/browse/JBIDE-16066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.1.CR1 > Environment: JBDS 7.1.0 CR1, EAP-6.1 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR2 > > Attachments: topDownServer.log > > > Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible. > It works with other slider levels and all levels works when the server isn't started before the web service is created. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17670) Web Service Tester: JAX-WS request doesn't contain definition of SOAPAction

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17670?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-17670: -------------------------------------- Fix Version/s: 4.2.x (was: 4.2.0.CR2) > Web Service Tester: JAX-WS request doesn't contain definition of SOAPAction > --------------------------------------------------------------------------- > > Key: JBIDE-17670 > URL: https://issues.jboss.org/browse/JBIDE-17670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17670) Web Service Tester: JAX-WS request doesn't contain definition of SOAPAction

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17670?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-17670: ------------------------------------------- This is out of our hands as far as the Sun JDK goes, bumping to 4.2.x for now. > Web Service Tester: JAX-WS request doesn't contain definition of SOAPAction > --------------------------------------------------------------------------- > > Key: JBIDE-17670 > URL: https://issues.jboss.org/browse/JBIDE-17670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Brian Fitzpatrick > Priority: Critical > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18224) Table Selection has poor performance if "Verify Database Connection" is checked in previous step

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18224?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-18224: ----------------------------------------- Yes, it is supposed to be fixed in Forge 2.11.0.Final. > Table Selection has poor performance if "Verify Database Connection" is checked in previous step > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-18224 > URL: https://issues.jboss.org/browse/JBIDE-18224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR2 > > > If the "Verify Database Connection" *is checked* then there is very *poor performance* in the next step during tables selection on JPA: Generate Entities From Tables wizard. > I don't understand what is going on behind the scenes - but there is for sure some communication with DB happening. Not sure if this is necessary as the list of tables is read correctly and imho the list should be just checked if there is at least one table selected. > It works *without performance problems* if "Verify Database Connection" was *not checked* in previous step. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18277) Early Access features installed with abridged tools

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18277?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-18277. ------------------------------------ Resolution: Done Actually, Central already fetches last file from remote server so it doesn't require a change. > Early Access features installed with abridged tools > --------------------------------------------------- > > Key: JBIDE-18277 > URL: https://issues.jboss.org/browse/JBIDE-18277 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, updatesite > Affects Versions: 4.2.0.CR1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.2.0.CR2 > > Attachments: early-access.png > > > Right after installing JBT into Eclipse (whole Abridged JBoss Tools category) Central is showing that Early access features are installed, namely: > org.jboss.tools.jst.jsdt.feature (3.6.0.CR1-v20140904-0921-B61) and org.jboss.tools.jst.angularjs.feature (3.6.0.CR1-v20140904-0921-B61) > In freshly installed JBDS there is this same issue, but only org.jboss.tools.jst.jsdt.feature (3.6.0.CR1-v20140904-0921-B61) is shown in Early Access features. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3143) Closing the internal browser with JBDS 8.0.CR1 on RHEL 6.5 crashes JBDS8 - with Java8

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3143?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3143: ------------------------------------ futex(0x7f58ab0369d0, FUTEX_WAIT, 3269, NULL) = ? ERESTARTSYS (To be restarted) futex(0x7f58ab0369d0, FUTEX_WAIT, 3269, NULL) = ? ERESTARTSYS (To be restarted) futex(0x7f58ab0369d0, FUTEX_WAIT, 3269, NULL+++ killed by SIGSEGV (core dumped) +++ Stack trace - 150MB compressed - is here: https://dl.dropboxusercontent.com/u/12067552/core.3268.tar The problem is a bit random - it sometimes crashes when the browser reaches a page such as redhat.com, other times it crashes when the browser is closed. > Closing the internal browser with JBDS 8.0.CR1 on RHEL 6.5 crashes JBDS8 - with Java8 > ------------------------------------------------------------------------------------- > > Key: JBDS-3143 > URL: https://issues.jboss.org/browse/JBDS-3143 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 8.0.0.CR1 > Environment: RHEL 6.5 > java version "1.8.0" > Java(TM) SE Runtime Environment (build 1.8.0-b132) > Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode) > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.0.CR2 > > > To recreate: > * Start JBDS8 > * Open Internal Browser view > * Navigate to a site - such as www.redhat.com > * Close the browser - JBDS8 crashes -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-493) Add info for GTK3 issues and workaround

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-493?page=com.atlassian.jira.plug... ] Len DiMaggio commented on TOOLSDOC-493: --------------------------------------- I'd vote for documenting this - see the bugs here: https://issues.jboss.org/browse/JBIDE-17075?jql=project%20%3D%20JBIDE%20a... > Add info for GTK3 issues and workaround > ---------------------------------------- > > Key: TOOLSDOC-493 > URL: https://issues.jboss.org/browse/TOOLSDOC-493 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Release Notes > Affects Versions: 4.2.0.Beta1, 4.2.0.Final > Reporter: Jiri Peterka > Assignee: Len DiMaggio > Fix For: 4.2.0.Final > > > There are many serious issues related to GTK3 systems (Ubuntu, Fedora and other GNU/Linux distros). For example https://issues.jboss.org/browse/JBIDE-16315 . It would be good to mention that for OS containing GTK3 this tweak is needed to avoid these issues: > {code} > export SWT_GTK3=0 > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18224) Table Selection has poor performance if "Verify Database Connection" is checked in previous step

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18224?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18224: --------------------------------------- What was fixed? It seems jbosstools side has no changes. Is there forge related issue that was fixed in new version of forge included in JBoss Tools? > Table Selection has poor performance if "Verify Database Connection" is checked in previous step > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-18224 > URL: https://issues.jboss.org/browse/JBIDE-18224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR1 > Reporter: Pavol Srna > Assignee: Koen Aers > Priority: Critical > Labels: respin-b > Fix For: 4.2.0.CR2 > > > If the "Verify Database Connection" *is checked* then there is very *poor performance* in the next step during tables selection on JPA: Generate Entities From Tables wizard. > I don't understand what is going on behind the scenes - but there is for sure some communication with DB happening. Not sure if this is necessary as the list of tables is read correctly and imho the list should be just checked if there is at least one table selected. > It works *without performance problems* if "Verify Database Connection" was *not checked* in previous step. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18449) remove VJET from Central/Early Access

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18449?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-18449: --------------------------------------- I see no harm to remove VJet from EA and I agree with Mickael. I'd rather remove it completely before releasing it. > remove VJET from Central/Early Access > ------------------------------------- > > Key: JBIDE-18449 > URL: https://issues.jboss.org/browse/JBIDE-18449 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, target-platform, updatesite > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > > As approved by Fred, Burr, and Max: > {quote} > On 09/29/2014 11:15 AM, Burr Sutter wrote: > > +1 > > On Sep 29, 2014, at 10:04 AM, Fred Bricon <fbricon(a)redhat.com> wrote: > >> +1 to remove it. > >> Do we have usage tracking data about it? > >> Fred > >> > >> Le 29 sept. 2014 a 05:46, Max Rydahl Andersen <manderse(a)redhat.com> a ecrit : > >>> VJET is not maintained anymore it seems. > >>> We don't use it. We moved it from tech preview to earlyaccess, but now wondering why we even bother. > >>> Anyone object if we remove it from earlyaccess ? > >>> Anyone actually use it and found it good ? > {quote} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 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 September 2014