September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20535) wildfly-bmt quickstart fails with unsupported content validation error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20535?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20535: ------------------------------------- quickstart "wildfly-greeter" also suffers from this error. > wildfly-bmt quickstart fails with unsupported content validation error > ---------------------------------------------------------------------- > > Key: JBIDE-20535 > URL: https://issues.jboss.org/browse/JBIDE-20535 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > > Importing the above quickstart fails validation with the following (cryptic) error: > The persistence.xml file does not have supported content for this JPA platform. > Stack-overflow on a similar topic: http://stackoverflow.com/questions/3701901/eclipse-does-not-recognize-con... > Link to bugzilla from 2008 that claims issue is fixed: https://bugs.eclipse.org/bugs/show_bug.cgi?id=251323 > I have absolutely no idea how to fix this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20401: --------------------------------------------- just a check - I assume the *default* url will still be http://tools.jboss.org/documentation/howto/openshift3_getting_started.html so we actually can fix its content indepencent on what ends up on openshift.com, right ? So just don't forget to make sure http://tools.jboss.org/documentation/howto/openshift3_getting_started.html will actually exist - even if it just redirects to https://docs.openshift.com/enterprise/3.0/admin_guide/install/overview.html > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20538) wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-20538: ----------------------------------- Summary: wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate Key: JBIDE-20538 URL: https://issues.jboss.org/browse/JBIDE-20538 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Reporter: Rob Stryker Root cause here seems to be that the xsd on the web url http://www.jboss.org/schema/jbossas/jboss-ejb3-spec-2_0.xsd has a schemaLocation=jboss-ejb3-2_0.xsd relative path -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20447) 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20447?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20447: --------------------------------------------- if they are not in the RHEL7 node group then that sounds like a bug to me OR that this node is not something that are available in the shared pool of servers. > 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component > ------------------------------------------------------------------ > > Key: JBIDE-20447 > URL: https://issues.jboss.org/browse/JBIDE-20447 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Konstantin Marmalyukov > Labels: testfailure > Fix For: 4.3.0.CR1 > > > *2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component:* > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_mast... > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds) > [Search for Test Failure JIRAs in JBIDE 4.3.0.CR1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...] > ----- > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowserOrLink{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowserOrLink} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.268</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowserOrLink(BrowserUtilTest.java:51) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowserOrLink</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} > * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowser{color} (failing for 11 builds) > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowser} > <case> > <age>11</age> > <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className> > <duration>0.0030</duration> > <errorStackTrace>java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) > </errorStackTrace> > <failedSince>776</failedSince> > <name>testCreateBrowser</name> > <skipped>false</skipped> > <status>FAILED</status> > </case> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20529: ------------------------------------- Ignore previous comment. The repo had been given new branches and I was working off old examples. > Master JIRA for XML Validation Problems > --------------------------------------- > > Key: JBIDE-20529 > URL: https://issues.jboss.org/browse/JBIDE-20529 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples, server > Reporter: Rob Stryker > > This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20100: --------------------------------------------- thanks for the screencast, here are some initial comments then later on some concerns: a) I assume the dialog does not show up if there is just one connector available and it is GA'ed (non-early access), right ? b) it should automatically select an option - I suggest the supported version and after that what user chose last. c) earlyaccess should not be the first item in the list. d) how do I disable earlyaccess so it will remove the EA updatesite from the list of updatesites it will look at ? and now the issue with this approach: Once you have installed something from early access the earlyaccess updatesite is added to your jbds install and thus the choice you have here really does not guarantee you that the GA bits will be installed over what is in the earlyaccess. IMO, once a user the first time have said yes to earlyaccess and thus *enabled* earlyaccess he don't really have a choice anymore until he disables it. About the making JBDS users aware of using older JBDS - that was the main issue in this jira and I suggested a few times now how to do it (introduce a new connector type or certification which won't install anything but provide a way to tell users where to get things from). It is not an either or situation we have here - we need this (to stop having jiras and discussions about Fuse etc. missing from the field) AND we need to investe in having Fuse build compatible enough with JBDS - but the latter haven't worked the last 4 years and i'm sure we won't be much better of in the future nor does enabling earlyacccess by default work (as described above). What is so difficult/wrong about providing a way for us to tell users to go use another version for download ? (sure - it hurts my professional soul having to do it, but not handling it is no longer an option). > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > Attachments: JBIDE-20100-2.png > > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20537) wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-20537: ----------------------------------- Summary: wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate Key: JBIDE-20537 URL: https://issues.jboss.org/browse/JBIDE-20537 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Affects Versions: 4.3.0.CR1 Reporter: Rob Stryker Even after fixing https://issues.jboss.org/browse/JBIDE-20536 to import some namespaces using exact schema locations on the web, wildfly-ejb-multi-server-app-one-ejb fails to validate. The file jboss-ejb3.xml has the following content (trimmed for brevity): {code} <jboss:ejb-jar (cut out xml:ns stuff) version="3.1" impl-version="2.0"> <enterprise-beans> </enterprise-beans> <assembly-descriptor> </assembly-descriptor> </jboss:ejb-jar> {code} Unfortunately, empty enterprise-beans tags are invalid according to the xsd against which this is validated. Error message as follows: {code} cvc-complex-type.2.4.b: The content of element 'enterprise-beans' is not complete. One of '{"http:// java.sun.com/xml/ns/javaee":session, "http://java.sun.com/xml/ns/javaee":entity, "http:// java.sun.com/xml/ns/javaee":message-driven}' is expected. {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20479) broken images in JBT/JBDS Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20479?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-20479: ------------------------------------ Fedora 22, OpenJDK 1.8.0_51 > broken images in JBT/JBDS Central > --------------------------------- > > Key: JBIDE-20479 > URL: https://issues.jboss.org/browse/JBIDE-20479 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.CR1 > > Attachments: broken-images-central-JBDS9CR1.png, broken-images-central-JBT-JBDS.png > > > Broken images. See screenshot. The first image, for the HTML5 project, links to this: > file:///home/nboldt/eclipse/workspace-clean45-2/.metadata/.plugins/org.jboss.tools.central/images/1206740293/images%2Fwizards%2Fhtml5.png > But that won't load in my browser. > Instead, THIS image DOES load: > file:///home/nboldt/eclipse/workspace-clean45-2/.metadata/.plugins/org.jboss.tools.central/images/1206740293/images%252Fwizards%252Fhtml5.png > Seems you need one extra level of escapes: `%252F` instead of just `%2F` for those slashes ( / ). > Could your filenames simply be images-wizards-html5.png to avoid the need for hexcode escapes? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20536) Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-20536: ----------------------------------- Summary: Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements Key: JBIDE-20536 URL: https://issues.jboss.org/browse/JBIDE-20536 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Reporter: Rob Stryker Several errors fail with the following error message: Referenced file contains errors (file:/home/rob/code/fuseide/fuseide/targetplatform/target/org.fusesource.ide.targetplatform.target.repo/../../../../../jbtools/github/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." The schema seems to fail to resolve any elements that have 'jboss' in them, for example: {code} <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/> {code} When looking at the entire xsd space, I see no attempt to reference or import any remote schema or any jboss schema url or namespace. The offending schema file is here: {code}<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.jboss.com/xml/ns/javaee" xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:javaee="http://java.sun.com/xml/ns/javaee" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.0">   <xs:import namespace="http://java.sun.com/xml/ns/javaee"/> <xs:element name="ejb" type="javaee:jboss-ejb-beanType"/> <xs:element name="ejb-jar" type="javaee:jboss-ejb-jarType"/> <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/> <xs:element name="destination-jndi-name" type="xs:string" /> <xs:element name="distinct-name" type="xs:string"> <xs:annotation> <xs:documentation> The distinct-name for this EJB module. </xs:documentation> </xs:annotation> </xs:element> </xs:schema> {code} Perhaps I'm not understanding xml enough, but I kinda agree with the validator here, in that there's no clear way to resolve any of the jboss-* elements. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20535) wildfly-bmt quickstart fails with unsupported content validation error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20535?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20535: ------------------------------------- wildfly-cmt and wildfly-deltaspike-beanbuilder fail with same error. Updating namespace urls to point to redirected locations also does not fix the problem and seems unrelated. > wildfly-bmt quickstart fails with unsupported content validation error > ---------------------------------------------------------------------- > > Key: JBIDE-20535 > URL: https://issues.jboss.org/browse/JBIDE-20535 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > > Importing the above quickstart fails validation with the following (cryptic) error: > The persistence.xml file does not have supported content for this JPA platform. > Stack-overflow on a similar topic: http://stackoverflow.com/questions/3701901/eclipse-does-not-recognize-con... > Link to bugzilla from 2008 that claims issue is fixed: https://bugs.eclipse.org/bugs/show_bug.cgi?id=251323 > I have absolutely no idea how to fix this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2015