[JBoss JIRA] (JBIDE-14929) Verbose application type type dissapears after refreshing the connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14929?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14929:
------------------------------------------
Fixing JBIDE-14514 does not resolve this issue. The cause for the verbose labels to disappear is limited information when a standalone catridge object is created from the application listing:
{code}
{
"data":{
"aliases":[
"jbosstools.org"
],
"app_url":"http://springeap6-foobarz.rhcloud.com/",
...
"framework":"jbosseap-6.0",
...
"type":"application",
"version":"1.2"
}
{code}
Whereas when we list the available cartridges we have the full set of informations:
{code}
{
"data":[
{
"current_scale":0,
"description":"The leading open source Java EE6 application server for enterprise Java applications. Popular development frameworks include Seam, CDI, Weld, and Spring.",
"display_name":"JBoss Application Server 7.1",
"help_topics":{
"Developer Center":"https://openshift.redhat.com/community/developers"
},
"license":"ASL 2.0",
"license_url":"",
"name":"jbossas-7",
"scales_from":1,
"scales_to":-1,
"scales_with":"haproxy-1.4",
"supported_scales_from":1,
"supported_scales_to":-1,
"tags":[
"service",
"web_framework",
"java",
"jboss"
],
"type":"standalone",
"usage_rates":[
],
"version":7,
"website":"http://www.jboss.org"
},
...
"type":"cartridges",
"version":"1.2"
}
{code}
> Verbose application type type dissapears after refreshing the connection
> ------------------------------------------------------------------------
>
> Key: JBIDE-14929
> URL: https://issues.jboss.org/browse/JBIDE-14929
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: shorthand-label.png, type1.png, type2.png, verbose-application-type.png
>
>
> !type1.png! -> !type2.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, 7 months
[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15485?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15485 at 9/12/13 5:54 AM:
-------------------------------------------------------------------
The OpenShift jenkins plugin is actually using this functionality. We should migrate the jenkins plugin to set the system properties on its own:
https://github.com/openshift/jenkins-cloud-plugin/blob/master/src/main/ja...
{code}
service = new OpenShiftConnectionFactory().getConnection(
username, username, password, authKey, authIV, url);
service.setEnableSSLCertChecks(!ignoreBrokerCertCheck);
if (proxyHost != null && proxyHost.length() > 0) {
service.setProxySet(true);
service.setProxyHost(proxyHost.trim());
service.setProxyPort(Integer.toString(proxyPort));
}
{code}
was (Author: adietish):
The OpenShift jenkins plugin is actually using this functionality. We should migrate the jenkins plugin to set the system properties on its own:
https://github.com/openshift/jenkins-cloud-plugin/blob/master/src/main/ja...
{code}
service = new OpenShiftConnectionFactory().getConnection(
username, username, password, authKey, authIV, url);
service.setEnableSSLCertChecks(!ignoreBrokerCertCheck);
if (proxyHost != null && proxyHost.length() > 0) {
service.setProxySet(true);
service.setProxyHost(proxyHost.trim());
service.setProxyPort(Integer.toString(proxyPort));
}
{code}
> openshift-java-client: remove proxy settings from APIResource
> -------------------------------------------------------------
>
> Key: JBIDE-15485
> URL: https://issues.jboss.org/browse/JBIDE-15485
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
> The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 7 months
[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15485?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15485:
------------------------------------------
The OpenShift jenkins plugin is actually using this functionality. We should migrate the jenkins plugin to set the system properties on its own:
https://github.com/openshift/jenkins-cloud-plugin/blob/master/src/main/ja...
{code}
service = new OpenShiftConnectionFactory().getConnection(
username, username, password, authKey, authIV, url);
service.setEnableSSLCertChecks(!ignoreBrokerCertCheck);
if (proxyHost != null && proxyHost.length() > 0) {
service.setProxySet(true);
service.setProxyHost(proxyHost.trim());
service.setProxyPort(Integer.toString(proxyPort));
}
{code}
> openshift-java-client: remove proxy settings from APIResource
> -------------------------------------------------------------
>
> Key: JBIDE-15485
> URL: https://issues.jboss.org/browse/JBIDE-15485
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
> The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 7 months
[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-15485:
----------------------------------------
Summary: openshift-java-client: remove proxy settings from APIResource
Key: JBIDE-15485
URL: https://issues.jboss.org/browse/JBIDE-15485
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.2.0.Alpha1
The class APIResource offers some accessors that allow users to set the proxy system variables. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 7 months
[JBoss JIRA] (JBIDE-15485) openshift-java-client: remove proxy settings from APIResource
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15485?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15485:
-------------------------------------
Description: The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes). (was: The class APIResource offers some accessors that allow users to set the proxy system variables. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).)
> openshift-java-client: remove proxy settings from APIResource
> -------------------------------------------------------------
>
> Key: JBIDE-15485
> URL: https://issues.jboss.org/browse/JBIDE-15485
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
>
> The class APIResource offers some accessors that allow users to set the proxy system properties. This is a leftover when the old client code was migrated to the new RESTful service. This is IMHO a bad practice that should get removed since this affects all java code that's using HttpURLConnection and that's running on the same JVM (it sets the system properties for the jvm behind the scenes).
--
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, 7 months
[JBoss JIRA] (JBIDE-15028) When a remote wildfly server is stop the process keeps running
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15028?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-15028.
---------------------------------
Works properly now. Verified in JBDS 7.1.0.Alpha1 B378
> When a remote wildfly server is stop the process keeps running
> --------------------------------------------------------------
>
> Key: JBIDE-15028
> URL: https://issues.jboss.org/browse/JBIDE-15028
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.Beta2
> Environment: OS X Mountain Lion
> JBDS 7.0.0.Beta2a B345
> Wildfly 8.0.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.Alpha1
>
>
> Currently remote wildfly servers don't accept credentials - that is described in JBIDE-14979.
> When you encounter this issue and then try to stop the server, tooling will show Stopped, but the process will keep running on the remote server. See the steps to reproduce.
--
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, 7 months
[JBoss JIRA] (JBIDE-14979) Remote Wildfly cannot be started - password not accepted
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14979?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-14979.
---------------------------------
Verified in JBDS 7.1.0.Alpha1 B378
> Remote Wildfly cannot be started - password not accepted
> --------------------------------------------------------
>
> Key: JBIDE-14979
> URL: https://issues.jboss.org/browse/JBIDE-14979
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.1.0.Beta2
> Environment: OS X Mountain Lion - client
> RHEL 6 - remote server
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.1.1.Alpha1
>
>
> When I try to create a remote server using the wildfly adapter I get stuck on tools asking me for a password and not accepting the correct password.
> A side issue is that when you ignore the dialog and then try to stop the server, it will show [Stopped] in the server view, but the process will keep running on the server - it should kill the process.
--
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, 7 months