September 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4547) Fix RunAsSecurityInterceptor

by Kabir Khan (JIRA)

Fix RunAsSecurityInterceptor ---------------------------- Key: JBAS-4547 URL: http://jira.jboss.com/jira/browse/JBAS-4547 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: AOP Affects Versions: JBossAS-4.2.1.GA Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossAS-4.2.2.GA Add this fix once branch is no longer frozen -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4680) Update example for JBossWS Message TRACE in jboss-log4j.xml

by Darran Lofthouse (JIRA)

Update example for JBossWS Message TRACE in jboss-log4j.xml ----------------------------------------------------------- Key: JBAS-4680 URL: http://jira.jboss.com/jira/browse/JBAS-4680 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-4.2.1.GA Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.2.2.GA The current example for JBossWS message logging is: -  However the category has been changed so the example needs to be changed to: -  -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPM-1008) ejb deployment : avoid ClassNotFoundException on client side after unmarshalling

by Adrian Dimulescu (JIRA)

ejb deployment : avoid ClassNotFoundException on client side after unmarshalling --------------------------------------------------------------------------------- Key: JBPM-1008 URL: http://jira.jboss.com/jira/browse/JBPM-1008 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM jPDL 3.2.1 Environment: enterprise jBPM Reporter: Adrian Dimulescu Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.2 Two aspects in this jira : 1: hide hibernate-specific exceptions; 2: hide hibernate-specific datatypes. 1. The EJB client only depends on the jBPM jar (for the various Command implementations) and on the JBoss client jar. If a Hibernate exception occurs, it is wrapped by a JBPMException and rethrown. When deserialiezed on the client side (which does not have a Hibernate dependency), a ClassNotFoundException occurs. I think the CommandServiceBean should not wrap internal implementation-specific exceptions; it should instead simply copy the stack trace and throw a new implementation-independent exception which contains the exception trace without containing the causes themselves. That typically avoids ClassNotFoundExceptions without losing exception history. 2. The second problem is that hibernate-specific collections get serialized over the wire, here is the description of the problem : I use the GetProcessInstancesCommand in order to experiment with querying the remote ejb. This command returns a list with ProcessInstances. A ProcessInstance is read by Hibernate from the database. As Hibernate uses specific lazy-loading-aware implementations for collections -- the ProcessInstance.instances attribute, which is declared of type java.util.Map, is actually implemented by org.hibernate.collections.PersistentMap. Which generates class loading exception while deserializing to hibernate-unaware ejb clients. The solution would then be for the Command implementations to return clean JDK collections, by replacing Hibernate collection with JDK standard ones. Note that IIUC only the collections must be replaced, not the collection contents too, so the "cleaning" operation should not be that expensive. Cleaning should be only done in the SLSB remote call use case -- because in-JVM callers may want to benefit lazy-loading. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1153) Accumulate/Collect can't be used in queries

by Edson Tirelli (JIRA)

Accumulate/Collect can't be used in queries ------------------------------------------- Key: JBRULES-1153 URL: http://jira.jboss.com/jira/browse/JBRULES-1153 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Edson Tirelli Assigned To: Mark Proctor query "Count possible cell values"( $row, $col ) # A superclass or interface can be used to match any derived classes $count : Number() from accumulate( $a : AbstractCellValue( row == $row, col == $col ), count( $a ) ) end -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1165) StatelessSession does not have the ability to set globals.

by Michael Neale (JIRA)

StatelessSession does not have the ability to set globals. ----------------------------------------------------------- Key: JBRULES-1165 URL: http://jira.jboss.com/jira/browse/JBRULES-1165 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Reteoo Affects Versions: 4.0.1 Reporter: Michael Neale Assigned To: Mark Proctor Fix For: 4.0.2 Most likely an oversight. However, to keep the stateless nature of the API - there isn't another way to do this other then add more methods to the interface, unfortunately. -- 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, 10 months

2
12
0 / 0

[JBoss JIRA] Created: (JBAS-4693) Any cluster-config element in EJB2 jboss.xml is ignored

by Brian Stansberry (JIRA)

Any cluster-config element in EJB2 jboss.xml is ignored ------------------------------------------------------- Key: JBAS-4693 URL: http://jira.jboss.com/jira/browse/JBAS-4693 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, EJB2 Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 JBossEjbObjectFactory.newChild(BeanHolder bean, UnmarshallingContext navigator, String namespaceURI, String localName, Attributes attrs) does not set the local variable "child" when processing localName "cluster-config". As a a result the method returns null and no ClusterConfigMetaData gets associated with the BeanMetaData. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4692) NPE starting EJB2 entity container with cache invalidation

by Brian Stansberry (JIRA)

NPE starting EJB2 entity container with cache invalidation ---------------------------------------------------------- Key: JBAS-4692 URL: http://jira.jboss.com/jira/browse/JBAS-4692 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 InvalidableEntityInstanceCache.start() throws an NPE on line 123: String groupName = emd.getDistributedCacheInvalidationConfig().getInvalidationGroupName(); Problem is EntityMetaData.getDistributedCacheInvalidationConfig() will return null in the usual situation where there is no "cache-invalidation-config" element. In 4.x this doesn't occur because EntityMetaData.importFromJBossXml() ensures that a default CacheInvalidationConfigMetaData is created. Solution is to lazy initialize the default CacheInvalidationConfigMetaData in EntityMetaData.getDistributedCacheInvalidationConfig(). -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1066) XARecoveryTest::testMockCoordinatorRecoveryWithJBossTSXids makes XAResourceRecoveryTest::testRecoveryOnSend to fail

by Clebert Suconic (JIRA)

XARecoveryTest::testMockCoordinatorRecoveryWithJBossTSXids makes XAResourceRecoveryTest::testRecoveryOnSend to fail ------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1066 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1066 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Clebert Suconic -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JASSIST-35) Equals and Hashcode on Javassist's (proxied) Annotations do not match the java.lang.Annotation contract

by Paul Field (JIRA)

Equals and Hashcode on Javassist's (proxied) Annotations do not match the java.lang.Annotation contract ------------------------------------------------------------------------------------------------------- Key: JASSIST-35 URL: http://jira.jboss.com/jira/browse/JASSIST-35 Project: Javassist Issue Type: Bug Reporter: Paul Field Assigned To: Shigeru Chiba java.lang.Annotation defines that implementation provide a very particular implementation of equals() and hashcode() that implement a definition of "logically equivalent" for annotations. See: http://java.sun.com/j2se/1.5.0/docs/api/java/lang/annotation/Annotation.html The current implementation of Javassist (3.6.0 RC1) uses a proxy backed by javassist.bytecode.annotation.AnnotationImpl. It does not implement hashcode() and equals() according to the Annotation contract. This makes it hard to tell if two annotations are equivalent (e.g. when the same type of annotation has been used on various overriden versions of a method). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4691) JACC: Unchecked WebUserDataPermission(s) for excluded and transport guarantee use cases

by Anil Saldhana (JIRA)

JACC: Unchecked WebUserDataPermission(s) for excluded and transport guarantee use cases --------------------------------------------------------------------------------------- Key: JBAS-4691 URL: http://jira.jboss.com/jira/browse/JBAS-4691 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.2.2.GA If security constraints exist with an excluding auth-constraint, then a WUDP needs to be added to unchecked policy for http methods that are non-excluded. Additionally, an unchecked perm should be added for : /** * A WebResourcePermission and a WebUserDataPermission must be added to the unchecked * policy statements for each url-pattern in the DD and the default pattern, "/", that is not combined by the webresource-collection elements of the deployment descriptor * with every HTTP method value. (JACC 1.0: Section 3.1.3.1) */ -- 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, 10 months

1
1
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 September 2007