November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on WFLY-2471: ------------------------------------ As I recall (as the person who made the change), the change to the 1.4 schema was to fix a bug. As I recall, previously, the schema allowed an <invalidation-cache/> to contain a <state-transfer/> element. However, this is not allowed by either the parser or the model. So, really, assuming my recollection is correct, this fix should be backported to EAP 6. > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2471: ---------------------------------------- >From what I have seen so far, yes I believe this change should just not have been made to the 1.4 schema - the addition of the 1.5 schema which was subsequently renamed to 2.0 should have been sufficient. > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2471) jboss-as-infinispan_1_4.xsd differs between EAP and WildFly

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2471?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-2471: -------------------------------------- The change is about cross-site replication which is not supported in EAP. So in other words this issue is that the schema version should have been bumped, right? > jboss-as-infinispan_1_4.xsd differs between EAP and WildFly > ----------------------------------------------------------- > > Key: WFLY-2471 > URL: https://issues.jboss.org/browse/WFLY-2471 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Darran Lofthouse > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-infinispan_1_4.xsd' is not in sync between EAP and WildFly. > For a given namespace there is supposed to be only one definition and that definition is frozen as soon as it reaches a Final release. > The following commit affected version 1.4 of the schema in WildFly but did not make it to the EAP version: - > https://github.com/wildfly/wildfly/commit/a9ed468bba498d55c2aa8008100f0f9... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2475) Bad marshalling of identity-trust's module in security subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2475?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2475: ----------------------------- Summary: Bad marshalling of identity-trust's module in security subsystem (was: Bad marshalling of identity-trust's module) > Bad marshalling of identity-trust's module in security subsystem > ---------------------------------------------------------------- > > Key: WFLY-2475 > URL: https://issues.jboss.org/browse/WFLY-2475 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > > {code} > <identity-trust> > <trust-module name="acl" code="AclThingy" flag="required" module="test"> > <module-option name="d" value="r"/> > </trust-module> > </identity-trust> > {code} > becomes > {code} > <identity-trust> > <login-module name="acl" code="AclThingy" flag="required" module="test"> > <module-option name="d" value="r"/> > </login-module> > </identity-trust> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2474) Security subsystem does not handle acl's module properly

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2474?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2474: ----------------------------- Component/s: Domain Management > Security subsystem does not handle acl's module properly > -------------------------------------------------------- > > Key: WFLY-2474 > URL: https://issues.jboss.org/browse/WFLY-2474 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.CR1 > > > The parsed add is done for /subsystem=security/security-domain=other/acl=classic/acl-module=acl > However in the acl resource this is called login-module=acl. > WHen marshalling > {code} > <acl> > <acl-module name="acl" code="AclThingy" flag="required" module="test"> > <module-option name="d" value="r"/> > </acl-module> > </acl> > {code} > becomes > {code} > <acl> > <login-module name="acl" code="AclThingy" flag="required" module="test"> > <module-option name="d" value="r"/> > </login-module> > </acl> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2475) Bad marshalling of identity-trust's module

by Kabir Khan (JIRA)

Kabir Khan created WFLY-2475: -------------------------------- Summary: Bad marshalling of identity-trust's module Key: WFLY-2475 URL: https://issues.jboss.org/browse/WFLY-2475 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 8.0.0.Beta1 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.CR1 {code} <identity-trust> <trust-module name="acl" code="AclThingy" flag="required" module="test"> <module-option name="d" value="r"/> </trust-module> </identity-trust> {code} becomes {code} <identity-trust> <login-module name="acl" code="AclThingy" flag="required" module="test"> <module-option name="d" value="r"/> </login-module> </identity-trust> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1716) NoClassDefFoundError: org/jboss/el/cache/FactoryFinderCache deploying ear with war inside

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-1716?page=com.atlassian.jira.plugin.... ] Stuart Douglas reopened WFLY-1716: ---------------------------------- > NoClassDefFoundError: org/jboss/el/cache/FactoryFinderCache deploying ear with war inside > ----------------------------------------------------------------------------------------- > > Key: WFLY-1716 > URL: https://issues.jboss.org/browse/WFLY-1716 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EE > Affects Versions: 8.0.0.Alpha3 > Environment: Win 7, JEE 6, JDK 7 > Reporter: Oliver Pfau > Assignee: Stuart Douglas > Labels: Deploy, classnotfound, war > > I tried to deploy my ear which works in JBoss 7 in wildfly and got the following error on deploy: > 09:59:55,060 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.subunit."my.ear"."mywar.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."my.ear"."mywar.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment "mywar.war" of deployment "my.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha3.jar:8.0.0.Alpha3] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1944) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1877) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > Caused by: java.lang.NoClassDefFoundError: org/jboss/el/cache/FactoryFinderCache > at org.wildfly.extension.undertow.deployment.ELExpressionFactoryProcessor.deploy(ELExpressionFactoryProcessor.java:78) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha3.jar:8.0.0.Alpha3] > ... 5 more > 09:59:55,100 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "my.ear")]) - failure description: { > "JBAS014671: Failed services" => {"jboss.deployment.subunit.\"my.ear\".\"mywar.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"my.ear\".\"mywar.war\".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of subdeployment \"mywar.war\" of deployment \"my.ear\" > Caused by: java.lang.NoClassDefFoundError: org/jboss/el/cache/FactoryFinderCache"}, > "JBAS014771: Services with missing/unavailable dependencies" => [ > "jboss.naming.context.java.comp.my-service-ejb-x-SNAPSHOT.MyServiceName.ValidatorFactory is missing [jboss.naming.context.java.comp.my-service-ejb-x-SNAPSHOT.MyServiceName]", > "jboss.naming.context.java.comp.my-service-ejb-x-SNAPSHOT.MyServiceName.InstanceName is missing [jboss.naming.context.java.comp.my-service-ejb-x-SNAPSHOT.MyServiceName]", > "jboss.naming.context.java.comp.my-service-ejb-x-SNAPSHOT.MyServiceName.Validator is missing [jboss.naming.context.java.comp.my-service-ejb-x-SNAPSHOT.MyServiceName]", > > <all other services> > ] > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2474) Security subsystem does not handle acl's module properly

by Kabir Khan (JIRA)

Kabir Khan created WFLY-2474: -------------------------------- Summary: Security subsystem does not handle acl's module properly Key: WFLY-2474 URL: https://issues.jboss.org/browse/WFLY-2474 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 8.0.0.Beta1 Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 8.0.0.CR1 The parsed add is done for /subsystem=security/security-domain=other/acl=classic/acl-module=acl However in the acl resource this is called login-module=acl. WHen marshalling {code} <acl> <acl-module name="acl" code="AclThingy" flag="required" module="test"> <module-option name="d" value="r"/> </acl-module> </acl> {code} becomes {code} <acl> <login-module name="acl" code="AclThingy" flag="required" module="test"> <module-option name="d" value="r"/> </login-module> </acl> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2472) jboss-as-xts_1_0.xsd in WildFly modified since EAP release

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2472?page=com.atlassian.jira.plugin.... ] Darran Lofthouse commented on WFLY-2472: ---------------------------------------- Hello Tom, Yes it is something along those lines - overall the changes need to be reviewed in a but more detail to get to the bottom of the exact change needed. In some cases we have found that actually parsers were supporting features not documented in the schema, in that case we can sometimes get away with just updating the schema in all locations - our main concern is backwards compatibility so if the parser was supporting something then updating the schema is just really updating docs to reflect it. On the other hand once a schema makes it into a Final or GA release it needs to be considered frozen for backwards compatibility purposes and only compatible changes should be made at that point e.g. correcting documentation. At this point any schema changes in WildFly should actually result in a schema in the 2.x range (All should be no more than 2.0 at this point as we have not had the first Final release) - this then leaves EAP free to continue to add additional 1.x schemas without conflict. Of course if we know a change being made to a subsystem is going to be made in exactly the same way in EAP we can sometimes add a 1.x schema to WildFly and add the same to EAP. Sorry for not being precise with a response, unfortunately this area is a little complex with some decisions needed on a case by case basis with the main rule being compatibility once it reaches a GA or Final release. In this case it is about the additional elements added in WildFly - a configuration based on that schema that is working in WildFly would fail on EAP despite the schema with the same namespace being supported on EAP. Maybe also get a thread started in wildfly-dev(a)lists.jboss.org - I can be contacted in IRC but we may also want some input from Brian as well. > jboss-as-xts_1_0.xsd in WildFly modified since EAP release > ---------------------------------------------------------- > > Key: WFLY-2472 > URL: https://issues.jboss.org/browse/WFLY-2472 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Darran Lofthouse > Assignee: Tom Jenkinson > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-xts_1_0.xsd' has been modified in WildFly making it incompatible with the version in EAP - additional elements have been added. > The following commit is where additional elements were added: - > https://github.com/wildfly/wildfly/commit/09dda67ed71b9f5cf4c9f865f08bbe3... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2472) jboss-as-xts_1_0.xsd in WildFly modified since EAP release

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-2472?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-2472: ------------------------------------- Hi Darren, Please can you provide some more context, I have cc'd [~gytis] who made the commit but I am not too sure what the problem is from the subject. It sounds from the subject that Gytis has updated jboss-as-xts_1_0.xsd rather than creating a new jboss-as-xts_1_1.xsd and you would like him to revert the jboss-as-xts_1_0.xsd changes and create the new jboss-as-xts_1_1.xsd? Please can you confirm? Tom > jboss-as-xts_1_0.xsd in WildFly modified since EAP release > ---------------------------------------------------------- > > Key: WFLY-2472 > URL: https://issues.jboss.org/browse/WFLY-2472 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Darran Lofthouse > Assignee: Tom Jenkinson > Fix For: 8.0.0.CR1 > > > The schema 'jboss-as-xts_1_0.xsd' has been modified in WildFly making it incompatible with the version in EAP - additional elements have been added. > The following commit is where additional elements were added: - > https://github.com/wildfly/wildfly/commit/09dda67ed71b9f5cf4c9f865f08bbe3... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 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 November 2013