January 2007 - jboss-jira - Jboss List Archives

[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, 3 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3969) IOException: unknown protocol: vfsfile

by Thomas Diesler (JIRA)

IOException: unknown protocol: vfsfile -------------------------------------- Key: JBAS-3969 URL: http://jira.jboss.com/jira/browse/JBAS-3969 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.CR1 All webservice tests fail because of Caused by: java.io.IOException: unknown protocol: vfsfile at java.net.URL.readObject(URL.java:1217) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.jboss.ws.core.jaxrpc.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:112) An application client is bound into JNDI. At lookup time and object is deserialized that contains a URL property with the vfsfile protocol. It seems that the JNDI layer is not aware of the URLStreamHandlerFactory -- 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, 3 months

2
2
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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-841) Only allow classes which implement Pool in PoolClass annotation

by Carlo de Wolf (JIRA)

Only allow classes which implement Pool in PoolClass annotation --------------------------------------------------------------- Key: EJBTHREE-841 URL: http://jira.jboss.com/jira/browse/EJBTHREE-841 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Minor Fix For: EJB 3.0 RC10 - FD -- 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, 3 months

2
3
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, 3 months

4
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-104) DeploymentContext shortName for jar is messed up as well as url

by Bill Burke (JIRA)

DeploymentContext shortName for jar is messed up as well as url --------------------------------------------------------------- Key: JBMICROCONT-104 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-104 Project: JBoss MicroContainer Issue Type: Bug Components: Container Reporter: Bill Burke The DeploymentContext.getName() ends up being the full URL of a JAR if you have a JAR file within a directory, its name is jar:file:/.../foo.jar!/ Shouldn't this be a "short" name? My bet this has something to do with how the URL is messed up too for VirtualFiles that are JARs. -- 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, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBREM-634) update doc on callbacks

by Tom Elrod (JIRA)

update doc on callbacks ----------------------- Key: JBREM-634 URL: http://jira.jboss.com/jira/browse/JBREM-634 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: callbacks Affects Versions: 2.2.0.Alpha3 (Bluto) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Update doc to include more info on callbacks, especially changes made for JBREM-622 -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-335) Create a Maven plugin version of JBossRetro

by Paul Gier (JIRA)

Create a Maven plugin version of JBossRetro ------------------------------------------- Key: JBBUILD-335 URL: http://jira.jboss.com/jira/browse/JBBUILD-335 Project: JBoss Build System Issue Type: Feature Request Components: JBossRetro, Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: JBossBuild-1.1 RC1 In order for maven to build the retro versions of various projects, it would be nice to have a maven plugin version of JBossRetro. -- 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, 3 months

2
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-831) REQUIRES_NEW is supported for MDBs - not allowed by spec

by William DeCoste (JIRA)

REQUIRES_NEW is supported for MDBs - not allowed by spec -------------------------------------------------------- Key: EJBTHREE-831 URL: http://jira.jboss.com/jira/browse/EJBTHREE-831 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste Per spec, "For a message-driven bean's message listener methods (or interface), only the REQUIRED and NOT_SUPPORTED TransactionAttribute values may be used." -- 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, 3 months

2
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 January 2007