September 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5248) wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate in eclipse

by Rob Stryker (JIRA)

Rob Stryker created WFLY-5248: --------------------------------- Summary: wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate in eclipse Key: WFLY-5248 URL: https://issues.jboss.org/browse/WFLY-5248 Project: WildFly Issue Type: Bug Reporter: Rob Stryker Assignee: Jason Greene The quickstart wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate. The reason seems to be as follows: 1) jboss-ejb3.xml imports the xmlns:ci ="urn:container-interceptors:1.0" namespace. 2) boss-ejb-container-interceptors_1_0.xsd imports jboss-ejb3-spec-2_0.xsd namespace as follows: {code} <xs:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd {code} 3) jboss-ejb3-spec-2_0.xsd imports jboss-ejb3-2_0.xsd as follows: {code} <xs:import namespace="http://www.jboss.com/xml/ns/javaee" schemaLocation="jboss-ejb3-2_0.xsd"/> {code} The use of a relative path in step 3 breaks the eclipse validator. It would be best to use full urls that point to the actual xsd file. This fix will most likely require: 1) Changes to jboss-ejb3-spec-2_0.xsd in whatever repository it lives in 2) Changes to jboss-ejb3-spec-2_0.xsd on http://www.jboss.org/schema/jbossas/ 3) Changes to jboss-ejb3-spec-2_0.xsd inside jbosstools, which typically clones all updated files living at http://www.jboss.org/schema/jbossas/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5247) wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate in eclipse

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/WFLY-5247?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on WFLY-5247: ----------------------------------- A second problem with this file is in the namespace imports. {code} 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://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" {code} The URL http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd should be changed to http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/javaee/ejb-jar_3_1... since there's a current bug in eclipse that does not follow redirects. > wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate in eclipse > ---------------------------------------------------------------------------- > > Key: WFLY-5247 > URL: https://issues.jboss.org/browse/WFLY-5247 > Project: WildFly > Issue Type: Bug > Reporter: Rob Stryker > Assignee: Jason Greene > > wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate. > The xml file jboss-ejb3.xml file inside the project has the following content: > {code} > <?xml version="1.0" encoding="UTF-8"?> >  > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:security" > 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://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" impl-version="2.0"> > <enterprise-beans> > </enterprise-beans> > <assembly-descriptor> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > Unfortunately, the element "enterprise-beans" is not allowed to be empty. > A solution is to remove the empty "enterprise-beans" element. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5247) wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate in eclipse

by Rob Stryker (JIRA)

Rob Stryker created WFLY-5247: --------------------------------- Summary: wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate in eclipse Key: WFLY-5247 URL: https://issues.jboss.org/browse/WFLY-5247 Project: WildFly Issue Type: Bug Reporter: Rob Stryker Assignee: Jason Greene wildfly-ejb-multi-server-app-one-ejb quickstart fails to validate. The xml file jboss-ejb3.xml file inside the project has the following content: {code} <?xml version="1.0" encoding="UTF-8"?>  <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:security" 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://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1" impl-version="2.0"> <enterprise-beans> </enterprise-beans> <assembly-descriptor> </assembly-descriptor> </jboss:ejb-jar> {code} Unfortunately, the element "enterprise-beans" is not allowed to be empty. A solution is to remove the empty "enterprise-beans" element. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5246) Upgrade RESTEasy to 3.0.12.Final

by Weinan Li (JIRA)

Weinan Li created WFLY-5246: ------------------------------- Summary: Upgrade RESTEasy to 3.0.12.Final Key: WFLY-5246 URL: https://issues.jboss.org/browse/WFLY-5246 Project: WildFly Issue Type: Component Upgrade Components: REST Reporter: Weinan Li Assignee: Weinan Li -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-900) java.lang.IncompatibleClassChangeError error while using HashSets

by Pravasis Pattnaik (JIRA)

[ https://issues.jboss.org/browse/DROOLS-900?page=com.atlassian.jira.plugin... ] Pravasis Pattnaik updated DROOLS-900: ------------------------------------- Workaround Description: If I change it to Sets.newHashSet(e1,e2,..).contains(input) it fixes everything. (was: If I change it to Sets.newHashSet(e1,e2,..).contains(i) it fixes everything.) > java.lang.IncompatibleClassChangeError error while using HashSets > ----------------------------------------------------------------- > > Key: DROOLS-900 > URL: https://issues.jboss.org/browse/DROOLS-900 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 5.6.0.Final > Reporter: Pravasis Pattnaik > Assignee: Mario Fusco > Priority: Minor > Attachments: compiled-drl.txt, req.txt > > > In the compiled drl file we were using (Sets.newHashSet(e1,e2,..)).contains(x) then we get an exception java.lang.IncompatibleClassChangeError: Class XYZ does not implement the requested interface java.util.Collection on large input sets.Here XYZ is our input ruleRequest to be evaluated. If I change it to Sets.newHashSet(e1,e2,..).contains(x) it fixes everything. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-900) java.lang.IncompatibleClassChangeError error while using HashSets

by Pravasis Pattnaik (JIRA)

[ https://issues.jboss.org/browse/DROOLS-900?page=com.atlassian.jira.plugin... ] Pravasis Pattnaik updated DROOLS-900: ------------------------------------- Description: In the compiled drl file we were using (Sets.newHashSet(e1,e2,..)).contains(input) then we get an exception java.lang.IncompatibleClassChangeError: Class XYZ does not implement the requested interface java.util.Collection on large input sets.Here XYZ is our input ruleRequest to be evaluated. If I change it to Sets.newHashSet(e1,e2,..).contains(input) it fixes everything. (was: In the compiled drl file we were using (Sets.newHashSet(e1,e2,..)).contains(x) then we get an exception java.lang.IncompatibleClassChangeError: Class XYZ does not implement the requested interface java.util.Collection on large input sets.Here XYZ is our input ruleRequest to be evaluated. If I change it to Sets.newHashSet(e1,e2,..).contains(x) it fixes everything.) > java.lang.IncompatibleClassChangeError error while using HashSets > ----------------------------------------------------------------- > > Key: DROOLS-900 > URL: https://issues.jboss.org/browse/DROOLS-900 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 5.6.0.Final > Reporter: Pravasis Pattnaik > Assignee: Mario Fusco > Priority: Minor > Attachments: compiled-drl.txt, req.txt > > > In the compiled drl file we were using (Sets.newHashSet(e1,e2,..)).contains(input) then we get an exception java.lang.IncompatibleClassChangeError: Class XYZ does not implement the requested interface java.util.Collection on large input sets.Here XYZ is our input ruleRequest to be evaluated. If I change it to Sets.newHashSet(e1,e2,..).contains(input) it fixes everything. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-900) java.lang.IncompatibleClassChangeError error while using HashSets

by Pravasis Pattnaik (JIRA)

Pravasis Pattnaik created DROOLS-900: ---------------------------------------- Summary: java.lang.IncompatibleClassChangeError error while using HashSets Key: DROOLS-900 URL: https://issues.jboss.org/browse/DROOLS-900 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 5.6.0.Final Reporter: Pravasis Pattnaik Assignee: Mario Fusco Priority: Minor Attachments: compiled-drl.txt, req.txt In the compiled drl file we were using (Sets.newHashSet(e1,e2,..)).contains(x) then we get an exception java.lang.IncompatibleClassChangeError: Class XYZ does not implement the requested interface java.util.Collection on large input sets.Here XYZ is our input ruleRequest to be evaluated. If I change it to Sets.newHashSet(e1,e2,..).contains(x) it fixes everything. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-900) java.lang.IncompatibleClassChangeError error while using HashSets

by Pravasis Pattnaik (JIRA)

[ https://issues.jboss.org/browse/DROOLS-900?page=com.atlassian.jira.plugin... ] Pravasis Pattnaik updated DROOLS-900: ------------------------------------- Workaround Description: If I change it to Sets.newHashSet(e1,e2,..).contains(i) it fixes everything. (was: If I change it to Sets.newHashSet(e1,e2,..).contains(x) it fixes everything.) > java.lang.IncompatibleClassChangeError error while using HashSets > ----------------------------------------------------------------- > > Key: DROOLS-900 > URL: https://issues.jboss.org/browse/DROOLS-900 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 5.6.0.Final > Reporter: Pravasis Pattnaik > Assignee: Mario Fusco > Priority: Minor > Attachments: compiled-drl.txt, req.txt > > > In the compiled drl file we were using (Sets.newHashSet(e1,e2,..)).contains(x) then we get an exception java.lang.IncompatibleClassChangeError: Class XYZ does not implement the requested interface java.util.Collection on large input sets.Here XYZ is our input ruleRequest to be evaluated. If I change it to Sets.newHashSet(e1,e2,..).contains(x) it fixes everything. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5245) [Quickstart] application-component-2 fails xml validation in eclipse

by Rob Stryker (JIRA)

Rob Stryker created WFLY-5245: --------------------------------- Summary: [Quickstart] application-component-2 fails xml validation in eclipse Key: WFLY-5245 URL: https://issues.jboss.org/browse/WFLY-5245 Project: WildFly Issue Type: Bug Reporter: Rob Stryker Assignee: Jason Greene jts/application-component-2/src/main/resources/META-INF/jboss-ejb3.xml file includes: {code} <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:iiop="urn:iiop" 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:iiop jboss-ejb-iiop_1_0.xsd" {code} The line "urn:iiop jboss-ejb-iiop_1_0.xsd" is clearly problematic and provides no evidence of where it might pull this xsd from. I suggest replacing it with urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5244) bean-validation quickstart fails to validate due to non-compliant arquillian.xml

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/WFLY-5244?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on WFLY-5244: ----------------------------------- If it turns out that arquillian_1_0.xsd is modified to fix this bug by adding the property element to the schema, (rather than removing the property from the quickstart) I'd like to request that the schema be added to http://www.jboss.org/schema/jbossas/ for easy mirroring of all of our relevant schema into JBoss Tools. > bean-validation quickstart fails to validate due to non-compliant arquillian.xml > -------------------------------------------------------------------------------- > > Key: WFLY-5244 > URL: https://issues.jboss.org/browse/WFLY-5244 > Project: WildFly > Issue Type: Bug > Reporter: Rob Stryker > Assignee: Jason Greene > > bean-validation quickstart fails to validate in arquillian.xml. > The arquillian_1_0.xsd file includes the following: > {code} > <element name="container"> > <complexType> > <choice minOccurs="1" maxOccurs="unbounded"> > <element ref="tns:configuration" minOccurs="0" maxOccurs="1" /> >  > <element ref="tns:protocol" minOccurs="0" maxOccurs="unbounded" /> > </choice> > <attribute name="qualifier" type="string" use="required" /> > <attribute name="default" type="boolean" use="optional" default="false" /> > <attribute name="mode" use="optional" default="suite"> > <simpleType> > <restriction base="string"> > <enumeration value="suite" /> > <enumeration value="class" /> > <enumeration value="manual" /> > <enumeration value="custom" /> > </restriction> > </simpleType> > </attribute> > </complexType> > <unique name="unique-protocol-within-container"> > <annotation> > <documentation> > @type must be unique between all > protocols in a container. > </documentation> > </annotation> > <selector xpath="tns:protocol" /> > <field xpath="@type" /> > </unique> > </element> > {code} > The arquillian.xml included in the example includes the following: > {code} > <container qualifier="jboss" default="true"> >  >  > <property name="jbossHome">C:/tools/wildfly-9.0.0.Final</property> >  > </container> > {code} > Validation error is that "property" is not a valid sub-element, which is true based on the xsd file. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2015