October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBTM-72) Trail map neglects to remind reader to start recovery manager

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-72?page=all ] Mark Little reassigned JBTM-72: ------------------------------- Assignee: Mark Little (was: Jonathan Halliday) > Trail map neglects to remind reader to start recovery manager > ------------------------------------------------------------- > > Key: JBTM-72 > URL: http://jira.jboss.com/jira/browse/JBTM-72 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.2.2 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-741) Aspects RunAsSecurityInterceptors should push the current RunAsIdentity onto the stack

by Anil Saldhana (JIRA)

Aspects RunAsSecurityInterceptors should push the current RunAsIdentity onto the stack -------------------------------------------------------------------------------------- Key: EJBTHREE-741 URL: http://jira.jboss.com/jira/browse/EJBTHREE-741 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD Irrespective of whether the current ejb defines a RunAs annotation or not, there is a need to push the current RunAsIdentity (can be null) on the RunAs stack in the SecurityAssociation RunAs stack such that a peek into the stack at a depth of 1, always returns the correct RunAsIdentity of the caller. Note that depth 0, would be the current RunAsIdentity of the bean/component in consideration. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-740) RunASSecurityInterceptorFactory should not return NullInterceptor

by Anil Saldhana (JIRA)

RunASSecurityInterceptorFactory should not return NullInterceptor ----------------------------------------------------------------- Key: EJBTHREE-740 URL: http://jira.jboss.com/jira/browse/EJBTHREE-740 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD Currently the RunAsSecurityInterceptorFactory returns a NullInterceptor is the RunAs annotation is missing. You can control whether this factory gets called or not via the pointcut binding in ejb3-interceptors.aop -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-739) Jacc layer should throw javax.ejb.EJBAccessException

by Anil Saldhana (JIRA)

Jacc layer should throw javax.ejb.EJBAccessException ---------------------------------------------------- Key: EJBTHREE-739 URL: http://jira.jboss.com/jira/browse/EJBTHREE-739 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: EJB 3.0 RC10 - FD I see that JaccHelper throws SecurityException. I think JEE5 has a requirement for javax.ejb.EJBAccessException http://java.sun.com/javaee/5/docs/api/javax/ejb/EJBAccessException.html -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-105) Use a true UID implementation

by Mark Little (JIRA)

Use a true UID implementation ----------------------------- Key: JBESB-105 URL: http://jira.jboss.com/jira/browse/JBESB-105 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Alpha 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 The core code uses the notion of a UID, but seems to only use a long. If this needs to be unique, then we need to look at using a proper UID 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

18 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBJMX-102) JSR-77 / MEJB support does not work for many MBeans

by Peter Becker (JIRA)

JSR-77 / MEJB support does not work for many MBeans --------------------------------------------------- Key: JBJMX-102 URL: http://jira.jboss.com/jira/browse/JBJMX-102 Project: JBoss JMX Issue Type: Bug Affects Versions: JBossAS-4.0.0 Environment: Obeyed on Windows XP with newest JBoss 4.04 release Reporter: Peter Becker My administration client cannot access many (about 50 %) of the MBeans in the MEJB because they use non-serializable classes. I receive lots of exceptions like java.io.NotSerializableException: org.jboss.mx.loading.UnifiedLoaderRepository3 java.io.NotSerializableException: org.jboss.tm.TxManager java.io.NotSerializableException: org.jboss.tm.XidFactory java.io.NotSerializableException: java.lang.reflect.Method java.io.NotSerializableException: java.util.Hashtable$ValueCollection The exceptions occur when I try to read the MBean attributes. The JBoss classes used by MBeans need to be Serializable, and they must not use non.-Serializable classes to make the JSR-77 feature work 100%. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-701) Do not truncate long messages/exceptions

by Ryan Campbell (JIRA)

Do not truncate long messages/exceptions ---------------------------------------- Key: JBPM-701 URL: http://jira.jboss.com/jira/browse/JBPM-701 Project: JBoss jBPM Issue Type: Sub-task Environment: Sybase/DB2 Reporter: Ryan Campbell Assigned To: Tom Baeyens For sybase, a "text" column should be used instead of the current varchar(4000) This will prevent the truncation of stack traces. Similarly, a CLOB or equivalent should be used on DB2. -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-700) Out-of-the-box compatibility with Sybase and DB2

by Ryan Campbell (JIRA)

Out-of-the-box compatibility with Sybase and DB2 ------------------------------------------------ Key: JBPM-700 URL: http://jira.jboss.com/jira/browse/JBPM-700 Project: JBoss jBPM Issue Type: Feature Request Environment: Sybase 12.5 DB2 8.x Reporter: Ryan Campbell Assigned To: Tom Baeyens Priority: Critical Fix For: jBPM 3.1.2 jBPM must be compatible with Sybase 12.5 and DB2 8.x without any manual modification by the user. There should either be a sybase/db2 specific hibernate configuration, or some automated way of generating such. This should be validated on release. Linked tasks will document the issues we have run into which have made a generic hibernate configuration untenable. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPM-702) Use non-nullable binary fields instead of varbinary on Sybase

by Ryan Campbell (JIRA)

Use non-nullable binary fields instead of varbinary on Sybase ------------------------------------------------------------- Key: JBPM-702 URL: http://jira.jboss.com/jira/browse/JBPM-702 Project: JBoss jBPM Issue Type: Sub-task Reporter: Ryan Campbell Assigned To: Tom Baeyens -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1078) CMSPortlet default content update

by Roy Russo (JIRA)

CMSPortlet default content update --------------------------------- Key: JBPORTAL-1078 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1078 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 -- 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, 5 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006