May 2016 - jbosstools-issues - Jboss List Archives

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

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21943?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21943. ------------------------------ > 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 > Fix For: 4.3.1.CR1 > > > 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)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3684. ----------------------------- Neither I could reproduce this, closing. > Preview pane in HTML editor fails with 404 error with OpenJDK > ------------------------------------------------------------- > > Key: JBDS-3684 > URL: https://issues.jboss.org/browse/JBDS-3684 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Priority: Critical > Labels: openjdk > Fix For: 9.1.0.CR1 > > Attachments: preview.png > > > The editor opens the file, and its palette is displayed - the preview pane shows a 404 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-21841: ------------------------------- Attachment: (was: screenshot-1.png) > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3878) Devstudio shortcuts have outdated version in their names (again)

by Jan Richter (JIRA)

Jan Richter created JBDS-3878: --------------------------------- Summary: Devstudio shortcuts have outdated version in their names (again) Key: JBDS-3878 URL: https://issues.jboss.org/browse/JBDS-3878 Project: Red Hat Developer Studio (DevStudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.0.0.Alpha1 Reporter: Jan Richter Assignee: Nick Boldt A while back wemoved the devstudio icons to show 9.1 as their version. It's time to update that since we've switched to 10.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3878) Devstudio shortcuts have outdated version in their names (again)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3878?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3878: ------------------------------ Description: A while back we moved the devstudio icons to show 9.1 as their version. It's time to update that since we've switched to 10.0. (was: A while back wemoved the devstudio icons to show 9.1 as their version. It's time to update that since we've switched to 10.0.) > Devstudio shortcuts have outdated version in their names (again) > ---------------------------------------------------------------- > > Key: JBDS-3878 > URL: https://issues.jboss.org/browse/JBDS-3878 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Nick Boldt > > A while back we moved the devstudio icons to show 9.1 as their version. It's time to update that since we've switched to 10.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21841) Shortened repo URL in Import wizard is weird

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21841?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-21841: ------------------------------- Attachment: screenshot-1.png > Shortened repo URL in Import wizard is weird > -------------------------------------------- > > Key: JBIDE-21841 > URL: https://issues.jboss.org/browse/JBIDE-21841 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, shortened_repo_url.png > > > When Importing an OpenShift 3 application via File - Import - Existing OpenShift Application, there is a wizard page to select a build config to import application repo. We should display repo name as styled text with style (grayed) and it should not be shorten or at least not like this when there is missing a part in the middle of URL. > !shortened_repo_url.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18697) Error deploying exploded war on windows; fs / copy error

by Heiko Kopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18697?page=com.atlassian.jira.plugi... ] Heiko Kopp commented on JBIDE-18697: ------------------------------------ Hello Max, thank you for your suggestions. We tried to find some steps to reproduce, but those reported in https://developer.jboss.org/message/907562 have been already sufficient. Regardless what we did, where the directories for deployment and/or temporary directory resided, the problem sometimes occurred and sometimes not. However, the JDK bug that has been found sounds like the problem we are facing here as after the problem arises, stopping the Wildfly is impossible. It seens the hanging thread is causing this. The only way to end Wildfly is to kill the Java process. I hope this bug will be fixed soon not only in OpenJDK but Oracle JDK too. It would be good to find out when it is fixed. Then we can test again. > Error deploying exploded war on windows; fs / copy error > -------------------------------------------------------- > > Key: JBIDE-18697 > URL: https://issues.jboss.org/browse/JBIDE-18697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.1.Final > > > https://developer.jboss.org/message/907562 > A user has reported that on windows, deploying a simple exploded war has failed with a copy error. This should be investigated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21228) DeploymentConfig for Deploying a docker image should point the image container to the imagestream

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21228?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21228: --------------------------------------- I've created it in tooling via context menu of a docker image. Image stream has been created as well. When created via command line "oc new-app openshift/hello-openshift" dc is following: https://gist.github.com/mlabuda/c5775f159d622860dc904364a2696057#file-dep... So when creating via tooling, image is referenced with docker.io too. Is this desired? > DeploymentConfig for Deploying a docker image should point the image container to the imagestream > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-21228 > URL: https://issues.jboss.org/browse/JBIDE-21228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Deploying a docker image from a local machine will create resources. When the image is pushed to OS, the DC should assume it will be namespaced to the same project in which the resources are created. Ref: https://gist.github.com/jcantrill/cb84b919e1a7a4791440#file-gistfile1-txt... > This image was deployed to the 'helloworld' namespace and the image spec should not include the original docker namespace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21228) DeploymentConfig for Deploying a docker image should point the image container to the imagestream

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21228?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21228: --------------------------------------- The specific value pointed to here is what the server substitutes into the DC based on how it is originally defined; if its pointed to an actual image, imagestreamtag, etc. Additionally, the 'openshift' namespace is special in that it is a library of various resources. How was this 'app' created? My guess is it was deployed by falling back to the image that was in the openshift namespace. If that was the case, this DC looks as I would expect. > DeploymentConfig for Deploying a docker image should point the image container to the imagestream > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-21228 > URL: https://issues.jboss.org/browse/JBIDE-21228 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Deploying a docker image from a local machine will create resources. When the image is pushed to OS, the DC should assume it will be namespaced to the same project in which the resources are created. Ref: https://gist.github.com/jcantrill/cb84b919e1a7a4791440#file-gistfile1-txt... > This image was deployed to the 'helloworld' namespace and the image spec should not include the original docker namespace. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21860) Include Docker tooling 1.2.2 in JBT 4.3.x TP

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21860?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21860. ------------------------------- Verified in 4.3.1. > Include Docker tooling 1.2.2 in JBT 4.3.x TP > -------------------------------------------- > > Key: JBIDE-21860 > URL: https://issues.jboss.org/browse/JBIDE-21860 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > Include Docker tooling 1.2.2 due March 19th, 2016 in JBoss Tools Target Platform for 4.3.1.CR1. This is a bug-fix only version (no new feature, no API change) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

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