March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21453) Server Adapter: use rsync flag instead of local filtered-copy

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21453?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-21453: ---------------------------------- Sprint: devex #4 March 2016 > Server Adapter: use rsync flag instead of local filtered-copy > ------------------------------------------------------------- > > Key: JBIDE-21453 > URL: https://issues.jboss.org/browse/JBIDE-21453 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Xavier Coulon > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > With https://github.com/openshift/origin/issues/6143 *oc rsync* now allows specific white-listed flag to be used. > Our current implementation works around this by doing a local copy where excluded bits are filtered (not copied). We need to use exclusion flags if available. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21823) Unable to re-edit Service config

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21823?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21823: ----------------------------------- Workaround Description: close the editor (cancel the current changes) refresh the OpenShift Explorer view open the editor again. > Unable to re-edit Service config > -------------------------------- > > Key: JBIDE-21823 > URL: https://issues.jboss.org/browse/JBIDE-21823 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > > Once a service config has been changed, closing and reopening the config editor does not reveal the latest config, which then causes 409 error when saving subsequent changes, making it impossible to submit new changes. > Steps to reproduce: > - select a service in the OpenShift Explorer > - click on the {{Edit...}} command. > - in the JSON editor for the service config, note the resource version. Eg: > {code} > { > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38301", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > }, > ... > {code} > - make some changes and save > - the service config version should have incremented: > {code} > { > "kind" : "Service", > "apiVersion" : "v1", > "metadata" : { > "name" : "jee-sample", > "namespace" : "sample", > "selfLink" : "/api/v1/namespaces/sample/services/jee-sample", > "uid" : "5663ba0f-da47-11e5-ab9d-525400659b2e", > "resourceVersion" : "38390", > "creationTimestamp" : "2016-02-23T16:06:03Z", > "labels" : {"app" : "jee-sample"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftWebConsole"} > } > .... > {code} > - close the config editor > - re-open the config editor > *ASSERT: the editor displays the latest config* > *FAIL the editor displays the initial config* > *Also, on subsequent changes, the OpenShift server responds with a {{409}} error because the new config to save is based out-dated version* > {code} > Could not update "[sample] Service : jee-sample.json" for project "sample" : services "jee-sample" cannot be updated: the object has been modified; please apply your changes to the latest version and try again > Could not update resource jee-sample: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "services \"jee-sample\" cannot be updated: the object has been modified; please apply your changes to the latest version and try again", > "reason": "Conflict", > "details": { > "name": "jee-sample", > "kind": "services" > }, > "code": 409 > } > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21943) Errors validating jboss-ejb3.xml

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21943?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21943: -------------------------------------- Assignee: Rob Stryker > Errors validating jboss-ejb3.xml > -------------------------------- > > Key: JBIDE-21943 > URL: https://issues.jboss.org/browse/JBIDE-21943 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Final > Reporter: Bartosz Spyrko-Śmietanko > Assignee: Rob Stryker > Priority: Minor > > Trying to include urn:trans-timeout element in jboss-ejb3.xml leads to a validation failure: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'tx:trans-timeout'. One of '{"http://java.sun.com/xml/ns/javaee":container-transaction-entry}' is expected. > {noformat} > and a warning: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'tx:trans-timeout'. One of '{"http://java.sun.com/xml/ns/javaee":container-transaction-entry}' is expected. > {noformat} > Example jboss-ejb3.xml file: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:tx="urn:trans-timeout" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation=" > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd > http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd > urn:trans-timeout http://www.jboss.org/j2ee/schema/trans-timeout-1_0.xsd > " > > <assembly-descriptor> > <container-transaction> > <description>foobar</description> > <method> > <ejb-name>foobar</ejb-name> > <method-name>foobar</method-name> > </method> > <trans-attribute>Supports</trans-attribute> > <tx:trans-timeout> > <tx:timeout>100</tx:timeout> > <tx:unit>Seconds</tx:unit> > </tx:trans-timeout> > </container-transaction> > </assembly-descriptor> > </jboss:ejb-jar> > {noformat} > I think the issue might be related to how Eclipse matches the entries in XML Catalog - giving priority to schemaLocation over namespace match [1]. Since the trans-transactions schema is only referenced via urn:trans-timeout namespace in the catalog, Eclipse tries to download it from jboss.org, fails and never uses the version shipped with Tools. > [1] https://wiki.eclipse.org/Using_the_XML_Catalog#FAQ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21943) Errors validating jboss-ejb3.xml

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21943?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21943: ----------------------------------- Issue Type: Bug (was: Feature Request) > Errors validating jboss-ejb3.xml > -------------------------------- > > Key: JBIDE-21943 > URL: https://issues.jboss.org/browse/JBIDE-21943 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.3.0.Final > Reporter: Bartosz Spyrko-Śmietanko > Priority: Minor > > Trying to include urn:trans-timeout element in jboss-ejb3.xml leads to a validation failure: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'tx:trans-timeout'. One of '{"http://java.sun.com/xml/ns/javaee":container-transaction-entry}' is expected. > {noformat} > and a warning: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'tx:trans-timeout'. One of '{"http://java.sun.com/xml/ns/javaee":container-transaction-entry}' is expected. > {noformat} > Example jboss-ejb3.xml file: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:tx="urn:trans-timeout" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation=" > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd > http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd > urn:trans-timeout http://www.jboss.org/j2ee/schema/trans-timeout-1_0.xsd > " > > <assembly-descriptor> > <container-transaction> > <description>foobar</description> > <method> > <ejb-name>foobar</ejb-name> > <method-name>foobar</method-name> > </method> > <trans-attribute>Supports</trans-attribute> > <tx:trans-timeout> > <tx:timeout>100</tx:timeout> > <tx:unit>Seconds</tx:unit> > </tx:trans-timeout> > </container-transaction> > </assembly-descriptor> > </jboss:ejb-jar> > {noformat} > I think the issue might be related to how Eclipse matches the entries in XML Catalog - giving priority to schemaLocation over namespace match [1]. Since the trans-transactions schema is only referenced via urn:trans-timeout namespace in the catalog, Eclipse tries to download it from jboss.org, fails and never uses the version shipped with Tools. > [1] https://wiki.eclipse.org/Using_the_XML_Catalog#FAQ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21943) Errors validating jboss-ejb3.xml

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21943?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21943: ----------------------------------- Component/s: upstream > Errors validating jboss-ejb3.xml > -------------------------------- > > Key: JBIDE-21943 > URL: https://issues.jboss.org/browse/JBIDE-21943 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Final > Reporter: Bartosz Spyrko-Śmietanko > Priority: Minor > > Trying to include urn:trans-timeout element in jboss-ejb3.xml leads to a validation failure: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'tx:trans-timeout'. One of '{"http://java.sun.com/xml/ns/javaee":container-transaction-entry}' is expected. > {noformat} > and a warning: > {noformat} > cvc-complex-type.2.4.a: Invalid content was found starting with element 'tx:trans-timeout'. One of '{"http://java.sun.com/xml/ns/javaee":container-transaction-entry}' is expected. > {noformat} > Example jboss-ejb3.xml file: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:tx="urn:trans-timeout" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation=" > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd > http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd > urn:trans-timeout http://www.jboss.org/j2ee/schema/trans-timeout-1_0.xsd > " > > <assembly-descriptor> > <container-transaction> > <description>foobar</description> > <method> > <ejb-name>foobar</ejb-name> > <method-name>foobar</method-name> > </method> > <trans-attribute>Supports</trans-attribute> > <tx:trans-timeout> > <tx:timeout>100</tx:timeout> > <tx:unit>Seconds</tx:unit> > </tx:trans-timeout> > </container-transaction> > </assembly-descriptor> > </jboss:ejb-jar> > {noformat} > I think the issue might be related to how Eclipse matches the entries in XML Catalog - giving priority to schemaLocation over namespace match [1]. Since the trans-transactions schema is only referenced via urn:trans-timeout namespace in the catalog, Eclipse tries to download it from jboss.org, fails and never uses the version shipped with Tools. > [1] https://wiki.eclipse.org/Using_the_XML_Catalog#FAQ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21911) Icons for Service and Route are not whole

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21911?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-21911 at 3/22/16 4:23 PM: -------------------------------------------------------------- I resized [~crobson]'s icons and added them to the git repo. I'll wait to see if we can't get less pixellated icons from her designer, before resolving this issue was (Author: fbricon): I cropped [~crobson]'s icons and added them to the git repo. I'll wait to see if we can't get less pixellated icons from her designer, before resolving this issue > Icons for Service and Route are not whole > ----------------------------------------- > > Key: JBIDE-21911 > URL: https://issues.jboss.org/browse/JBIDE-21911 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: icons.png, pficon-route-black.png, pficon-service-black.png > > > Icons for OpenShift 3 services and routing are cut off. The upper arrow on an icon is not whole, the sharp part is missing. See on the screenshot: > !icons.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21911) Icons for Service and Route are not whole

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21911?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21911: ------------------------------------- I cropped [~crobson]'s icons and added them to the git repo. I'll wait to see if we can't get less pixellated icons from her designer, before resolving this issue > Icons for Service and Route are not whole > ----------------------------------------- > > Key: JBIDE-21911 > URL: https://issues.jboss.org/browse/JBIDE-21911 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: icons.png, pficon-route-black.png, pficon-service-black.png > > > Icons for OpenShift 3 services and routing are cut off. The upper arrow on an icon is not whole, the sharp part is missing. See on the screenshot: > !icons.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21911) Icons for Service and Route are not whole

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21911?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21911: -------------------------------- Fix Version/s: 4.3.1.CR1 > Icons for Service and Route are not whole > ----------------------------------------- > > Key: JBIDE-21911 > URL: https://issues.jboss.org/browse/JBIDE-21911 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: icons.png, pficon-route-black.png, pficon-service-black.png > > > Icons for OpenShift 3 services and routing are cut off. The upper arrow on an icon is not whole, the sharp part is missing. See on the screenshot: > !icons.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21911) Icons for Service and Route are not whole

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21911?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21911: ----------------------------------- Assignee: Fred Bricon > Icons for Service and Route are not whole > ----------------------------------------- > > Key: JBIDE-21911 > URL: https://issues.jboss.org/browse/JBIDE-21911 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: openshift_v3 > Attachments: icons.png, pficon-route-black.png, pficon-service-black.png > > > Icons for OpenShift 3 services and routing are cut off. The upper arrow on an icon is not whole, the sharp part is missing. See on the screenshot: > !icons.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21932) Log a warning if a runtime file contains incorrect/missing path

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21932?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21932: -------------------------------------- Fix Version/s: 4.4.0.Alpha1 Assignee: Alexey Kazakov (was: Rob Stryker) Resolution: Done > Log a warning if a runtime file contains incorrect/missing path > --------------------------------------------------------------- > > Key: JBIDE-21932 > URL: https://issues.jboss.org/browse/JBIDE-21932 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.1.CR1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > If runtime_locations.properties file has some incorrect path and we can't find a folder for this path it would be much easier to detect a problem if we log a warning message. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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