April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-454) Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-454?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated WFLY-454: ----------------------------- Component/s: Web (Undertow) (was: Web (JBoss Web)) > Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together > -------------------------------------------------------------------------------------------- > > Key: WFLY-454 > URL: https://issues.jboss.org/browse/WFLY-454 > Project: WildFly > Issue Type: Task > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > There are many workarounds in undertow subsystem code just to make it behave exactly as jbossweb did but that is wrong in many cases. > This issue is here just to track such occurrences and resolutions for this issue should eventual removal of this hacks when web subsystem is removed from AS8 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-301) Undertow management API

by Brian Stansberry (JIRA)

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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-454) Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-454?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated WFLY-454: ----------------------------- Component/s: Web (JBoss Web) > Task for tracking all workarounds / hacks needed to have undertow & jbossweb living together > -------------------------------------------------------------------------------------------- > > Key: WFLY-454 > URL: https://issues.jboss.org/browse/WFLY-454 > Project: WildFly > Issue Type: Task > Components: Web (JBoss Web), Web (Undertow) > Affects Versions: 8.0.0.Alpha1 > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > There are many workarounds in undertow subsystem code just to make it behave exactly as jbossweb did but that is wrong in many cases. > This issue is here just to track such occurrences and resolutions for this issue should eventual removal of this hacks when web subsystem is removed from AS8 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1159) Allow configure SSL connection in stanalone.xml for email servers

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1159?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-1159: --------------------------------- Assignee: Tomaz Cerar (was: Darran Lofthouse) > Allow configure SSL connection in stanalone.xml for email servers > ----------------------------------------------------------------- > > Key: WFLY-1159 > URL: https://issues.jboss.org/browse/WFLY-1159 > Project: WildFly > Issue Type: Feature Request > Components: Mail > Reporter: Alexey Volkov > Assignee: Tomaz Cerar > Priority: Optional > > Allow to configure SSL connection to email servers into stanalone.xml > Here is the discussion into community https://community.jboss.org/thread/205364 -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-249) Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-249?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-249: ---------------------------------- Assignee: (was: Brian Stansberry) > Look into whether READ_ONLY but not RUNTIME_ONLY domain server ops should be visible to users > --------------------------------------------------------------------------------------------- > > Key: WFLY-249 > URL: https://issues.jboss.org/browse/WFLY-249 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > Ops registered on a domain server without the RUNTIME_ONLY flag are hidden from users (e.g. in read-operation-names results etc) in order to not delude users into thinking they can do something like :write-attribute directly on a server (instead of modifying host or domain config elements.) > But shouldn't a READ_ONLY flag be sufficient as well? An op that only reads config should be valid. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-250) Expose webservices endpoint metrics in console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-250?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-250: ---------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Expose webservices endpoint metrics in console > ---------------------------------------------- > > Key: WFLY-250 > URL: https://issues.jboss.org/browse/WFLY-250 > Project: WildFly > Issue Type: Feature Request > Components: Web Console, Web Services > Reporter: Alessio Soldano > Assignee: Heiko Braun > Fix For: 8.0.0.Alpha1 > > > The Status->Subsystems->Webservices section of the Runtime area of the console contains basic info regarding deployed ws endpoints. It does not currently use all the available information for each of them in the model (e.g. [1]), in particular the metrics are missing and should really be added to the console (average-processing-time, fault-count, max-processing-time, min-processing-time, request-count, response-count, total-processing-time) > [1] /deployment=foo.war/subsystem=webservices/endpoint=foo-ep -- 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

13 years, 2 months

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-263?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-263: ---------------------------------- Assignee: Alessio Soldano (was: Brian Stansberry) > 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: Alessio Soldano > Fix For: 8.0.0.Alpha1 > > > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-260) Error

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-260?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-260: ---------------------------------- Assignee: David Lloyd (was: Brian Stansberry) > 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.Alpha1 > > > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-267) Support updated JCA management API

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-267?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-267: ---------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Support updated JCA management API > ----------------------------------- > > Key: WFLY-267 > URL: https://issues.jboss.org/browse/WFLY-267 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-676) Windows PowerShell scripts in bin

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-676?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar reassigned WFLY-676: -------------------------------- Assignee: Tomaz Cerar (was: Jason Greene) > Windows PowerShell scripts in bin > --------------------------------- > > Key: WFLY-676 > URL: https://issues.jboss.org/browse/WFLY-676 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: Awaiting Volunteers > > > Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language. -- 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

13 years, 2 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 April 2013