January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCLUSTER-143) Create initial release schedule

by Brian Stansberry (JIRA)

Create initial release schedule ------------------------------- Key: JBCLUSTER-143 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-143 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Analyze when things need to be done so they can be integrated into dependent 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

18 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5029) Integrate jboss-ha-server-api.jar

by Brian Stansberry (JIRA)

Integrate jboss-ha-server-api.jar --------------------------------- Key: JBAS-5029 URL: http://jira.jboss.com/jira/browse/JBAS-5029 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Extract the server-side API classes from the AS codebase. -- 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

18 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1182) Specifying security Identity in ejb-jar.xml is ignored for MDB using the quartz-ra.rar resource adapter

by alex soto (JIRA)

Specifying security Identity in ejb-jar.xml is ignored for MDB using the quartz-ra.rar resource adapter ------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1182 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1182 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: AS 4.2.2.GA Environment: Java 5 Windows XP Mac OS X 10.4.11 Reporter: alex soto A MDB calling an EJB fails with Authorization failure exception when the run-as identity of the MDB is specified in the deployment descriptor files rather than with annotations. The MDB uses the quartz-ra resource adapter, but I'm not sure if this makes any difference. Here is the call stack: 16:23:00,016 INFO [CronJob] CronJob called. 16:23:00,017 ERROR [RoleBasedAuthorizationInterceptor] Insufficient permissions, principal=null, requiredRoles=[admin], principalRoles=[] 16:23:00,020 ERROR [JobRunShell] Job default.job.0.1200691035489 threw an unhandled Exception: javax.ejb.EJBTransactionRolledbackException: Authorization failure at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy72.execute(Unknown Source) at org.jboss.resource.adapter.quartz.inflow.QuartzJob.execute(QuartzJob.java:57) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: javax.ejb.EJBAccessException: Authorization failure at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:120) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:81) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107) at $Proxy67.doit(Unknown Source) at test.CronJob.execute(CronJob.java:21) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) ... 11 more 16:23:00,021 ERROR [ErrorLogger] Job (default.job.0.1200691035489 threw an exception. org.quartz.SchedulerException: Job threw an unhandled exception. [See nested exception: javax.ejb.EJBTransactionRolledbackException: Authorization failure] at org.quartz.core.JobRunShell.run(JobRunShell.java:214) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) * Nested Exception (Underlying Cause) --------------- javax.ejb.EJBTransactionRolledbackException: Authorization failure at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy72.execute(Unknown Source) at org.jboss.resource.adapter.quartz.inflow.QuartzJob.execute(QuartzJob.java:57) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520) Caused by: javax.ejb.EJBAccessException: Authorization failure at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:120) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:81) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107) at $Proxy67.doit(Unknown Source) at test.CronJob.execute(CronJob.java:21) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) ... 11 more -- 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

18 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-114) Move resources into standard maven location

by Paul Gier (JIRA)

Move resources into standard maven location ------------------------------------------- Key: SECURITY-114 URL: http://jira.jboss.com/jira/browse/SECURITY-114 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX Reporter: Paul Gier Assigned To: Anil Saldhana The current resources configuration has the files spread across a few directories. {code} <resources> <resource> <directory>src/main</directory> <includes> <include>**/*.xml</include> </includes> </resource> <resource> <directory>${basedir}</directory> <includes> <include>JBossORG-EULA.txt</include> </includes> </resource> <resource> <directory>src/resources</directory> <includes> <include>**/*.dtd</include> <include>**/*.xsd</include> </includes> </resource> <resource> <directory>target/generated-sources/javacc</directory> <includes> <include>**/*.class</include> </includes> </resource> </resources> <testResources> <testResource> <directory>src/tests/resources/</directory> </testResource> <testResource> <directory>src/main</directory> </testResource> </testResources> {code} All the resource files could be moved to the standard maven locations of src/main/resources, and src/test/resources. This way, the only configuration needed would be the appropriate includes. -- 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

18 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5087) Upgrade to JBoss Cache 2.1.0.GA

by Brian Stansberry (JIRA)

Upgrade to JBoss Cache 2.1.0.GA ------------------------------- Key: JBAS-5087 URL: http://jira.jboss.com/jira/browse/JBAS-5087 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry -- 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

18 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1871) Localize page names

by Luc Boudreau (JIRA)

Localize page names ------------------- Key: JBPORTAL-1871 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1871 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Reporter: Luc Boudreau Assigned To: Julien Viet Page names cannot be localized, which makes the whole point of localization within the CMS pretty useless. -- 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

18 years, 6 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1181) Use ClassContainer.getMethodInfo() instead of accessing the deprecated methodInterceptors field directly

by Kabir Khan (JIRA)

Use ClassContainer.getMethodInfo() instead of accessing the deprecated methodInterceptors field directly -------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1181 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1181 Project: EJB 3.0 Issue Type: Task Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: AS 5.0.0.Beta4 -- 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

18 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWEB-97) Cross-context request dispatching is not working for PHP files

by Thomas Heute (JIRA)

Cross-context request dispatching is not working for PHP files -------------------------------------------------------------- Key: JBWEB-97 URL: http://jira.jboss.com/jira/browse/JBWEB-97 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss AS 4.2.2.GA Reporter: Thomas Heute Assigned To: Mladen Turk I installed the php-examples.war from the documentation. Now i'm trying to do a cross-context request dispatching from a servlet in context /foo to the resource /index.php of the context /php-examples.war The PHP handler Servlet is lost and it ends up with: ERROR [ScriptEnvironment] Invalid script names It looks like the Servlet is looking in the wrong context. I'm attaching my test webapp which tried to include /php-examples/index.php -- 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

18 years, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1466) customizable error page in the portlet that threw the exception

by William DeCoste (JIRA)

customizable error page in the portlet that threw the exception --------------------------------------------------------------- Key: JBPORTAL-1466 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1466 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.CR2 Reporter: William DeCoste Assigned To: Julien Viet Feature request from Intuit Feature: For error handing, the portlet should be able to render a customizable error page in the portlet that threw the exception. This feature would be something similar to the error-page tag in web.xml. Currently JBoss Portal provides a way to either hide the portlet that has errors or show it with the stack trace or show it with only the error message. But there is no way where the developers could customize the contents that appear in the window for the portlet that throws an exception. We had opened case #00015844 about not being able to use web.xml error-page tag with JBoss portal applications. The provided solution about catching the specific exception in the render method does not work as it is not customizable & too tied up with the portlet class code. And as you might be aware about the WAP function - someone using the WAP application components will not be able to customize it according to their requirements. We know that the portlet standard doesn't specify what to do, and we're just trying to have it behave as much like a regular web application in lieu of something being in the standard. -- 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

18 years, 6 months

4
13
0 / 0

[JBoss JIRA] Created: (JBAOP-515) Awful error report to syserr: use logger for this instead

by Carlos XXXXX (JIRA)

Awful error report to syserr: use logger for this instead --------------------------------------------------------- Key: JBAOP-515 URL: http://jira.jboss.com/jira/browse/JBAOP-515 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR3 Reporter: Carlos XXXXX Priority: Minor When trying to introduce the same method twice, an error is correctly reported. But no matter which setting is having effect (verbose true/false, suppressTransformationErrors true/false), this error is printed directly to the console, ignoring the logging system. This should be in an ERROR level log entry, it's not a fatal error that aborts execution. java.lang.RuntimeException: Mixin jbossaop.SirenMixin of pointcut file:/home/carlos/dev/java/eclipse/test-stuff/src/jbossaop/jboss-aop.xml3 is trying to apply an already existing methodsing for class jbossaop.Bean at org.jboss.aop.instrument.Instrumentor.addMixin(Instrumentor.java:321) at org.jboss.aop.instrument.Instrumentor.instrumentIntroductions(Instrumentor.java:386) at org.jboss.aop.instrument.Instrumentor.transform(Instrumentor.java:725) at org.jboss.aop.instrument.GeneratedAdvisorInstrumentor.transform(GeneratedAdvisorInstrumentor.java:120) at org.jboss.aop.SuperClassesFirstWeavingStrategy.instrumentClass(SuperClassesFirstWeavingStrategy.java:200) at org.jboss.aop.SuperClassesFirstWeavingStrategy.translate(SuperClassesFirstWeavingStrategy.java:70) at org.jboss.aop.AspectManager.translate(AspectManager.java:934) at org.jboss.aop.AspectManager.transform(AspectManager.java:880) .... -- 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

18 years, 6 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 January 2008