February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21662: ---------------------------------------- Assignee: Rob Stryker (was: Andre Dietisheim) > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21662: ------------------------------------------ [~rob.stryker] can you please look into this? > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21662: ---------------------------------------- Assignee: Andre Dietisheim > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21662: ------------------------------------- Fix Version/s: 4.3.1.CR1 > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21665) Scaling OS3 application does not work properly

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21665?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21665: ------------------------------------------ [~mlabuda] it looks to me as if refreshing before down-scaling would work around this issue? [~jcantrill] looks like we should reload the resource that we changed since it was modified on the server side? > Scaling OS3 application does not work properly > ---------------------------------------------- > > Key: JBIDE-21665 > URL: https://issues.jboss.org/browse/JBIDE-21665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > Attachments: edit_error.png > > > When I am trying to scale application via tooling, first attempt to set replicas amount works but every consecutive attempt to edit same resource fails. See following screenshot of the error followed by stack trace > !edit_error.png! > {code} > com.openshift.restclient.OpenShiftException: Could not update resource eap-app-1: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:480) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:247) > at org.jboss.tools.openshift.internal.ui.property.OpenShiftResourceDocumentProvider$2.run(OpenShiftResourceDocumentProvider.java:92) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.restclient.http.HttpClientException: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "replicationControllers \"eap-app-1\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "eap-app-1", > "kind": "replicationControllers" > }, > "code": 409 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:226) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:191) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.put(UrlConnectionHttpClient.java:119) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:243) > ... 2 more > Caused by: java.io.IOException: Server returned HTTP response code: 409 for URL: https://10.1.2.2:8443/api/v1/namespaces/project01/replicationcontrollers/... > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1840) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:187) > ... 4 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19910) Add w3 schemes to XML catalog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19910?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-19910 at 2/15/16 11:29 AM: --------------------------------------------------------------- Already present in JBT: http://jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd Already included in wtp source editing: http://java.sun.com/xml/ns/j2ee/connector_1_6.xsd - redirects http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd - redirects http://java.sun.com/xml/ns/javaee/application_7.xsd - redirects http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/connector_1_6.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_6.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_serv... Misc to be added: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit... http://docs.oasis-open.org/xacml/access_control-xacml-2.0-context-schema-... http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-policy-sche... http://docs.oasis-open.org/xacml/access_control-xacml-2.0-policy-schema-o... http://glassfish.org/dtds/glassfish-resources_1_5.dtd http://glassfish.org/dtds/glassfish-web-app_3_0-1.dtd http://java.sun.com/dtd/properties.dtd http://maven.apache.org/xsd/assembly-1.1.2.xsd http://www.infinispan.org/schemas/infinispan-config-6.0.xsd http://www.puppycrawl.com/dtds/configuration_1_2.dtd http://www.w3.org/2001/XMLSchema.dtd http://www.w3.org/2001/datatypes.dtd http://www.w3.org/2006/03/addressing/ws-addr.xsd http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd Not even a schema file, cannot be added to catalog: http://www.ws-i.org/Testing/Tools/2004/12/AP10_BP11_SSBP10_TAD.xml http://www.ws-i.org/Testing/Tools/2005/01/SSBP10_BP11_TAD_1-0.xml JBoss to be added: http://jboss.org/schema/arquillian/arquillian_1_0.xsd http://jboss.org/ironjacamar/schema/ironjacamar_1_0.xsd http://jboss.org/j2ee/schema/jboss-web_6_0.xsd http://jboss.org/j2ee/dtd/service-ref_4_0.dtd was (Author: rob.stryker): Already present in JBT: http://jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd Already included in wtp source editing: http://java.sun.com/xml/ns/j2ee/connector_1_6.xsd - redirects http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd - redirects http://java.sun.com/xml/ns/javaee/application_7.xsd - redirects http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/connector_1_6.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_6.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_serv... Misc to be added: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit... http://docs.oasis-open.org/xacml/access_control-xacml-2.0-context-schema-... http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-policy-sche... http://docs.oasis-open.org/xacml/access_control-xacml-2.0-policy-schema-o... http://glassfish.org/dtds/glassfish-resources_1_5.dtd http://glassfish.org/dtds/glassfish-web-app_3_0-1.dtd http://java.sun.com/dtd/properties.dtd http://maven.apache.org/xsd/assembly-1.1.2.xsd http://www.infinispan.org/schemas/infinispan-config-6.0.xsd http://www.puppycrawl.com/dtds/configuration_1_2.dtd http://www.w3.org/2001/XMLSchema.dtd http://www.w3.org/2001/datatypes.dtd http://www.w3.org/2006/03/addressing/ws-addr.xsd http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd http://www.ws-i.org/Testing/Tools/2004/12/AP10_BP11_SSBP10_TAD.xml http://www.ws-i.org/Testing/Tools/2005/01/SSBP10_BP11_TAD_1-0.xml JBoss to be added: http://jboss.org/schema/arquillian/arquillian_1_0.xsd http://jboss.org/ironjacamar/schema/ironjacamar_1_0.xsd http://jboss.org/j2ee/schema/jboss-web_6_0.xsd http://jboss.org/j2ee/dtd/service-ref_4_0.dtd > Add w3 schemes to XML catalog > ----------------------------- > > Key: JBIDE-19910 > URL: https://issues.jboss.org/browse/JBIDE-19910 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Fix For: 4.3.x > > > We should add w3 schemes which are used in our quickstarts/examples to XML catalog because: > 1) w3 servers are intentionally slow > 2) it seems that wsdl validator does no caching of previously downloaded schemes > I will take a look at examples and list schemes here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21666) Set correct OpenShift resource name for Repplication controller in properties view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21666: ------------------------------------------ [~jcantrill] dare to comment? > Set correct OpenShift resource name for Repplication controller in properties view > ---------------------------------------------------------------------------------- > > Key: JBIDE-21666 > URL: https://issues.jboss.org/browse/JBIDE-21666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3 > > At the moment we have following OpenShift resources listed for a project in Properties view: > * Builds > * Build Configs > * Deployment Configs > * Pods > * Deployments > * Image Streams > * Routes > * Services > What is misleading is having "Deployment Configs" and "Deployments". We are trying to copy web-UI, as far as I know. But in the web-UI under Deployments are placed "Deployment Configs". We, under "Deployments" in properties view, have "Replication Controllers". So its misleading for me. I think we should rename our Deployment Configs to Deployment and our Deployments to Replication Controllers, which are missing in web-ui because the most significant functionality accessible via Replication Controllers is editable in web-ui through overview page (e.g spinner for amount of pods). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21669) Enable easy scaling of OpenShift 3 applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21669?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21669: ------------------------------------- Fix Version/s: 4.3.1.CR1 > Enable easy scaling of OpenShift 3 applications > ----------------------------------------------- > > Key: JBIDE-21669 > URL: https://issues.jboss.org/browse/JBIDE-21669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > Fix For: 4.3.1.CR1 > > > In Web-UI there is a spinner to set amount of running pods and we don't have something similar and user friendly in our tooling. At the moment to scale up/down an OpenShift 3 application, it is required to modify replication controller (which is a bit buggy see JBIDE-21665 and whole work flow is not quite user friendly). It would be nice to have a context menu item in context menu of a service, something like "Scale Up" enabled all the time and "Scale Down" in case there are at least 2 pods running. Or it could be "Add Pod" "Remove Pod" or something similar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19910) Add w3 schemes to XML catalog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19910?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19910: ------------------------------------- Already present in JBT: http://jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd Already included in wtp source editing: http://java.sun.com/xml/ns/j2ee/connector_1_6.xsd - redirects http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd - redirects http://java.sun.com/xml/ns/javaee/application_7.xsd - redirects http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/connector_1_6.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_6.xsd http://oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_serv... Misc to be added: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit... http://docs.oasis-open.org/xacml/access_control-xacml-2.0-context-schema-... http://docs.oasis-open.org/xacml/2.0/access_control-xacml-2.0-policy-sche... http://docs.oasis-open.org/xacml/access_control-xacml-2.0-policy-schema-o... http://glassfish.org/dtds/glassfish-resources_1_5.dtd http://glassfish.org/dtds/glassfish-web-app_3_0-1.dtd http://java.sun.com/dtd/properties.dtd http://maven.apache.org/xsd/assembly-1.1.2.xsd http://www.infinispan.org/schemas/infinispan-config-6.0.xsd http://www.puppycrawl.com/dtds/configuration_1_2.dtd http://www.w3.org/2001/XMLSchema.dtd http://www.w3.org/2001/datatypes.dtd http://www.w3.org/2006/03/addressing/ws-addr.xsd http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd http://www.ws-i.org/Testing/Tools/2004/12/AP10_BP11_SSBP10_TAD.xml http://www.ws-i.org/Testing/Tools/2005/01/SSBP10_BP11_TAD_1-0.xml JBoss to be added: http://jboss.org/schema/arquillian/arquillian_1_0.xsd http://jboss.org/ironjacamar/schema/ironjacamar_1_0.xsd http://jboss.org/j2ee/schema/jboss-web_6_0.xsd http://jboss.org/j2ee/dtd/service-ref_4_0.dtd > Add w3 schemes to XML catalog > ----------------------------- > > Key: JBIDE-19910 > URL: https://issues.jboss.org/browse/JBIDE-19910 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: upstream, webservices > Affects Versions: 4.3.0.Alpha2 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Fix For: 4.3.x > > > We should add w3 schemes which are used in our quickstarts/examples to XML catalog because: > 1) w3 servers are intentionally slow > 2) it seems that wsdl validator does no caching of previously downloaded schemes > I will take a look at examples and list schemes here. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21675) Text editor of OpenShift resource should provide more information about resource

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21675?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21675: ------------------------------------- Fix Version/s: 4.3.1.CR1 > Text editor of OpenShift resource should provide more information about resource > -------------------------------------------------------------------------------- > > Key: JBIDE-21675 > URL: https://issues.jboss.org/browse/JBIDE-21675 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Fix For: 4.3.1.CR1 > > > When I choose Edit.. in context menu of an OpenShift resource, its open a new text editor with JSON of resource. Currently name/title of such text editor is in format "resource type : resource name" (example "Image Stream : bug-consolidator"). If I have more such editor opened, e.g. I have a staging project, testing project and production project with same resource name, it is difficult to find out to which resource the content of editor belongs (it is possible but it requires to read content and find namespace or selflink which contain project name). > It would be nice if editor of OpenShift resource would contain at least project name in its name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016