April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1085) No audit feature for security-realm

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1085?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1085: ----------------------------------- Assignee: Darran Lofthouse (was: Brian Stansberry) > No audit feature for security-realm > ----------------------------------- > > Key: WFLY-1085 > URL: https://issues.jboss.org/browse/WFLY-1085 > Project: WildFly > Issue Type: Feature Request > Components: Logging > Environment: EAP 6.0.x > Reporter: Hisanobu Okuda > Assignee: Darran Lofthouse > > There is no auditing feature for security-realm. Need the feature like audit provider for security-domain. -- 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-1071) Fail the deployment if CMP beans are present but the CMP subsystem is not installed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1071?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-1071. ------------------------------------ Fix Version/s: 8.0.0.Alpha1 Resolution: Won't Fix WildFly 8 will not support CMP. > Fail the deployment if CMP beans are present but the CMP subsystem is not installed > ----------------------------------------------------------------------------------- > > Key: WFLY-1071 > URL: https://issues.jboss.org/browse/WFLY-1071 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Stuart Douglas > Assignee: Brian Stansberry > Fix For: 8.0.0.Alpha1 > > > If a cmp deployment is done on a server without CMP installed the EJB subsystem should detect this and throw an exception -- 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-1070) Add a redirect-socket configuration to the web connector config

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1070?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1070: ----------------------------------- Assignee: Jean-Frederic Clere (was: Brian Stansberry) > Add a redirect-socket configuration to the web connector config > --------------------------------------------------------------- > > Key: WFLY-1070 > URL: https://issues.jboss.org/browse/WFLY-1070 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Jean-Frederic Clere > > Support configuring a connector on the http socket and then redirect to the https socket without having to specify the actual port number outside of the socket-binding-group. > The referenced forum thread has an example that uses "redirect-port" for this, but a new attribute would be needed, since changing the meaning of "redirect-port" would be incompatible. > -- 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-1067) Integrate JGroups with core AS security infrastructure

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1067?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1067: ----------------------------------- Assignee: Paul Ferraro (was: Brian Stansberry) > Integrate JGroups with core AS security infrastructure > ------------------------------------------------------ > > Key: WFLY-1067 > URL: https://issues.jboss.org/browse/WFLY-1067 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Security > Reporter: Brian Stansberry > Assignee: Paul Ferraro > > Container task for better integrating JGroups security with overall AS security. The basic concept is the various security aware aspects of JGroups will expose an SPI, and the AS can create implementations of those SPIs that integrate with the AS security realms. The AS JGroups subsystem will inject the implementation into the JGroups runtime components. > Subtasks are for the various aspects. These can be done separately but a common overall design should be created to ensure a consistent approach is taken. -- 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-685) Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-685?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned WFLY-685: --------------------------------- Assignee: Brad Maxwell (was: Stuart Douglas) Correcting migration > Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory > ------------------------------------------------------------------------- > > Key: WFLY-685 > URL: https://issues.jboss.org/browse/WFLY-685 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: Awaiting Volunteers > > > Packaging Xerces in war causes JSF ClassCastException on SAXParserFactory > ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost]. (main) Exception sending context initialized event to listener instance of class org.jboss.web.jsf.integration.config.JBossJSFConfigureListener > java.lang.ClassCastException: org.apache.xerces.jaxp.SAXParserFactoryImpl cannot be cast to javax.xml.parsers.SAXParserFactory > at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:128) > at com.sun.faces.config.ConfigureListener$WebXmlProcessor.getConfiguredFactory(ConfigureListener.java:702) > at com.sun.faces.config.ConfigureListener$WebXmlProcessor.scanForFacesServlet(ConfigureListener.java:674) > at com.sun.faces.config.ConfigureListener$WebXmlProcessor.<init>(ConfigureListener.java:648) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:156) > at org.jboss.web.jsf.integration.config.JBossJSFConfigureListener.contextInitialized(JBossJSFConfigureListener.java:60) > at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3910) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:4389) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:321) > at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:145) > at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) > at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) -- 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-1061) Expose pool statistcs from a deployed .rar via the console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1061?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1061: ----------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Expose pool statistcs from a deployed .rar via the console > ----------------------------------------------------------- > > Key: WFLY-1061 > URL: https://issues.jboss.org/browse/WFLY-1061 > Project: WildFly > Issue Type: Feature Request > Reporter: Johnathon Lee > Assignee: Heiko Braun > > Currently pool statistics are not available from a resource adapter, but can be seen via jboss-cli.sh [1]. > Note this is a subset of a rejected FR [2] (found during creation of this FR) > The FR is to expose these statistics via the web console. > [1] > [standalone@localhost:9999 /] /deployment=helloworld.rar/subsystem=resource-adapters/statistics=statistics/connection-definitions=java\:\/eis\/HelloWorld:read-resource(include-runtime=true) > { > "outcome" => "success", > "result" => { > "ActiveCount" => "0", > "AvailableCount" => "20", > "AverageBlockingTime" => "0", > "AverageCreationTime" => "0", > "CreatedCount" => "0", > "DestroyedCount" => "0", > "MaxCreationTime" => "0", > "MaxUsedCount" => "0", > "MaxWaitTime" => "0", > "TimedOut" => "0", > "TotalBlockingTime" => "0", > "TotalCreationTime" => "0" > } > } > [standalone@localhost:9999 /] > [2] > https://issues.jboss.org/browse/AS7-3780 -- 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-738) Add clear cache operation on cache container and cache (accessible via admin console)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-738?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-738: ---------------------------------- Assignee: Paul Ferraro (was: Brian Stansberry) > Add clear cache operation on cache container and cache (accessible via admin console) > ------------------------------------------------------------------------------------- > > Key: WFLY-738 > URL: https://issues.jboss.org/browse/WFLY-738 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Domain Management > Reporter: Guillaume Grossetie > Assignee: Paul Ferraro > Fix For: Awaiting Volunteers > > > Add operation on infinispan subsystem to clear cache at cache container level (ie. clear all caches for the container) and at cache level. > The implementation of the clear operation just calls the method #clear() on the org.infinispan.Cache interface. If needed we can clear the associated CacheStore (make it optional ?) and handle more complex cases. -- 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-1051) Indicate failed deployment within the web console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1051?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1051: ----------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Indicate failed deployment within the web console > ------------------------------------------------- > > Key: WFLY-1051 > URL: https://issues.jboss.org/browse/WFLY-1051 > Project: WildFly > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > -- 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-734) Deadlock detection for Entity beans

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-734?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved WFLY-734. ----------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: Awaiting Volunteers) Resolution: Won't Fix Support for CMP has been dropped for WildFly 8. > Deadlock detection for Entity beans > ----------------------------------- > > Key: WFLY-734 > URL: https://issues.jboss.org/browse/WFLY-734 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Environment: Windows 7 64 bit, Java 1.7.0 64 bit > Reporter: Christian Inzko > Fix For: 8.0.0.Alpha1 > > > Deadlock detection with EJB 2.1 entity beans and pessimistic locking does not work. > We are migrating our application from Jboss 4.05 where we used entity beans. This jboss version was able to detect deadlock situations and throw a org.jboss.util.deadlock.ApplicationDeadlockException. This mechanism does no longer work - instead of that both transactions just hang until a transaction timeout is reached. -- 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-731) Store config file comments in the model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-731?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-731: ---------------------------------- Assignee: (was: Brian Stansberry) > Store config file comments in the model > --------------------------------------- > > Key: WFLY-731 > URL: https://issues.jboss.org/browse/WFLY-731 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: Awaiting Volunteers > > -- 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