October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-263) JASPI Support for Web Services

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-263?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-263: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > JASPI Support for Web Services > ------------------------------ > > Key: WFLY-263 > URL: https://issues.jboss.org/browse/WFLY-263 > Project: WildFly > Issue Type: Feature Request > Components: Security, Web Services > Reporter: Anil Saldhana > Assignee: Jim Ma > Fix For: 8.0.0.CR1 > > > Take care of the JASPI requirements for SOAP layer. -- 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-258) mod_cluster schema 1.2

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-258?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-258: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > mod_cluster schema 1.2 > ---------------------- > > Key: WFLY-258 > URL: https://issues.jboss.org/browse/WFLY-258 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > Changes to the schema > * simplified names and sync in line with scheme recommendations > * remove redundant <mod-cluster-config .. /> for good, everything should be element of the subsystem > * fix load factor enum: no pool metric supported > * make load-balancers configurable via socket-outbuound-group mechanism > * add missing load-balancer properties to <proxies/> -- 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-260) Error

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-260?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-260: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Error > ----- > > Key: WFLY-260 > URL: https://issues.jboss.org/browse/WFLY-260 > Project: WildFly > Issue Type: Feature Request > Components: Class Loading > Reporter: Pablo Ochoa > Assignee: David Lloyd > Fix For: 8.0.0.CR1 > > > Buenos Días, > Tengo problema con la version 7.1.1 de Jboss por defecto viene creado un Selector y yo intento crea uno nuevo para el manejo de mi classes me arroja el siguiente error > Preferred repository selector not installed because one has already exists. No problem, using existing selector... > Estado investigando de verdad no conseguido algo para poder solventar este problema el la ultima version de Jboss 6 no ocurre este mismo problema agradezco toda la colaboración que me puedan brindar > Te anexo el codigo que utilizo > import java.util.*; > import javax.naming.*; > import org.apache.log4j.Hierarchy; > import org.apache.log4j.Level; > import org.apache.log4j.spi.*; > public class Log4jContextJNDISelector > implements RepositorySelector > { > public Log4jContextJNDISelector(){ > defaultHierarchy = new Hierarchy(new RootLogger(Level.DEBUG)); > } > public LoggerRepository getLoggerRepository() > { > String loggingContextName = null; > try > { > Context ctx = new InitialContext(); > loggingContextName = (String)ctx.lookup("java:comp/env/log4j/logging-context"); > } > catch(NamingException ne) { } > if(loggingContextName == null) > return defaultHierarchy; > Hierarchy hierarchy = (Hierarchy)hierMap.get(loggingContextName); > if(hierarchy == null) > { > hierarchy = new Hierarchy(new RootLogger(Level.DEBUG)); > hierMap.put(loggingContextName, hierarchy); > } > return hierarchy; > } > Archivo web.xml esta configuración > <context-param> > <param-name>log4j-selector</param-name> > <param-value>ve.com.prueba.gdis.cia.config.logging.Log4jContextJNDISelector</param-value> > <description> Selector de repositorios basado en JNDI desde donde se > configurar el repositorio de logs para esta aplicación > </description> > </context-param> -- 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-283) EJB timers in cluster and failover support

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-283?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-283: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > EJB timers in cluster and failover support > ------------------------------------------ > > Key: WFLY-283 > URL: https://issues.jboss.org/browse/WFLY-283 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, EJB > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > Support for clustered EJB timer service providing failover. -- 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-277) TS: Integrate JUnitDiff

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-277?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-277: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > TS: Integrate JUnitDiff > ----------------------- > > Key: WFLY-277 > URL: https://issues.jboss.org/browse/WFLY-277 > Project: WildFly > Issue Type: Feature Request > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 8.0.0.CR1 > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > Running with > {code} > -DjunitDiff='<path1>:<path2>:<path3>' > {code} > would create a comparison to given testsuite result sets (JUnit .xml and txt files). -- 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-279) Add deployment-scanner for singleton deployments

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-279?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-279: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add deployment-scanner for singleton deployments > ------------------------------------------------ > > Key: WFLY-279 > URL: https://issues.jboss.org/browse/WFLY-279 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > To simplify the use of singleton deployments in standalone mode, it would be nice to have a mechanism analogous to the hasingleton-deploy directory in AS6 and earlier. To do this, we can enhance the existing deployment-scanner to accept an additional policy attribute. Something like: > <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1"> > <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="standard"/> > <deployment-scanner path="singleton-deployments" relative-to="jboss.server.base.dir" scan-interval="5000" policy="singleton"/> > </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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-276) TS: How to use -Djpda with clustered tests

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-276?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-276: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > TS: How to use -Djpda with clustered tests > ------------------------------------------ > > Key: WFLY-276 > URL: https://issues.jboss.org/browse/WFLY-276 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Documentation, Test Suite > Reporter: Radoslav Husar > Assignee: Ondrej Zizka > Priority: Minor > Fix For: 8.0.0.CR1 > > > The doc now says whats pasted below, but I am not sure if both servers are listening on 8787 because (that would fail the startup), if I have to connect to both or where do I configure that, etc. > {code} > Running JBoss AS instances with debugger > Adding -Djpda (May be changed to -Ddebug in the future) will make JBoss AS run with JPDA JVM arguments for debugging. > It will suspend and wait for the debugger to connect at port 8787. > JBoss AS is started by Arquillian, when the first test which requires given instance is run. There's (currently) no challenge text in the console, it will look like the first test is stuck. This is being solved in http://jira.codehaus.org/browse/SUREFIRE-781. > Depending on which test group(s) you run, multiple instances may be started. In that case, you need to attach the debugger multiple times. > {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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-273) Document how to configure firewall when using different JGroups stacks

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-273?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-273: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Document how to configure firewall when using different JGroups stacks > ---------------------------------------------------------------------- > > Key: WFLY-273 > URL: https://issues.jboss.org/browse/WFLY-273 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Documentation > Reporter: Radoslav Husar > Assignee: Paul Ferraro > Fix For: 8.0.0.CR1 > > > Document how to configure firewall for using different clustering stacks > https://docs.jboss.org/author/display/AS71/High+Availability+Guide > Needed by OpenShift team (especially TCP stacks). -- 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-307) Add ability to migrate timers between data stores

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-307?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-307: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add ability to migrate timers between data stores > ------------------------------------------------- > > Key: WFLY-307 > URL: https://issues.jboss.org/browse/WFLY-307 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > > It should be possible to move timers between data stores, so that timers can be migrated from the legacy file store. -- 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-301) Undertow management API

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-301?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-301: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Undertow management API > ----------------------- > > Key: WFLY-301 > URL: https://issues.jboss.org/browse/WFLY-301 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management, Web (Undertow) > Reporter: Heiko Braun > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Expose undertow subsystem management opertions -- 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