February 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2887) Drop OS X 10.7 Lion from the support matrix

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2887?page=com.atlassian.jira.plugin.... ] Fred Bricon resolved JBDS-2887. ------------------------------- Resolution: Done Resolving as per Len's comment on IRC : {quote} (15:15:55) ldimaggi: fbricon, we talked about this at the meeting last Thursday - all can be marked 'resolved' as the proper OS's will be tested {quote} > Drop OS X 10.7 Lion from the support matrix > ------------------------------------------- > > Key: JBDS-2887 > URL: https://issues.jboss.org/browse/JBDS-2887 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.1.0.GA > Reporter: Martin Malina > Assignee: Len DiMaggio > Labels: jbds711 > Fix For: 7.1.1.CR1, 8.0.0.Alpha2 > > > Since JBDS-2857 adds Mavericks to the support matrix, we can remove OS X 10.7 Lion and keep only the latest 2 versions of OS X. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16655) WS Tester should put a warning when parameter is invalid

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created JBIDE-16655: ----------------------------------------- Summary: WS Tester should put a warning when parameter is invalid Key: JBIDE-16655 URL: https://issues.jboss.org/browse/JBIDE-16655 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: webservices Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Brian Fitzpatrick Fix For: 4.2.0.Beta1 WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type. User should be allowed to submit the request with bad parameters if she really wants to. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16655) WS Tester should put a warning when parameter is invalid

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16655?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-16655: -------------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.2.0.Beta1) > WS Tester should put a warning when parameter is invalid > -------------------------------------------------------- > > Key: JBIDE-16655 > URL: https://issues.jboss.org/browse/JBIDE-16655 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Brian Fitzpatrick > Fix For: 4.1.2.CR1 > > > WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type. > User should be allowed to submit the request with bad parameters if she really wants to. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15593) WS Tester should put a warning when parameter is not valid

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15593?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-15593: -------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.CR1) > WS Tester should put a warning when parameter is not valid > ---------------------------------------------------------- > > Key: JBIDE-15593 > URL: https://issues.jboss.org/browse/JBIDE-15593 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.Beta1 > > > WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type. > User should be allowed to submit the request with bad parameters if she really wants to. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15593) WS Tester should put a warning when parameter is not valid

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15593?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-15593: -------------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.x) > WS Tester should put a warning when parameter is not valid > ---------------------------------------------------------- > > Key: JBIDE-15593 > URL: https://issues.jboss.org/browse/JBIDE-15593 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Brian Fitzpatrick > Fix For: 4.2.0.CR1 > > > WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type. > User should be allowed to submit the request with bad parameters if she really wants to. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16654) Wildfly server adapter is labeled experimental - CLONE

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-16654: ----------------------------------- Summary: Wildfly server adapter is labeled experimental - CLONE Key: JBIDE-16654 URL: https://issues.jboss.org/browse/JBIDE-16654 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Alpha2 Reporter: Pavol Srna Fix For: 4.2.0.Beta1 Released version of Wildfly is 8.0.0.Final and I assume we should change the server adapter label and remove the "(Experimental)" string. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16654) Wildfly server adapter is labeled experimental - CLONE

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16654?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-16654: -------------------------------- Fix Version/s: 4.1.2.CR1 (was: 4.2.0.Beta1) > Wildfly server adapter is labeled experimental - CLONE > ------------------------------------------------------ > > Key: JBIDE-16654 > URL: https://issues.jboss.org/browse/JBIDE-16654 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Alpha2 > Reporter: Pavol Srna > Fix For: 4.1.2.CR1 > > > Released version of Wildfly is 8.0.0.Final and I assume we should change the server adapter label and remove the "(Experimental)" string. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16646) Connection dialog: cannot connect to DEVENV

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16646?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16646: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have a DEVENV running # ASSERT: make sure that you have sse extensions turned off (-Djsse.enableSNIExtension=false) # EXEC: create a new connection to a devenv # ASSERT: in connection dialog: once you have provided all settings the certificate dialog shows up !devenv-certificate.png! # EXEC: accept it Result: Back in connection dialog you get an error: !connection-dialog-error.png! In Eclipse log you'll spot the following: {code} com.openshift.client.OpenShiftEndpointException: Could not request https://184.73.45.42/broker/rest/api: java.io.IOException: HTTPS hostname wrong: should be <184.73.45.42> at com.openshift.internal.client.RestService.request(RestService.java:136) at com.openshift.internal.client.RestService.request(RestService.java:109) at com.openshift.internal.client.RestService.request(RestService.java:92) at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:164) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:150) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:111) at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:227) at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:203) at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:247) at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.io.IOException: HTTPS hostname wrong: should be <184.73.45.42> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:186) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:154) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:129) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:88) at com.openshift.internal.client.RestService.request(RestService.java:175) at com.openshift.internal.client.RestService.request(RestService.java:123) ... 11 more Caused by: java.io.IOException: HTTPS hostname wrong: should be <184.73.45.42> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1675) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1673) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1671) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1244) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:169) ... 16 more Caused by: java.io.IOException: HTTPS hostname wrong: should be <184.73.45.42> at sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.java:652) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:577) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1300) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150) ... 15 more {code} Expected result: You should be able to successfully create the connection if you accept the certificate. was: # ASSERT: make sure that you have a DEVENV running # ASSERT: make sure that you have sse extensions turned off ( # EXEC: create a new connection to a devenv # ASSERT: in connection dialog: once you have provided all settings the certificate dialog shows up !devenv-certificate.png! # EXEC: accept it Result: Back in connection dialog you get an error: !connection-dialog-error.png! In Eclipse log you'll spot the following: {code} com.openshift.client.OpenShiftEndpointException: Could not request https://184.73.45.42/broker/rest/api: java.io.IOException: HTTPS hostname wrong: should be <184.73.45.42> at com.openshift.internal.client.RestService.request(RestService.java:136) at com.openshift.internal.client.RestService.request(RestService.java:109) at com.openshift.internal.client.RestService.request(RestService.java:92) at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:164) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:150) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:111) at org.jboss.tools.openshift.express.internal.core.connection.Connection.createUser(Connection.java:227) at org.jboss.tools.openshift.express.internal.core.connection.Connection.connect(Connection.java:203) at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:247) at org.jboss.tools.openshift.express.internal.ui.wizard.connection.ConnectionWizardPage$ConnectJob.run(ConnectionWizardPage.java:474) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) Caused by: com.openshift.internal.client.httpclient.HttpClientException: java.io.IOException: HTTPS hostname wrong: should be <184.73.45.42> at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:186) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:154) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:129) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:88) at com.openshift.internal.client.RestService.request(RestService.java:175) at com.openshift.internal.client.RestService.request(RestService.java:123) ... 11 more Caused by: java.io.IOException: HTTPS hostname wrong: should be <184.73.45.42> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1675) at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1673) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1671) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1244) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:169) ... 16 more Caused by: java.io.IOException: HTTPS hostname wrong: should be <184.73.45.42> at sun.net.www.protocol.https.HttpsClient.checkURLSpoofing(HttpsClient.java:652) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:577) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1300) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:150) ... 15 more {code} Expected result: You should be able to successfully create the connection if you accept the certificate. > Connection dialog: cannot connect to DEVENV > ------------------------------------------- > > Key: JBIDE-16646 > URL: https://issues.jboss.org/browse/JBIDE-16646 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: connection-dialog-error.png, devenv-certificate.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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15593) WS Tester should put a warning when parameter is not valid

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15593?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15593: --------------------------------------- Thanks, [~bfitzpat], this PR looks good to me ! > WS Tester should put a warning when parameter is not valid > ---------------------------------------------------------- > > Key: JBIDE-15593 > URL: https://issues.jboss.org/browse/JBIDE-15593 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Brian Fitzpatrick > Fix For: 4.2.x > > > WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type. > User should be allowed to submit the request with bad parameters if she really wants to. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16653) Forge integration should be able to take proxy info from eclipse

by Koen Aers (JIRA)

Koen Aers created JBIDE-16653: --------------------------------- Summary: Forge integration should be able to take proxy info from eclipse Key: JBIDE-16653 URL: https://issues.jboss.org/browse/JBIDE-16653 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 4.2.0.Beta1 -- 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, 1 month

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 February 2014