March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBDEPLOY-255) Move DeploymentMetaData to spi

by Ales Justin (JIRA)

Move DeploymentMetaData to spi ------------------------------ Key: JBDEPLOY-255 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-255 Project: JBoss Deployers Issue Type: Task Components: classloading Affects Versions: JBDEPLOY-2.2.x Reporter: Ales Justin Assignee: Ales Justin DeploymentMetaData should be in spi. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBNAME-40) JNDI Lookup for EJB3 Component with EJB2 Interface delivers wrong Proxy (EJB3 instead of EJB2)

by Volker Raum (JIRA)

JNDI Lookup for EJB3 Component with EJB2 Interface delivers wrong Proxy (EJB3 instead of EJB2) ---------------------------------------------------------------------------------------------- Key: JBNAME-40 URL: https://jira.jboss.org/jira/browse/JBNAME-40 Project: JBoss Naming Issue Type: Bug Affects Versions: 5.1.0.GA Environment: JBoss 5.1.0 (out of the box). Windows 7 (64 Bit), Also under Windows XP (32 Bit) Java 1.6.0_16 (Sun) Reporter: Volker Raum Two EJB components are packaged into two jars within an EAR. EJB3 is an EJB3.0 Stateless Session Bean. EJB2 is a EJB2.0 Stateless Session Bean. EJB2 needs access to EJB3 so EJB3 was equipped with EJB2.0 Home and Remote Interfaces. 1. The EJB3 is coded like that: ... @Stateless(name="EJB3") @RemoteHome(EJB3Home.class) public class EJB3Bean implements EJB3 { ... 2. EJB3Home looks like this: (for compatibility with EJB2.0) public interface EJB3Home extends EJBHome { public EJB3Remote create() throws CreateException, RemoteException; } 3. EJB3 is the EJB3 Business Remote Interface (according to EJB3.0 Spec) and looks like this: @Remote public interface EJB3 { public void doThings() ; 4. EJB3Remote is a Remote Interface according to the EJB2.0 Spec: public interface EJB3Remote extends EJBObject { public void doThings() throws RemoteException ; ... 5. For the EJB2 there is a deployment descriptor defined. The section for the EJB2 Session Bean contains the following ejb-ref: ... <ejb-ref> <ejb-ref-name>EJB2Remote</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> EJB3Home EJB3Remote <ejb-link>EJB3</ejb-link>  </ejb-ref> ... 6. The EJB2 does a Lookup like Object obj = jndi.lookup("EJB2Remote") ; What i would expect is an object implementing EJB3Home. After narrowing it i could call create() with it and get a EJB3Remote Object. But what i get instead is an object of type EJB3, the Business Interface. Looks like a bug. jaikiran from the community forums asked me to report this as bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBXB-245) JBossXBNoSchemaBuilder checks for org.jboss.reflect.plugins.introspection.ParameterizedClassInfo to get parameterized collection type

by Kabir Khan (JIRA)

JBossXBNoSchemaBuilder checks for org.jboss.reflect.plugins.introspection.ParameterizedClassInfo to get parameterized collection type ------------------------------------------------------------------------------------------------------------------------------------- Key: JBXB-245 URL: https://jira.jboss.org/jira/browse/JBXB-245 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Kabir Khan Assignee: Kabir Khan The javassist implementation of JBoss reflect does not use this class. There is no need to cast, since straight ClassInfos have the getActualTypeArguments() method -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1787) Update security API to work with EAP 5

by Howard Gao (JIRA)

Update security API to work with EAP 5 -------------------------------------- Key: JBMESSAGING-1787 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1787 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Affects Versions: 1.4.6.GA Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.6.GA.SP1 EAP 5 security uses a different set of APIs that are different from EAP/AS 4x. JBM need to update its relevant code for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-478) PicketBox Libraries into AS6 trunk

by Anil Saldhana (JIRA)

PicketBox Libraries into AS6 trunk ---------------------------------- Key: SECURITY-478 URL: https://jira.jboss.org/jira/browse/SECURITY-478 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: AS-Integration Reporter: Anil Saldhana Assignee: Stefan Guilhen Fix For: PicketBox_v3_0_beta4 Will require a PicketBox beta4 release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-479) Release PicketBox 3.0.0.Beta4

by Anil Saldhana (JIRA)

Release PicketBox 3.0.0.Beta4 ----------------------------- Key: SECURITY-479 URL: https://jira.jboss.org/jira/browse/SECURITY-479 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Release Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Stefan Guilhen Fix For: PicketBox_v3_0_beta4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBEE-33) JACC needs update to 1.4

by Paul Gier (JIRA)

JACC needs update to 1.4 ------------------------ Key: JBEE-33 URL: https://jira.jboss.org/jira/browse/JBEE-33 Project: JBoss JavaEE APIs Issue Type: Task Reporter: Paul Gier Assignee: Shelly McGowan According to the javaee 6 page [1], the jacc spec version should be at 1.4, but we currently only have 1.1. A new spec subproject should be created, and the javaee 6 aggregated should be updated. [1]http://jcp.org/aboutJava/communityprocess/final/jsr316/index.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (SECURITY-483) ConcurrentModificationException from the JBoss security manager

by Anil Saldhana (JIRA)

ConcurrentModificationException from the JBoss security manager --------------------------------------------------------------- Key: SECURITY-483 URL: https://jira.jboss.org/jira/browse/SECURITY-483 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_beta3 Environment: JBoss AS trunk Reporter: Jeff Mesnil Assignee: Stefan Guilhen Fix For: PicketBox_v3_0_beta4 When HornetQ delegates roles validation to JBoss Security manager, it throws a ConcurrentModificationException: 16:58:24,449 ERROR [org.hornetq.core.protocol.core.ServerSessionPacketHandler] Caught unexpected exception: java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) at java.util.AbstractList$Itr.next(AbstractList.java:343) at org.jboss.security.identity.plugins.SimpleRoleGroup.containsRole(SimpleRoleGroup.java:181) at org.jboss.security.plugins.JBossAuthorizationManager.doesRoleGroupHaveRole(JBossAuthorizationManager.java:254) at org.jboss.security.plugins.JBossAuthorizationManager.doesUserHaveRole(JBossAuthorizationManager.java:194) at org.jboss.security.plugins.auth.JaasSecurityManagerBase.doesUserHaveRole(JaasSecurityManagerBase.java:434) at org.jboss.security.plugins.JaasSecurityManager.doesUserHaveRole(JaasSecurityManager.java:195) at org.hornetq.integration.jboss.security.JBossASSecurityManager.validateUserAndRole(JBossASSecurityManager.java:110) This issue prevents to run TCK's JMS tests with security enabled in HornetQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-477) ConcurrentModificationException from the security manager

by Jeff Mesnil (JIRA)

ConcurrentModificationException from the security manager --------------------------------------------------------- Key: SECURITY-477 URL: https://jira.jboss.org/jira/browse/SECURITY-477 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jeff Mesnil Assignee: Anil Saldhana When HornetQ delegates roles validation to JBoss Security manager, it throws a ConcurrentModificationException: 16:58:24,449 ERROR [org.hornetq.core.protocol.core.ServerSessionPacketHandler] Caught unexpected exception: java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) at java.util.AbstractList$Itr.next(AbstractList.java:343) at org.jboss.security.identity.plugins.SimpleRoleGroup.containsRole(SimpleRoleGroup.java:181) at org.jboss.security.plugins.JBossAuthorizationManager.doesRoleGroupHaveRole(JBossAuthorizationManager.java:254) at org.jboss.security.plugins.JBossAuthorizationManager.doesUserHaveRole(JBossAuthorizationManager.java:194) at org.jboss.security.plugins.auth.JaasSecurityManagerBase.doesUserHaveRole(JaasSecurityManagerBase.java:434) at org.jboss.security.plugins.JaasSecurityManager.doesUserHaveRole(JaasSecurityManager.java:195) at org.hornetq.integration.jboss.security.JBossASSecurityManager.validateUserAndRole(JBossASSecurityManager.java:110) This issue prevents to run TCK's JMS tests with security enabled in HornetQ. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (SECURITY-487) JBossMappingManager uses incorrect (misleading) Logger

by jaikiran pai (JIRA)

JBossMappingManager uses incorrect (misleading) Logger ------------------------------------------------------ Key: SECURITY-487 URL: https://jira.jboss.org/jira/browse/SECURITY-487 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss AS Trunk Reporter: jaikiran pai Assignee: Anil Saldhana Priority: Minor While debugging an issue (through logs), I realized after much fighting, that JBossMappingManager uses an incorrect logger: public class JBossMappingManager implements MappingManager { protected static final Logger log = Logger.getLogger(JBossSecurityContext.class); Notice that it's using the JBossSecurityContext.class as the logger name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2010