October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3611) Get the jboss-4.0-testsuite-sun-1.5 passing

by Dimitris Andreadis (JIRA)

Get the jboss-4.0-testsuite-sun-1.5 passing ------------------------------------------- Key: JBAS-3611 URL: http://jira.jboss.com/jira/browse/JBAS-3611 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA Container task for sun jdk1.5 test run failures -- 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

19 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-3582) Get the ejb3-4.0 testsuite passing

by Dimitris Andreadis (JIRA)

Get the ejb3-4.0 testsuite passing ---------------------------------- Key: JBAS-3582 URL: http://jira.jboss.com/jira/browse/JBAS-3582 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Bill Burke Fix For: JBossAS-4.0.5.CR1 There are currenlty 28 failures -- 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

19 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBAS-3800) EJBQLToSQL92Compiler should use only searchable columns with DISTINCT

by Alexey Loubyansky (JIRA)

EJBQLToSQL92Compiler should use only searchable columns with DISTINCT --------------------------------------------------------------------- Key: JBAS-3800 URL: http://jira.jboss.com/jira/browse/JBAS-3800 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Currently it selects all columns which causes errors since, e.g. BLOBs are not comparable or searchable and, hence, can't be used with distinct. -- 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

19 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-3792) Better error reporting when messages "mysteriously" vanish

by Adrian Brock (JIRA)

Better error reporting when messages "mysteriously" vanish ---------------------------------------------------------- Key: JBAS-3792 URL: http://jira.jboss.com/jira/browse/JBAS-3792 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Reporter: Adrian Brock Fix For: JBossAS-4.0.6.GA It is commonly the case that people try to run two instances of JBossMQ against the same database tables. This can lead to errors like the ones in the parent task or a similar message in the delete when doing acknowledgements. These error messages need improving and also give a hint to the possible reasons, e.g. 1) competing JBossMQs trying to share the same database 2) trying to use a replicating database that does not support synchronous replication (i..e there is a delay in a row getting written to one database before it appears in the other database) The parent issue's error message belongs in org.jboss.mq.pm.jdbc2.PersistenceManager public SpyMessage loadFromStorage(MessageReference messageRef) throws JMSException { ... rs = stmt.executeQuery(); if (rs.next()) return extractMessage(rs); + else throw new JMSException("Unable to load message " + messageRef + " from storage, are you trying to share database tables between JBossMQ instances? Are you using a replicating database that does not support synchronous replication?"); - return null; -- 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

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-136) Set up project in SVN

by Brian Stansberry (JIRA)

Set up project in SVN --------------------- Key: JBCLUSTER-136 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-136 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Determine where in the repository the project should reside, layout project structure, etc. -- 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

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1020) Replace direct uses of Log4J by JBoss logging.

by Chris Laprun (JIRA)

Replace direct uses of Log4J by JBoss logging. ---------------------------------------------- Key: JBPORTAL-1020 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1020 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4 Final, 2.2 Branch Reporter: Chris Laprun Priority: Minor 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

19 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1046) documentation for Ldap/Portal integration

by Boleslaw Dawidowicz (JIRA)

documentation for Ldap/Portal integration ----------------------------------------- Key: JBPORTAL-1046 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1046 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.Alpha1 Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.Alpha1 Create documentation of configuring Portal with LDAP. It needs to cover new implementation of identity modules in 2.6 -- 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

19 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (SECURITY-15) Docbook for Security Project

by Anil Saldhana (JIRA)

Docbook for Security Project ---------------------------- Key: SECURITY-15 URL: http://jira.jboss.com/jira/browse/SECURITY-15 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 Create a Doc Book project for security -- 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-326) JBossRetro missing getDeclaredAnnotations; getAnnotations implementation is deficient

by David Lloyd (JIRA)

JBossRetro missing getDeclaredAnnotations; getAnnotations implementation is deficient ------------------------------------------------------------------------------------- Key: JBBUILD-326 URL: http://jira.jboss.com/jira/browse/JBBUILD-326 Project: JBoss Build System Issue Type: Bug Components: JBossRetro Affects Versions: JBossRetro-1.0.4.GA Reporter: David Lloyd Priority: Minor Fix For: JBossRetro-1.0.5.GA I put in a fix to JBossRetro to add support for getDeclaredAnnotations on Method, Field, Constructor, and AccessibleObject. In doing this I realized that getAnnotations seems to be doing what getDeclaredAnnotations is supposed to be doing; according to the JDK javadocs, getAnnotations is supposed to return inherited annotations as well as declared annotations, whereas getDeclaredAnnotations only returns annotations on the specific object. I committed a change to implement getDeclaredAnnotations which essentially duplicates the current getAnnotations behavior, but someone may want to go in and enhance getAnnotations. I'm attaching the patch that I committed in case I'm wrong and someone wants to revert it. -- 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

19 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3781) Stateful SB Instance Interceptor should not push SubjectContext if RunAsIdentity present

by Anil Saldhana (JIRA)

Stateful SB Instance Interceptor should not push SubjectContext if RunAsIdentity present ---------------------------------------------------------------------------------------- Key: JBAS-3781 URL: http://jira.jboss.com/jira/browse/JBAS-3781 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA, JBossAS-3.2.8.SP1, JBossAS-5.0.0.Beta Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta, JBossAS-3.2.8.SP2, JBossAS-4.0.6.CR1 The following Subject Context push (with null Subject) to establish client security context should not be performed if the user has configured a RunAsIdentity in the caller bean. /* The security context must be established before the cache lookup because the activation of a session should have the caller's security context as ejbActivate is allowed to call other secured resources. Since the pm makes the ejbActivate call, we need to set the caller's security context. The only reason this shows up for stateful session is that we moved the SecurityInterceptor to after the instance interceptor to allow security exceptions to result in invalidation of the session. This may be too literal an interpretation of the ejb spec requirement that runtime exceptions should invalidate the session. */ SecurityActions.pushSubjectContext(mi.getPrincipal(), mi.getCredential(), null); The resolution is: if(SecurityActions.peekRunAsIdentity() == null) SecurityActions.pushSubjectContext(mi.getPrincipal(), mi.getCredential(), null); -- 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

19 years, 2 months

4
4
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 October 2006