February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2991) Forward port core 1.6 xml schema

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2991?page=com.atlassian.jira.plugin.... ] Brian Stansberry reopened WFLY-2991: ------------------------------------ > Forward port core 1.6 xml schema > -------------------------------- > > Key: WFLY-2991 > URL: https://issues.jboss.org/browse/WFLY-2991 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 9.0.0.CR1 > > > The urn:jboss:domain:1.6 xml schema used in EAP 6.3 needs to be forward ported. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2991) [Duplicate] Forward port core 1.6 xml schema

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2991?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-2991: ----------------------------------- Summary: [Duplicate] Forward port core 1.6 xml schema (was: Forward port core 1.6 xml schema) > [Duplicate] Forward port core 1.6 xml schema > -------------------------------------------- > > Key: WFLY-2991 > URL: https://issues.jboss.org/browse/WFLY-2991 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 9.0.0.CR1 > > > The urn:jboss:domain:1.6 xml schema used in EAP 6.3 needs to be forward ported. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2991) [Duplicate] Forward port core 1.6 xml schema

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2991?page=com.atlassian.jira.plugin.... ] Brian Stansberry closed WFLY-2991. ---------------------------------- Resolution: Duplicate Issue > [Duplicate] Forward port core 1.6 xml schema > -------------------------------------------- > > Key: WFLY-2991 > URL: https://issues.jboss.org/browse/WFLY-2991 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 9.0.0.CR1 > > > The urn:jboss:domain:1.6 xml schema used in EAP 6.3 needs to be forward ported. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2956) Port version 1.6 of the management schema upstream.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2956?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-2956: ---------------------------------------- FYI: to solve the linear progression issue I evaluated simply dropping 1.6 and making it a 2.1. It won't work due to 1 attribute: "http-upgrade-enabled" on the http-interface elements. :( I'm tempted to switch EAP 6 HTTP management to undertow. Just kidding; I have many other higher value tasks. > Port version 1.6 of the management schema upstream. > --------------------------------------------------- > > Key: WFLY-2956 > URL: https://issues.jboss.org/browse/WFLY-2956 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 9.0.0.CR1 > > > EAP will be introducing version 1.6 of the management schema, this needs porting upstream. > At the same point the coding convention we have adopted has been based around a linear progression of the configuration schemas, when version 1.5 was ported this still worked as 1.5 contained a subset of the changes that went into 2.0. > 1.6 is going to be a special case as it will build on 1.5 so is already a subset of 2.0 but will also only contain a subset of changes that go into 3.0 - the risk however is our switch statements are built around dropping into a default block that is hit for all schema versions not explicitly listed. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-2881: --------------------------------------- Just saw, that problem reappeared once at http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=11225&buildTyp.... > org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout > -------------------------------------------------------------------------------------- > > Key: WFLY-2881 > URL: https://issues.jboss.org/browse/WFLY-2881 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Frank Langelage > Assignee: Tomaz Cerar > Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml > > > Running build with smoke tests on current github sources I get failure in this test case. > HOUR_OF_DAY is not 0 as expected but 1. > I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName. > See attached files for more. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2991) Forward port core 1.6 xml schema

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-2991?page=com.atlassian.jira.plugin.... ] Brian Stansberry closed WFLY-2991. ---------------------------------- Resolution: Duplicate Issue > Forward port core 1.6 xml schema > -------------------------------- > > Key: WFLY-2991 > URL: https://issues.jboss.org/browse/WFLY-2991 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 9.0.0.CR1 > > > The urn:jboss:domain:1.6 xml schema used in EAP 6.3 needs to be forward ported. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2991) Forward port core 1.6 xml schema

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2991: -------------------------------------- Summary: Forward port core 1.6 xml schema Key: WFLY-2991 URL: https://issues.jboss.org/browse/WFLY-2991 Project: WildFly Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 9.0.0.CR1 The urn:jboss:domain:1.6 xml schema used in EAP 6.3 needs to be forward ported. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2956) Port version 1.6 of the management schema upstream.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2956?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2956: ----------------------------------- Parent: WFLY-2990 Issue Type: Sub-task (was: Task) > Port version 1.6 of the management schema upstream. > --------------------------------------------------- > > Key: WFLY-2956 > URL: https://issues.jboss.org/browse/WFLY-2956 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 9.0.0.CR1 > > > EAP will be introducing version 1.6 of the management schema, this needs porting upstream. > At the same point the coding convention we have adopted has been based around a linear progression of the configuration schemas, when version 1.5 was ported this still worked as 1.5 contained a subset of the changes that went into 2.0. > 1.6 is going to be a special case as it will build on 1.5 so is already a subset of 2.0 but will also only contain a subset of changes that go into 3.0 - the risk however is our switch statements are built around dropping into a default block that is hit for all schema versions not explicitly listed. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2990) Forward port EAP 6.2/6.3 xml schemas

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2990: -------------------------------------- Summary: Forward port EAP 6.2/6.3 xml schemas Key: WFLY-2990 URL: https://issues.jboss.org/browse/WFLY-2990 Project: WildFly Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Priority: Blocker Fix For: 9.0.0.CR1 EAP 6.3 will be introducing new versions of domain configuration xml schemas. These will basically be schemas containing some subset of the diff between the AS 7.2 schemas and the WF 9 schemas. These schemas and parsing thereof need to be forward ported into WF. Hopefully the schemas used for EAP 6.2 are already forward ported and this is mostly about 6.3. This is a parent task to capture the overall requirement and the task of analyzing what areas need the forward port. Subtasks or linked issues should be used for the specific porting tasks (e.g. one per subsystem) -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2868) Expose underlying cause during InitialContextFactory instantiation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2868?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2868: ----------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 1061609|https://bugzilla.redhat.com/show_bug.cgi?id=1061609] from ON_QA to VERIFIED > Expose underlying cause during InitialContextFactory instantiation > ------------------------------------------------------------------ > > Key: WFLY-2868 > URL: https://issues.jboss.org/browse/WFLY-2868 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > Priority: Critical > Fix For: 8.0.0.Final > > > Instantiation an InitialContext might fail with just the follow cause: > javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.externalContextBindingTest.jar:main" from Service Module Loader > The underlying cause is no longer available. > https://bugzilla.redhat.com/show_bug.cgi?id=1061609 -- 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, 5 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 February 2014