June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20985) XML Schema validation fails when importing external schema

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20985?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20985: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > XML Schema validation fails when importing external schema > ---------------------------------------------------------- > > Key: JBIDE-20985 > URL: https://issues.jboss.org/browse/JBIDE-20985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.3.Final > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Priority: Critical > Fix For: LATER > > Attachments: bean-service-quickstart.zip, simplerSYexample.zip > > > Product JIRA for upstream bug - https://bugs.eclipse.org/bugs/show_bug.cgi?id=315741 > This is to track the upstream bug in Eclipse that we need to pull in to JBDS at some point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21743) no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21743?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21743: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > no declaration can be found for element "context:component-scan" in spring-kitchensink-basic quickstart > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21743 > URL: https://issues.jboss.org/browse/JBIDE-21743 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: LATER > > > Importing "spring-kitchensink-basic" EAP7 quickstart raises an error: > {noformat}Description Resource Path Location Type > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'context:component-scan'. jboss-as-spring-mvc-context.xml /jboss-spring-kitchensink-basic/src/main/webapp/WEB-INF line 26 XML Problem > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21695) 25 xml validation errors in

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21695?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21695: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > 25 xml validation errors in > ---------------------------- > > Key: JBIDE-21695 > URL: https://issues.jboss.org/browse/JBIDE-21695 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Reporter: Rob Stryker > Fix For: LATER > > > 25 xml validation errors on the git@github.com:jboss-developer/jboss-eap-quickstarts.git quickstart repository. > Description Resource Path Location Type > cvc-complex-type.2.4.a: Invalid content was found starting with element 'jee:interceptor-binding'. One of '{"http://java.sun.com/xml/ns/javaee":description, "http://java.sun.com/xml/ns/javaee":ejb-name}' is expected. jboss-ejb3.xml /jboss-ejb-security-interceptors/src/main/resources/META-INF line 31 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'aop:aspectj-autoproxy'. tools-config.xml /jboss-spring-petclinic/src/main/resources/spring line 40 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'context:component-scan'. mvc-core-config.xml /jboss-spring-petclinic/src/main/resources/spring line 39 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jdbc:embedded-database'. test-context.xml /jboss-spring-kitchensink-matrixvariables/src/test/resources line 40 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jee:jndi-lookup'. infrastructure.xml /jboss-spring-kitchensink-asyncrequestmapping/src/main/resources/META-INF/spring line 28 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jee:jndi-lookup'. infrastructure.xml /jboss-spring-kitchensink-matrixvariables/src/main/resources/META-INF/spring line 28 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'jee:jndi-lookup'. infrastructure.xml /jboss-spring-kitchensink-springmvctest/src/main/resources/META-INF/spring line 28 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'mvc:annotation-driven'. jboss-as-spring-mvc-context.xml /jboss-spring-kitchensink-controlleradvice/src/main/webapp/WEB-INF line 28 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'mvc:annotation-driven'. test-context.xml /jboss-spring-kitchensink-springmvctest/src/test/resources line 48 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'tx:jta-transaction-manager'. infrastructure.xml /jboss-spring-kitchensink-asyncrequestmapping/src/main/resources/META-INF/spring line 36 XML Problem > cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'tx:jta-transaction-manager'. infrastructure.xml /jboss-spring-kitchensink-matrixvariables/src/main/resources/META-INF/spring line 36 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-bean-validation/src/test/resources line 20 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-cdi-veto/src/test/resources line 20 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-kitchensink-jsp/src/test/resources line 21 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-kitchensink-ml-ear-ejb/src/test/resources line 21 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-shrinkwrap-resolver/src/test/resources line 21 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-spring-kitchensink-asyncrequestmapping/functional-tests/src/test/resources line 19 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-spring-kitchensink-basic/functional-tests/src/test/resources line 19 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-spring-kitchensink-matrixvariables/functional-tests/src/test/resources line 19 XML Problem > cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jboss-wsat-simple/src/test/resources line 21 XML Problem > cvc-elt.1: Cannot find the declaration of element 'beans'. business-config.xml /jboss-spring-petclinic/src/main/resources/spring line 27 XML Problem > cvc-elt.1: Cannot find the declaration of element 'datasources'. greeter-spring-quickstart-ds.xml /jboss-spring-greeter/src/main/webapp/WEB-INF line 23 XML Problem > Referenced file contains errors (http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/javaee_web_...). For more information, right click on the message in the Problems View and select "Show Details..." context-handlers.xml /jboss-wsat-simple/src/main/webapp/WEB-INF/classes line 1 XML Problem > Referenced file contains errors (jar:file:/home/rob/apps/eclipse/jbds/studio/plugins/org.jboss.tools.as.catalog_3.1.1.Beta2-v20160121-0132-B81.jar!/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-ejb-multi-server-app-one-ejb/src/main/resources/META-INF line 1 XML Problem > Referenced file contains errors (jar:file:/home/rob/apps/eclipse/jbds/studio/plugins/org.jboss.tools.as.catalog_3.1.1.Beta2-v20160121-0132-B81.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-ejb3.xml /jboss-jts-application-component-2/src/main/resources/META-INF line 1 XML Problem -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20538) wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20538?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20538: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > wildfly-ejb-multi-server-app-one-ejb quickstart upstream schema error > --------------------------------------------------------------------- > > Key: JBIDE-20538 > URL: https://issues.jboss.org/browse/JBIDE-20538 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Rob Stryker > Labels: xml_validation_schema_error > Fix For: LATER > > > 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 (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20701) [eap7 quickstarts] Eclipse Errors validating jboss-ejb-security-interceptors quickstart

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20701?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-20701: -------------------------------- Fix Version/s: LATER (was: 4.4.x) Bulk move all schema issues to 'LATER' because they take a lot of time to re-verify and they rarely make any progress. :| > [eap7 quickstarts] Eclipse Errors validating jboss-ejb-security-interceptors quickstart > --------------------------------------------------------------------------------------- > > Key: JBIDE-20701 > URL: https://issues.jboss.org/browse/JBIDE-20701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Labels: xml_validation_quickstart_content, xml_validation_quickstarts_eap7, xml_validation_schema_error > Fix For: LATER > > Attachments: 20529_security_interceptors_1.png > > > The above quickstart's file jboss-ejb3.xml indicates two errors. The first error seems to be a problem with the upstream / online schema, and I'm not sure if this is fixable in the quickstart or not. The second error may either be an error in the quickstart, or an error in the xsds, or, possibly, an error in eclipse validation. I am having trouble figuring out which. > *Error 1:* > Referenced file contains errors (jar:file:/home/rob/apps/eclipse/builds/mars_sr1_w_jbt/eclipse/plugins/ > org.jboss.tools.as.catalog_3.1.0.CR1-v20150911-0311-B31.jar!/schema/xsd/jboss-ejb3-spec-2_0.xsd). > Further details can be seen in attachment "20529_security_interceptors_1.png", > *Error 2:* > The current file in the quicksttarts has the following content: > {code} > <jee:assembly-descriptor> > <ci:container-interceptors> > <jee:interceptor-binding> > <ejb-name>IntermediateEJB</ejb-name> > <interceptor-class>org.jboss.as.quickstarts.ejb_security_interceptors.ServerSecurityInterceptor</interceptor-class> > </jee:interceptor-binding> > // removed 2nd for brevity > </ci:container-interceptors> > </jee:assembly-descriptor> > {code} > There are a few noted problems here. > 1) Validation insists that one jee:ejb-name element must live inside the container-interceptors but before the interceptor-binding. This basically means that that set of container-interceptors is only valid for one ejb. > 2) Validation also insists that ANOTHER jee:ejb-name ALSO live INSIDE the interceptor-binding > 3) If you have multiple interceptor bindings, only the first must have a jee:ejb-name OUTSIDE of it. > After a lot of spit-balling, the only valid xml I've managed to come up with that validates properly is: > {code} > <jee:assembly-descriptor> > <ci:container-interceptors> > <jee:ejb-name>IntermediateEJB</jee:ejb-name> > <ci:interceptor-binding> > <jee:ejb-name>IntermediateEJB</jee:ejb-name> > <jee:interceptor-class>org.jboss.as.quickstarts.ejb_security_interceptors.ServerSecurityInterceptor</jee:interceptor-class> > </ci:interceptor-binding> > </ci:container-interceptors> > <ci:container-interceptors> > <jee:ejb-name>SecuredEJB</jee:ejb-name> > <ci:interceptor-binding> > <jee:ejb-name>SecuredEJB</jee:ejb-name> > <jee:interceptor-class>org.jboss.as.quickstarts.ejb_security_interceptors.ServerSecurityInterceptor</jee:interceptor-class> > </ci:interceptor-binding> > </ci:container-interceptors> > </jee:assembly-descriptor> > {code} > You'll note there's a lot more namespacing going on in the elements, and that we now have two container-interceptors as opposed to one, because both are for different EJBs. You'll also note that the ejb-name must be declared twice, or else validation fails. This is most likely an error in the heirarchy / nesting of the xsd's, but I am not an expert in that regard. > So the above xml would be a good workaround for the quickstarts. Any other fix would require investigation of the xsd's by someone more qualified than I am. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24582) Runtime Environment appears twice in server editor for remote eap

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24582?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24582: ------------------------------------- I have a PR for testing. This seems important enough to pass it to QE for a review. https://github.com/jbosstools/jbosstools-server/pull/520 > Runtime Environment appears twice in server editor for remote eap > ----------------------------------------------------------------- > > Key: JBIDE-24582 > URL: https://issues.jboss.org/browse/JBIDE-24582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > Attachments: runtime-environment-twice.png > > > I just wanted to verify that remote servers are working and came across a situation where the Runtime Environment field was there twice: > !runtime-environment-twice.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24582) Runtime Environment appears twice in server editor for remote eap

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24582?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24582: ------------------------------------- Upstream change was: https://bugs.eclipse.org/bugs/show_bug.cgi?id=513486 > Runtime Environment appears twice in server editor for remote eap > ----------------------------------------------------------------- > > Key: JBIDE-24582 > URL: https://issues.jboss.org/browse/JBIDE-24582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > Attachments: runtime-environment-twice.png > > > I just wanted to verify that remote servers are working and came across a situation where the Runtime Environment field was there twice: > !runtime-environment-twice.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24582) Runtime Environment appears twice in server editor for remote eap

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24582?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24582: ------------------------------------- Upstream changes have made our workaround unnecessary. I will most likely delete the class that is providing the second combo. The downside of this is that the official combo does not include an option for 'no runtime', so the ability to remove the runtime is broken. But I don't think this was a primary use-case, as there's no benefit to removing a runtime other than easier testing of some specific bugs ;) > Runtime Environment appears twice in server editor for remote eap > ----------------------------------------------------------------- > > Key: JBIDE-24582 > URL: https://issues.jboss.org/browse/JBIDE-24582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > Attachments: runtime-environment-twice.png > > > I just wanted to verify that remote servers are working and came across a situation where the Runtime Environment field was there twice: > !runtime-environment-twice.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24582) Runtime Environment appears twice in server editor for remote eap

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24582?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-24582: -------------------------------- Fix Version/s: 4.5.0.AM2 > Runtime Environment appears twice in server editor for remote eap > ----------------------------------------------------------------- > > Key: JBIDE-24582 > URL: https://issues.jboss.org/browse/JBIDE-24582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM2 > > Attachments: runtime-environment-twice.png > > > I just wanted to verify that remote servers are working and came across a situation where the Runtime Environment field was there twice: > !runtime-environment-twice.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23350) Deploy Docker Wizard: Prompt to enter credentials contains Finish button

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23350?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23350. --------------------------------- Resolution: Out of Date This no longer seems replicatable and the UI differs from the description, so I suspect [~adietish] has already made large fixes here. Specifically, when i right-click an image and select 'deploy to openshift', a dialog appears which seems to recognize both the openshift and docker connections immediately. The 'next' button is enabled, and the 'finish' button is not. So I suspect this is out of date. > Deploy Docker Wizard: Prompt to enter credentials contains Finish button > ------------------------------------------------------------------------ > > Key: JBIDE-23350 > URL: https://issues.jboss.org/browse/JBIDE-23350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > > When opening Deploy Image to OpenShift wizard from context menu of a docker image and there was no OpenShift connection selected, OpenShift connection wizard is shown with Finish button, although connection is active (connected). There should be opened the Deploy Image to OpenShift with the connection wizard page and it should have next button. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017