October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-444) Remove ServerEnvironment.getModulesDir()

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-444?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-444: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Remove ServerEnvironment.getModulesDir() > ---------------------------------------- > > Key: WFLY-444 > URL: https://issues.jboss.org/browse/WFLY-444 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1 > > > This method was deprecated in 7.1.0 and the OSGi subsystem is removing the only known use of it in 7.1.2. Remove the method in 7.2. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-450) Add 7.2.0 configuration tests to ParseAndMarshalModelsTestCase

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-450?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-450: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add 7.2.0 configuration tests to ParseAndMarshalModelsTestCase > -------------------------------------------------------------- > > Key: WFLY-450 > URL: https://issues.jboss.org/browse/WFLY-450 > Project: WildFly > Issue Type: Task > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Priority: Critical > Fix For: 8.0.0.CR1 > > > Add 7.2.0 configuration tests to {{org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase}} test case. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-468) Report master SHA1 before pull request gets rebased

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-468?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-468: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Report master SHA1 before pull request gets rebased > --------------------------------------------------- > > Key: WFLY-468 > URL: https://issues.jboss.org/browse/WFLY-468 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Thomas Diesler > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > For a successful merge like [this|http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pul...] I see > {code} > + git init > Initialized empty Git repository in /home/jenkins/jenkins-work/workspace/as7-param-pull/.git/ > + git config user.email jenkins(a)example.com > + git config user.name 'Mr. Jenkins' > + git remote add origin git://github.com/jbossas/jboss-as.git > + git fetch origin master:refs/remotes/origin/master > From git://github.com/jbossas/jboss-as > * [new branch] master -> origin/master > From git://github.com/jbossas/jboss-as > ... > * [new tag] 7.1.2.Final -> 7.1.2.Final > + git fetch origin refs/pull/2593/head > From git://github.com/jbossas/jboss-as > * branch refs/pull/2593/head -> FETCH_HEAD > + git checkout FETCH_HEAD > ... > Checking out files: 100% (9519/9519), done. > Note: checking out 'FETCH_HEAD'. > You are in 'detached HEAD' state. You can look around, make experimental > changes and commit them, and you can discard any commits you make in this > state without impacting any branches by performing another checkout. > If you want to create a new branch to retain commits you create, you may > do so (now or later) by using -b with the checkout command again. Example: > git checkout -b new_branch_name > HEAD is now at 3a64ae5... [AS7-5052] Allow WAR deployments as OSGi bundles > + git rebase origin/master > First, rewinding head to replay your work on top of it... > Applying: [AS7-4918] Registered module using OSGi capability not visible as a bundle > Applying: [AS7-5049] Allow bundles to get resolved/activated during deployment unit processing > Applying: [AS7-5104] Remove no-start behaviour for test bundle deployments > Applying: [AS7-5093] Allow JDBC driver deployments as OSGi bundles > Applying: [AS7-5052] Allow WAR deployments as OSGi bundles > {code} > This tells me that the rebase was ok, but not onto what master revision it happened. Hence I cannot reproduce this run locally. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-465) Attribute check-for-live-server must set on live server to faillback

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-465?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-465: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Attribute check-for-live-server must set on live server to faillback > -------------------------------------------------------------------- > > Key: WFLY-465 > URL: https://issues.jboss.org/browse/WFLY-465 > Project: WildFly > Issue Type: Task > Components: JMS > Reporter: Miroslav Novak > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > Attachments: standalone-full-ha-backup.xml, standalone-full-ha-live.xml > > > When there is live/backup pair with replicated journal then it should be sufficient to set attribute "check-for-live-server" in messaging subsystem only on backup to force backup server to shutdown when live server comes alive again. Problem is this won't happen. > Only when attribute "check-for-live-server" is set on live server then failback is successful (backup shutdown itself) > It's not well documented where "check-for-live-server" should be set in HornetQ project documentation: > http://docs.jboss.org/hornetq/2.3.0.CR1/docs/user-manual/html_single/inde... > This issue was hit with EAP 6.1.0.DR2 (HQ 2.3.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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-463) Add utility for creating and destorying modules in tests

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-463?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-463: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add utility for creating and destorying modules in tests > -------------------------------------------------------- > > Key: WFLY-463 > URL: https://issues.jboss.org/browse/WFLY-463 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Stuart Douglas > Assignee: Ondrej Zizka > Fix For: 8.0.0.CR1 > > > Lots of tests create and destroy a static module to test functionaility involving static modules. If possible all this code should be moved into some kind of static module builder utility. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-462) Eliminate the threads subsystem

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-462?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-462: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Eliminate the threads subsystem > ------------------------------- > > Key: WFLY-462 > URL: https://issues.jboss.org/browse/WFLY-462 > Project: WildFly > Issue Type: Task > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > The threads subsystem should be eliminated, and instead the individual consuming subsystems should utilize common code from the jboss-as-threads module to define and manage thread pools within their own configuration models. > Subtasks for affected subsystems. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-459) correct JPA dependency injection (stop injecting javassist)

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-459?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-459: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > correct JPA dependency injection (stop injecting javassist) > ----------------------------------------------------------- > > Key: WFLY-459 > URL: https://issues.jboss.org/browse/WFLY-459 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.CR1 > > > Rather than export the javassist dependency, see if we can change javassist to generate proxies for the application classes which aren't on the hibernate module class path. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-469) Parent Issue for Java EE 7 Support

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-469?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-469: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Parent Issue for Java EE 7 Support > ---------------------------------- > > Key: WFLY-469 > URL: https://issues.jboss.org/browse/WFLY-469 > Project: WildFly > Issue Type: Task > Components: EE > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Critical > Fix For: 8.0.0.CR1 > > > This is the parent issue for tracking tasks related to completing our Java EE 7 support. Do not close the issue unless Jason has given his blessing. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-485) Review SecurityContext associations

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-485?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-485: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Review SecurityContext associations > ------------------------------------ > > Key: WFLY-485 > URL: https://issues.jboss.org/browse/WFLY-485 > Project: WildFly > Issue Type: Sub-task > Components: Security > Reporter: Darran Lofthouse > Assignee: David Lloyd > Labels: Security_SPI > Fix For: 8.0.0.CR1 > > > We should re-review the approach we take for security context association within AS7 containers. > Back at the time of AS 3 it fairly reliable to assume a 1:1 mapping of thread and client with the incoming connection being allocated it's own thread, this is no longer automatically the case and different containers can use different threading models e.g. using Executors to handle asynchronous requests. > The problem with using a ThreadLocal approach is that every time a container diverges from the 1:1 mapping of thread and client that container needs to work around the issue of an invalid SecurityContext association. > One possibility is to pass responsibility for managing the context to the container although this then introduces the question of how it is passed from container to container. This issue needs to consider this further. > Also need to review further how the security context can be created at all entry points to the server and how it can be manually switched now that we use SASL on entry for remote calls we do now have the opportunity for equivalent behaviour at the entry point for both web and ejb type calls - in the past we only had this opportunity for web based calls and would only create a security context on entering the interceptors for the EJB calls. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-479) Ability to rollback AS version updates

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-479?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-479: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Ability to rollback AS version updates > -------------------------------------- > > Key: WFLY-479 > URL: https://issues.jboss.org/browse/WFLY-479 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1 > > > This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010: > >> A fixpack installer that handles version rollbacks would be fantastic. > >> Of course it needs to remain flexible to work with JBoss installs that > >> have been manually modified. > Note that this may be out of scope for community AS 7; e.g. it may be a JON function. However, the AS 7 design of things like how we lay down content on the filesystem should take this use case into account. -- 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, 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

jboss-jira October 2013