November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-86) Adapt Resource Interface for ACL

by Anil Saldhana (JIRA)

Adapt Resource Interface for ACL -------------------------------- Key: SECURITY-86 URL: http://jira.jboss.com/jira/browse/SECURITY-86 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: 2.0.1.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA The Authorization framework interface "Resource" needs to be adapted for the ACL implementation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-93) Identity SPI

by Anil Saldhana (JIRA)

Identity SPI ------------ Key: SECURITY-93 URL: http://jira.jboss.com/jira/browse/SECURITY-93 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Identity Affects Versions: 2.0.1.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA Need a first cut Identity API for the ACL implementation. Basically, we want to represent identity, role and group. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-87) AuthorizationManager interface needs ACL semantics

by Anil Saldhana (JIRA)

AuthorizationManager interface needs ACL semantics -------------------------------------------------- Key: SECURITY-87 URL: http://jira.jboss.com/jira/browse/SECURITY-87 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security SPI Affects Versions: 2.0.1.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA The AuthorizationManager interface needs to be upgraded to handle the fast ACL implementation needs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4294) HttpSessionListener.sessionDestroyed is not invoked when the app gets undeployed

by Vladimir Piskarev (JIRA)

HttpSessionListener.sessionDestroyed is not invoked when the app gets undeployed -------------------------------------------------------------------------------- Key: JBAS-4294 URL: http://jira.jboss.com/jira/browse/JBAS-4294 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Vladimir Piskarev Assigned To: Remy Maucherat HttpSessionListener.sessionDestroyed is not invoked when the app gets undeployed. The bug affects JBossAS-4.0.4GA and later. JBossAS-4.0.3SP1 doesn't have this problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-4506) Unify the EJB 2 and EJB 3 deployers

by Carlo de Wolf (JIRA)

Unify the EJB 2 and EJB 3 deployers ----------------------------------- Key: JBAS-4506 URL: http://jira.jboss.com/jira/browse/JBAS-4506 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB2, EJB3, Web Services Reporter: Carlo de Wolf Assigned To: Scott M Stark The current deployer chain has no notion of annotations. A new deployer chain has to be created, which looks something like this: EjbAnnotationParsingDeployer -> EjbParsingDeployer -> JBossEjbParsingDeployer -> EjbDeployer -> SomeContainerDeployer... A new common metadata component needs to be build in projects/??/jboss-metadata which combines EJB 2 and EJB 3 metadata (and also has JavaEE metadata). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4039) Error Instantiating ExpressionFactory

by Kai Hackemesser (JIRA)

Error Instantiating ExpressionFactory ------------------------------------- Key: JBAS-4039 URL: http://jira.jboss.com/jira/browse/JBAS-4039 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta1 Environment: Windows XP SP2, Java 6 Reporter: Kai Hackemesser Assigned To: Remy Maucherat Priority: Minor This error is in my console log: 13:40:00,093 ERROR [STDERR] 31.01.2007 13:40:00 com.sun.faces.config.ConfigureListener registerELResolverAndListenerWithJsp SCHWERWIEGEND: Error Instantiating ExpressionFactory java.lang.ClassNotFoundException: com.sun.el.ExpressionFactoryImpl at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1355) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1201) at java.lang.ClassLoader.loadClassInternal(Unknown Source) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at com.sun.faces.config.ConfigureListener.registerELResolverAndListenerWithJsp(ConfigureListener.java:1682) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:513) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4336) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5285) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:297) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.web.tomcat.tc6.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:302) at org.jboss.web.tomcat.tc6.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:129) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:355) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:88) at org.jboss.web.deployers.WebModule.start(WebModule.java:66) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184) at $Proxy0.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:226) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:198) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:709) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:429) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:538) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:472) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:320) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:190) at org.jboss.system.ServiceController.doChange(ServiceController.java:656) at org.jboss.system.ServiceController.start(ServiceController.java:431) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:124) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:85) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:44) at org.jboss.deployers.plugins.deployers.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:53) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401) at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340) at org.jboss.Main.boot(Main.java:210) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4633) ClientAbortException stacktrace lines log as separate Log4J events.

by Matthew Robinson (JIRA)

ClientAbortException stacktrace lines log as separate Log4J events. ------------------------------------------------------------------- Key: JBAS-4633 URL: http://jira.jboss.com/jira/browse/JBAS-4633 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.5.GA Environment: SuSE Linux 10.0 Reporter: Matthew Robinson Assigned To: Remy Maucherat Priority: Minor A ClientAbortException is raised legitimately when an end-user closes thier browser before the web app is finished responding to the request. However, when the stacktrace is generated, it seems that each line is being logged using separate Log4J logger.log() call. This results in a nice looking file-base log: 2007-08-27 09:10:31,402 ERROR [STDERR] ClientAbortException: java.net.SocketException: Broken pipe 2007-08-27 09:10:31,640 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:366) 2007-08-27 09:10:31,937 ERROR [STDERR] at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:353) 2007-08-27 09:10:32,131 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392) 2007-08-27 09:10:32,326 ERROR [STDERR] at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381) 2007-08-27 09:10:32,607 ERROR [STDERR] at org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.java:88) ... But it causes unnecessary grief and clutter when using SMTP to log errors. Each line results in a separate email! So my inbox fills with an average of 60 emails per ClientAbortException! This problem seems to confined to the ClientAbortException. Other errors log the stacktrace as a single Log4J event. Please may I have this error logged in the same way? Ta. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4970) Hot redeployment displaying old content

by Petr Hejl (JIRA)

Hot redeployment displaying old content --------------------------------------- Key: JBAS-4970 URL: http://jira.jboss.com/jira/browse/JBAS-4970 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta2 Environment: Linux 2.6.22-14-generic java version "1.5.0_13" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05) Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode) Reporter: Petr Hejl Assigned To: Remy Maucherat Priority: Critical If the war is hot redeployed (delete war, copy the new one) fast enough, the server still displays the old content. It notes the new one - the expanded content at tmp/deploy/webaap-....war is the fresh one, however the (freshly) compiled jsps (in work/jboss.web/localhost/webapp/org/apache/jsp) are still the old. Same occurs for the war inside the ear. Occurs for both J2EE1.4 and Java EE5 projects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-167) Implement generic dependency annotation handling

by Ales Justin (JIRA)

Implement generic dependency annotation handling ------------------------------------------------ Key: JBMICROCONT-167 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-167 Project: JBoss MicroContainer Issue Type: Feature Request Components: Dependency Reporter: Ales Justin Assigned To: Ales Justin Handle dependency annotations in Decribe and Instantiate (factory generated beans) states. Add appropriate dependency / install items. Handling should be generic - easily able to add / handle new dependency annotations. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3460) Allow per-webapp configuration of useJK, snapshotMode and snapshotInterval

by Brian Stansberry (JIRA)

Allow per-webapp configuration of useJK, snapshotMode and snapshotInterval -------------------------------------------------------------------------- Key: JBAS-3460 URL: http://jira.jboss.com/jira/browse/JBAS-3460 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.1.CR1 The Tomcat SAR's useJK, snapshotMode and snapshotInterval attributes all drive the creation of valves that are deployed per web-app. Therefore the properties could also be changed per web-app. Need to add them to jboss-web.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 1 month

3
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007