[JBoss JIRA] (JBIDE-10818) OpenShift Express Console: different jobs have to block each other
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10818?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10818:
-------------------------------------
Fix Version/s: 4.1.x
(was: 4.0.x)
> OpenShift Express Console: different jobs have to block each other
> -------------------------------------------------------------------
>
> Key: JBIDE-10818
> URL: https://issues.jboss.org/browse/JBIDE-10818
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 3.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Xavier Coulon
> Fix For: 4.1.x
>
>
> The *OpenShift Express Console* allows you to delete applications, create new applications and will allow you to refresh the view. Those operations are executed in background jobs so that the Eclipse UI is not blocked in the meantime. We therefore have to setup scheduling rules on those jobs so that a refresh will wait until the delete is finished. To me the best way to achieve this is to create cathegories of jobs (ex. ApplicationJob, UserJob, etc.) that have the appropriate scheduling rules initialized (ex. ApplicationJobs operate on applications and therefore have to block UserJob that possibly operate on all applications.)
--
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, 6 months
[JBoss JIRA] (JBIDE-13114) openshift-java-client: improve how userAgent is passed to UrlConnectionClient
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13114?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13114:
-------------------------------------
Priority: Minor (was: Major)
> openshift-java-client: improve how userAgent is passed to UrlConnectionClient
> -----------------------------------------------------------------------------
>
> Key: JBIDE-13114
> URL: https://issues.jboss.org/browse/JBIDE-13114
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> clarify how the user-agent is set to the UrlConnectionHttpClient.
> You can actually set it to the constructor but also by a setter:
> {code:title=com.openshift.internal.client.httpclient.UrlConnectionHttpClient}
> public UrlConnectionHttpClient(String username, String password, String userAgent, boolean sslChecks, IMediaType requestMediaType, String acceptedMediaType, String version, String authKey, String authIV) {
> {code}
> {code:title=com.openshift.internal.client.httpclient.UrlConnectionHttpClient}
> public void setUserAgent(String userAgent) {
> this.userAgent = userAgent;
> }
> {code}
> Both variants are actually used in the library code:
> {code:title=com.openshift.internal.client.RestService}
> public RestService(String baseUrl, String clientId, IHttpClient client) {
> this.baseUrl = UrlUtils.ensureStartsWithHttps(baseUrl);
> this.client = client;
> client.setUserAgent(new RestServiceProperties().getUseragent(clientId));
> {code}
> {code:title=com.openshift.client.OpenShiftConnectionFactory}
> public IOpenShiftConnection getConnection(final String clientId, final String login, final String password,
> final String authKey, final String authIV, final String serverUrl,
> final boolean proxySet, final String proxyHost, final String proxyPort) throws OpenShiftException {
> Assert.notNull(clientId);
> Assert.notNull(login);
> Assert.notNull(password);
> Assert.notNull(serverUrl);
>
> if (proxySet) {
> System.setProperty("proxyHost", proxyHost);
> System.setProperty("proxyPort", proxyPort);
> }
> try {
> final IHttpClient httpClient = new UrlConnectionHttpClientBuilder().setCredentials(login, password, authKey, authIV)
> .client();
>
> final IRestService service = new RestService(serverUrl, clientId, httpClient);
> return getConnection(service, login, password);
> } catch (FileNotFoundException e) {
> throw new OpenShiftException(e, "Failed to establish connection for user ''{0}}''", login);
> } catch (IOException e) {
> throw new OpenShiftException(e, "Failed to establish connection for user ''{0}}''", login);
> }
> }
> {code}
--
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, 6 months
[JBoss JIRA] (JBIDE-13348) Cannot deploy BPEL project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13348?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-13348:
-------------------------------------
{code}
Author: rob.stryker(a)jboss.com
Date: 2013-01-09 07:01:36 -0500 (Wed, 09 Jan 2013)
New Revision: 44650
Modified:
branches/jbosstools-3.3.x/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/util/ServerConverter.java
Log:
JBDS-2437 JBIDE-13348 - added the old method back in addition to the new
Modified: branches/jbosstools-3.3.x/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/util/ServerConverter.java
===================================================================
--- branches/jbosstools-3.3.x/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/util/ServerConverter.java 2013-01-08 15:53:10 UTC (rev 44649)
+++ branches/jbosstools-3.3.x/as/plugins/org.jboss.ide.eclipse.as.core/jbosscore/org/jboss/ide/eclipse/as/core/util/ServerConverter.java 2013-01-09 12:01:36 UTC (rev 44650)
@@ -115,6 +115,17 @@
return dep;
}
+ public static IDeployableServer getDeployableServer(IServer server) {
+ if (server == null) {
+ return null;
+ }
+ IDeployableServer dep = (IDeployableServer) server.getAdapter(IDeployableServer.class);
+ if (dep == null) {
+ dep = (IDeployableServer) server.loadAdapter(IDeployableServer.class, new NullProgressMonitor());
+ }
+ return dep;
+ }
+
public static DeployableServerBehavior getDeployableServerBehavior(IServer server) {
if (server == null)
return null;
{code}
> Cannot deploy BPEL project
> --------------------------
>
> Key: JBIDE-13348
> URL: https://issues.jboss.org/browse/JBIDE-13348
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers, SOA Tooling
> Affects Versions: 3.3.2
> Reporter: Andrej Podhradsky
> Assignee: Rob Stryker
> Priority: Blocker
>
> After installing AS feature from JBoss Tools CR2 core the bpel project cannot be deployed to server.
> See JBDS-2437
--
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, 6 months
[JBoss JIRA] (JBIDE-13145) Cannot "Tail files" if I remove connection from OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13145?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13145:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have an application on OpenShift that you imported to your workspace (and got a project for it)
# ASSERT: make sure that you have a server adapter for this project
# EXEC: in *OpenShift Explorer*: select the connection that you used when importing and pick *Remove from View*
# EXEC: go to your server adapter and pick *OpenShift->Tail files*
Result:
Nothing happens. In the log you'll spot:
{quote}
!ENTRY org.jboss.tools.openshift.express.ui 4 0 2012-11-23 22:49:23.742
!MESSAGE Failed to retrieve Application from the selected Server.
Please verify that the associated OpenShift Application still exists.
{quote}
Expected:
The connection wizard pops up with the server, username filled in from the settings in your project (<project>/.settings/org.jboss.tools.openshift.express.ui.prefs)
was:
# ASSERT: make sure that you have an application on OpenShift that you imported to your workspace (and got a project for it)
# ASSERT: make sure that you have a server adapter for this project
# EXEC: in *OpenShift Explorer*: select the connection that you used when importing and pick *Remove from View"
# EXEC: go to your server adapter and pick *OpenShift->Tail files*
Result:
Nothing happens. In the log you'll spot:
{quote}
!ENTRY org.jboss.tools.openshift.express.ui 4 0 2012-11-23 22:49:23.742
!MESSAGE Failed to retrieve Application from the selected Server.
Please verify that the associated OpenShift Application still exists.
{quote}
Expected:
The connection wizard pops up with the server, username filled in from the settings in your project (<project>/.settings/org.jboss.tools.openshift.express.ui.prefs)
> Cannot "Tail files" if I remove connection from OpenShift Explorer
> ------------------------------------------------------------------
>
> Key: JBIDE-13145
> URL: https://issues.jboss.org/browse/JBIDE-13145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.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
13 years, 6 months
[JBoss JIRA] (JBIDE-13248) openshift-java-client: provide nice names, versions and descriptions for cartridges
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13248?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13248:
-------------------------------------
Priority: Minor (was: Major)
> openshift-java-client: provide nice names, versions and descriptions for cartridges
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13248
> URL: https://issues.jboss.org/browse/JBIDE-13248
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> The response (protocol v1.3) when querying the OpenShift REST service for cartridges (standalone and embeddable ones) was enhanced lately. It now offers
> * <display-name />
> * <version />
> * <description />
> eventually
> * <website />
> * <help-topics />
> We should add at least these 3 in the ICartridge.
> There are also further interesting informations:
> * <tag />
> * <scales-from /> & <scales-to />
> * <scales-with />
--
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, 6 months
[JBoss JIRA] (JBIDE-11427) Importing OpenShift maven application requires user to update project configuration
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11427?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-11427:
-------------------------------------
Summary: Importing OpenShift maven application requires user to update project configuration (was: Import on OpenShift Express Console requires Project configuration is not up-to-date with pom.xml. Run project configuration update)
> Importing OpenShift maven application requires user to update project configuration
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-11427
> URL: https://issues.jboss.org/browse/JBIDE-11427
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, openshift
> Affects Versions: 3.3.0.Beta2
> Environment: Mac OSX Lion - 32bit Eclipse with Tools 3.3.0.Beta2b
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 3.3.x, 4.0.x
>
>
> When selecting "Import Application" on a openshift deployed application (not in the current workspace) requires the end-user to update his project configuration (Maven->Update Project Configuration)
--
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, 6 months