October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2218) Subsystem transformers against 7.2.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-2218?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-2218: ------------------------------ Description: We have not tested the majority of subsystem transformers against AS 7.2.0. I have attempted to document why we need subsystem transformation here, and also how to use the framework: https://docs.jboss.org/author/display/WFLY8/Domain+Mode+Subsystem+Transfo... This document is WIP, and I will be updating it a bit more over the next few days. https://gist.github.com/kabir/6825607 contains the difference of a running WildFly instance against AS 7.2.0 in domain mode (for subsystems you don't really need to bother about this one) https://gist.github.com/kabir/6825559 contains the difference of a running WildFly instance against AS 7.2.0 in standalone mode, here you can see what has changed in the subsystems. When creating a new subsystem transformers test against 7.2.0, you will need the resource definition for the ModelVersion your subsystem uses in 7.2.0. If this is not found, you need to add a test to your subsystem, which you can delete once you have the .dmr file containing the resource defintion. Here is what I did to generate the file for JMX {code} @Test public void deleteMeWhenDone() throws Exception { ModelTestControllerVersion controllerVersion = ModelTestControllerVersion.V7_2_0_FINAL; ModelVersion modelVersion = ModelVersion.create(1, 1, 0); //Whatever version of your subsystem 7.2.0.Final has KernelServicesBuilder builder = createKernelServicesBuilder(null); builder.createLegacyKernelServicesBuilder(null, controllerVersion, modelVersion) .addMavenResourceURL("org.jboss.as:jboss-as-jmx:" + controllerVersion.getMavenGavVersion()); KernelServices services = builder.build(); generateLegacySubsystemResourceRegistrationDmr(services, modelVersion); } {code} Now run the test and delete it. The legacy .dmr file should be in {{target/test-classes/org/jboss/as/subsystem/test/<your-subsystem-name>-<your-version>.dmr}}. Copy this .dmr file to {{subsystem-test/framework/src/main/resources/org/jboss/as/subsystem/test}}. You will likely also need to update org.jboss.as.subsystem.test.KnownVersions to include your latest subsystem version, once you start doing real testing. Bear in mind that if you need to add some transformation to 7.2.0 due to some new feature in WildFly 8, you will probably also need to add the same transformation to 7.1.x as well! was: We have not tested the majority of subsystem transformers against AS 7.2.0. I have attempted to document why we need subsystem transformation here, and also how to use the framework: https://docs.jboss.org/author/display/WFLY8/Domain+Mode+Subsystem+https:/.... This document is WIP, and I will be updating it a bit more over the next few days. https://gist.github.com/kabir/6825607 contains the difference of a running WildFly instance against AS 7.2.0 in domain mode (for subsystems you don't really need to bother about this one) https://gist.github.com/kabir/6825559 contains the difference of a running WildFly instance against AS 7.2.0 in standalone mode, here you can see what has changed in the subsystems. When creating a new subsystem transformers test against 7.2.0, you will need the resource definition for the ModelVersion your subsystem uses in 7.2.0. If this is not found, you need to add a test to your subsystem, which you can delete once you have the .dmr file containing the resource defintion. Here is what I did to generate the file for JMX {code} @Test public void deleteMeWhenDone() throws Exception { ModelTestControllerVersion controllerVersion = ModelTestControllerVersion.V7_2_0_FINAL; ModelVersion modelVersion = ModelVersion.create(1, 1, 0); //Whatever version of your subsystem 7.2.0.Final has KernelServicesBuilder builder = createKernelServicesBuilder(null); builder.createLegacyKernelServicesBuilder(null, controllerVersion, modelVersion) .addMavenResourceURL("org.jboss.as:jboss-as-jmx:" + controllerVersion.getMavenGavVersion()); KernelServices services = builder.build(); generateLegacySubsystemResourceRegistrationDmr(services, modelVersion); } {code} Now run the test and delete it. The legacy .dmr file should be in {{target/test-classes/org/jboss/as/subsystem/test/<your-subsystem-name>-<your-version>.dmr}}. Copy this .dmr file to {{subsystem-test/framework/src/main/resources/org/jboss/as/subsystem/test}}. You will likely also need to update org.jboss.as.subsystem.test.KnownVersions to include your latest subsystem version, once you start doing real testing. Bear in mind that if you need to add some transformation to 7.2.0 due to some new feature in WildFly 8, you will probably also need to add the same transformation to 7.1.x as well! > Subsystem transformers against 7.2.0 > ------------------------------------ > > Key: WFLY-2218 > URL: https://issues.jboss.org/browse/WFLY-2218 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kabir Khan > Assignee: Brian Stansberry > > We have not tested the majority of subsystem transformers against AS 7.2.0. I have attempted to document why we need subsystem transformation here, and also how to use the framework: > https://docs.jboss.org/author/display/WFLY8/Domain+Mode+Subsystem+Transfo... > This document is WIP, and I will be updating it a bit more over the next few days. > https://gist.github.com/kabir/6825607 contains the difference of a running WildFly instance against AS 7.2.0 in domain mode (for subsystems you don't really need to bother about this one) > https://gist.github.com/kabir/6825559 contains the difference of a running WildFly instance against AS 7.2.0 in standalone mode, here you can see what has changed in the subsystems. > When creating a new subsystem transformers test against 7.2.0, you will need the resource definition for the ModelVersion your subsystem uses in 7.2.0. If this is not found, you need to add a test to your subsystem, which you can delete once you have the .dmr file containing the resource defintion. Here is what I did to generate the file for JMX > {code} > @Test > public void deleteMeWhenDone() throws Exception { > ModelTestControllerVersion controllerVersion = ModelTestControllerVersion.V7_2_0_FINAL; > ModelVersion modelVersion = ModelVersion.create(1, 1, 0); //Whatever version of your subsystem 7.2.0.Final has > KernelServicesBuilder builder = createKernelServicesBuilder(null); > builder.createLegacyKernelServicesBuilder(null, controllerVersion, modelVersion) > .addMavenResourceURL("org.jboss.as:jboss-as-jmx:" + controllerVersion.getMavenGavVersion()); > KernelServices services = builder.build(); > generateLegacySubsystemResourceRegistrationDmr(services, modelVersion); > } > {code} > Now run the test and delete it. The legacy .dmr file should be in {{target/test-classes/org/jboss/as/subsystem/test/<your-subsystem-name>-<your-version>.dmr}}. Copy this .dmr file to {{subsystem-test/framework/src/main/resources/org/jboss/as/subsystem/test}}. > You will likely also need to update org.jboss.as.subsystem.test.KnownVersions to include your latest subsystem version, once you start doing real testing. > Bear in mind that if you need to add some transformation to 7.2.0 due to some new feature in WildFly 8, you will probably also need to add the same transformation to 7.1.x as well! -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1697) Fix JPA SerializableValidatorFactory memory leak

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1697?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1697: ----------------------------------------------- Tomaz Cerar <tcerar(a)redhat.com> made a comment on [bug 1003600|https://bugzilla.redhat.com/show_bug.cgi?id=1003600] I can reproduce this, it is related to buggy h2 we use for ExampleDB datasource. I will send PR to address this same way we did in upstream > Fix JPA SerializableValidatorFactory memory leak > ------------------------------------------------ > > Key: WFLY-1697 > URL: https://issues.jboss.org/browse/WFLY-1697 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 8.0.0.Alpha3 > Reporter: Scott Marlow > Assignee: Scott Marlow > > See http://lists.jboss.org/pipermail/wildfly-dev/2013-July/000466.html for details on recreating the SerializableValidatorFactory leak and Hibernate service loader references to Integreation class/properties. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SASL-43) Release JBoss SASL 1.0.4.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-43: ------------------------------------ Summary: Release JBoss SASL 1.0.4.CR1 Key: SASL-43 URL: https://issues.jboss.org/browse/SASL-43 Project: JBoss SASL Provider Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SASL-42) Add option to relax protocol check within mechanisms.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SASL-42?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved SASL-42. ---------------------------------- Resolution: Done > Add option to relax protocol check within mechanisms. > ----------------------------------------------------- > > Key: SASL-42 > URL: https://issues.jboss.org/browse/SASL-42 > Project: JBoss SASL Provider > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.4.CR1 > > > The Digest MD5 mechanism contains a check that the URI received from the remote client matches the expected value, unfortunately older clients use a hard coded protocol or 'remote' - newer clients and servers use 'remoting'. > This issue is to add a configuration option so that server side this checking can be relaxed, most appropriate would be to supply a list of accepted alternative protocols. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1489) Incorrect heap description in VM metrics view

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1489?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1489: ----------------------------------------------- Heiko Braun <hbraun(a)redhat.com> changed the Status of [bug 880648|https://bugzilla.redhat.com/show_bug.cgi?id=880648] from NEW to MODIFIED > Incorrect heap description in VM metrics view > --------------------------------------------- > > Key: WFLY-1489 > URL: https://issues.jboss.org/browse/WFLY-1489 > Project: WildFly > Issue Type: Bug > Components: Web Console > Reporter: Heiko Braun > Assignee: Chao Wang > -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2239) Messaging subsystem transformers for 7.2.0

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2239?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-2239: ---------------------------------- Jeff, I noticed that the messaging subsystem transformers tests currently lack the following call: {code} checkSubsystemModelTransformation(mainServices, modelVersion); {code} That is needed to make sure that the model built up by the transformed operations is the same as the model created by the resource transformation. Please see the usage in the other transformers tests. > Messaging subsystem transformers for 7.2.0 > ------------------------------------------ > > Key: WFLY-2239 > URL: https://issues.jboss.org/browse/WFLY-2239 > Project: WildFly > Issue Type: Sub-task > Components: JMS > Reporter: Kabir Khan > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2251) ; jsessionid=... in URL not supported

by Frank Cornelis (JIRA)

Frank Cornelis created WFLY-2251: ------------------------------------ Summary: ;jsessionid=... in URL not supported Key: WFLY-2251 URL: https://issues.jboss.org/browse/WFLY-2251 Project: WildFly Issue Type: Bug Components: Web (Undertow) Affects Versions: 8.0.0.Beta1 Reporter: Frank Cornelis Assignee: Stuart Douglas Priority: Blocker When configuring a servlet within your Java EE application, you can reach it via: https://localhost/your_app_context/your_servlet_mapping but not via: https://localhost/your_app_context/your_servlet_mapping;jsessionid=whatever You get a "Not Found" error message instead. This used to work under JBoss EAP 6.1. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2250) Upgrade JGroups to 3.4.0.Final

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-2250: ---------------------------------- Summary: Upgrade JGroups to 3.4.0.Final Key: WFLY-2250 URL: https://issues.jboss.org/browse/WFLY-2250 Project: WildFly Issue Type: Component Upgrade Components: Clustering Affects Versions: 8.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.CR1 -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2176) JSF should be able to access the CDI-enabled ValidatorFactory

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-2176?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-2176: ----------------------------- Fix Version/s: 8.0.0.CR1 > JSF should be able to access the CDI-enabled ValidatorFactory > ------------------------------------------------------------- > > Key: WFLY-2176 > URL: https://issues.jboss.org/browse/WFLY-2176 > Project: WildFly > Issue Type: Feature Request > Components: JSF > Affects Versions: 8.0.0.Alpha4 > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 8.0.0.CR1 > > > Currently, for every deployment that uses JSF, the JSF subsystem adds the org.hibernate.validator module to the deployment. A ValidatorFactory is then obtained via the standard Bean Validation bootstrap strategy. However, a ValidatorFactory obtained this way isn't CDI-enabled. JSF needs to use the EE LazyValidatorFactory instead. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-364) a "failure-causes-rollback="false"" attribute for the filesystem scanner

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-364?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned WFLY-364: ------------------------------------- Assignee: Brian Stansberry > a "failure-causes-rollback="false"" attribute for the filesystem scanner > ------------------------------------------------------------------------ > > Key: WFLY-364 > URL: https://issues.jboss.org/browse/WFLY-364 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Max Rydahl Andersen > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > > JBIDE-11509, AS7-783 and TORQUE-576 all talk about the problem of all deployments found at startup is deployed in one operation and if one deployment fails all is rolled back resulting in some rather bad usability issues - especially at development time, but even also at production time for those using file deployments. > Suggestion on irc was that there could be an option on the file scanner (possibly false by default?) to say that failure causes rollback. > Individual deployments could then still fail, but at least not everything would be rolledback and it would still allow proper interdependent deployments to work. -- 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

12 years, 7 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

jboss-jira October 2013