November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-125) javax.ejb.Singleton annotation

by Alexey Loubyansky (JIRA)

javax.ejb.Singleton annotation ------------------------------ Key: JBMETA-125 URL: https://jira.jboss.org/jira/browse/JBMETA-125 Project: JBoss Metadata Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 1.0.0.CR2 @Target(TYPE) @Retention(RUNTIME) public @interface Singleton { String description() default ""; /** * A product specific name (in JBoss the global JNDI name) that this * session bean should be mapped to. Application servers are not * required to support any particular form or type of mapped name, * nor the ability to use mapped names. The mapped name is product-dependent * and often installation-dependent. No use of a mapped name is portable. */ String mappedName() default ""; /** * The ejb-name of this bean. */ String name() default ""; } -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMETA-124) javax.ejb.Startup annotation

by Alexey Loubyansky (JIRA)

javax.ejb.Startup annotation ---------------------------- Key: JBMETA-124 URL: https://jira.jboss.org/jira/browse/JBMETA-124 Project: JBoss Metadata Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 1.0.0.CR2 Support for @Startup -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMETA-123) support annotations for singleton session beans (ejb3.1, chaper 4.8)

by Alexey Loubyansky (JIRA)

support annotations for singleton session beans (ejb3.1, chaper 4.8) -------------------------------------------------------------------- Key: JBMETA-123 URL: https://jira.jboss.org/jira/browse/JBMETA-123 Project: JBoss Metadata Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 1.0.0.CR2 There are a few annotations that should be added to support singleton session beans. -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-6065) Upgrade jgroups

by Dimitris Andreadis (JIRA)

Upgrade jgroups --------------- Key: JBAS-6065 URL: https://jira.jboss.org/jira/browse/JBAS-6065 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Clustering Reporter: Dimitris Andreadis Assignee: Brian Stansberry Priority: Critical Fix For: JBossAS-5.0.0.GA I believe Brian wants to upgrade the jgroups stack for AS5 GA. -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1448) SecurityAspect->check() needs a privileged block

by Anil Saldhana (JIRA)

SecurityAspect->check() needs a privileged block ------------------------------------------------ Key: JBMESSAGING-1448 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1448 Project: JBoss Messaging Issue Type: Sub-task Reporter: Anil Saldhana Assignee: Clebert Suconic Caused by: java.security.AccessControlException: access denied (javax.management.MBeanPermission org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore#getSecurityMetadata[jboss.messaging:service=SecurityStore] invoke) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at org.jboss.mx.server.MBeanServerImpl.checkMBeanPermission(MBeanServerImpl.java:1735) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:663) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy89.getSecurityMetadata(Unknown Source) at org.jboss.jms.server.container.SecurityAspect.check(SecurityAspect.java:284) at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:112) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122) At the following line: at org.jboss.jms.server.container.SecurityAspect.check(SecurityAspect.java:284) -- 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

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1447) ServerConnectionFactoryEndpoint is missing a privileged block

by Anil Saldhana (JIRA)

ServerConnectionFactoryEndpoint is missing a privileged block ------------------------------------------------------------- Key: JBMESSAGING-1447 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1447 Project: JBoss Messaging Issue Type: Sub-task Reporter: Anil Saldhana Assignee: Clebert Suconic ======================================================================================= java.security.AccessControlException: access denied (javax.management.MBeanPermission org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore#authenticate[jboss.messaging:service=SecurityStore] invoke) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at org.jboss.mx.server.MBeanServerImpl.checkMBeanPermission(MBeanServerImpl.java:1735) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:663) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy89.authenticate(Unknown Source) at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:225) at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:165) at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108) at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java) at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) ============================================================================== Line 225 which calls authenticate on the proxy should go in a privileged block. -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1446) ClientAOPStackLoader is missing a privileged block for TCL setting

by Anil Saldhana (JIRA)

ClientAOPStackLoader is missing a privileged block for TCL setting ------------------------------------------------------------------ Key: JBMESSAGING-1446 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1446 Project: JBoss Messaging Issue Type: Sub-task Reporter: Anil Saldhana Assignee: Tim Fox ================================================================ 2008-11-07 15:42:43,532 ERROR [org.jboss.jms.client.JBossConnectionFactory] (WorkerThread#2[127.0.0.1:52424]) Failed to download and/or install client side AOPstack java.security.AccessControlException: access denied (java.lang.RuntimePermission setContextClassLoader) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at java.lang.Thread.setContextClassLoader(Thread.java:1306) at org.jboss.jms.client.ClientAOPStackLoader.load(ClientAOPStackLoader.java:83) at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:192) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95) at org.jboss.test.cts.jms.MsgSender.init(MsgSender.java:62) at org.jboss.test.cts.jms.MsgSender.sendMsg(MsgSender.java:94) at org.jboss.test.cts.ejb.CtsBmpBean.sendMsg(CtsBmpBean.java:664) at org.jboss.test.cts.ejb.CtsBmpBean.ejbCreate(CtsBmpBean.java:93) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ===================================================================== http://anonsvn.jboss.org/repos/messaging/branches/Branch_1_4/src/main/org... The following line: // This was done because of some weird behavior of AOP & classLoading // http://jira.jboss.org/jira/browse/JBMESSAGING-980 Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader()); This sensitive operation should go in a privileged block. -- 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

15 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1453) ClientAOPStackLoader needs privileged block to get TCL

by Anil Saldhana (JIRA)

ClientAOPStackLoader needs privileged block to get TCL ------------------------------------------------------ Key: JBMESSAGING-1453 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1453 Project: JBoss Messaging Issue Type: Sub-task Reporter: Anil Saldhana Assignee: Clebert Suconic ================================ java.security.AccessControlException: access denied (java.lang.RuntimePermission getClassLoader) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:264) at java.security.AccessController.checkPermission(AccessController.java:427) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at java.lang.Thread.getContextClassLoader(Thread.java:1276) at org.jboss.jms.client.ClientAOPStackLoader.load(ClientAOPStackLoader.java:67) at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:192) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101) at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95) at org.jboss.test.cts.jms.MsgSender.init(MsgSender.java:62) at org.jboss.test.cts.jms.MsgSender.sendMsg(MsgSender.java:94) at org.jboss.test.cts.ejb.CtsBmpBean.sendMsg(CtsBmpBean.java:664) at org.jboss.test.cts.ejb.CtsBmpBean.setEntityContext(CtsBmpBean.java:512) ===================================================== You need a priv block in ClientAOPStackLoader where you get TCL -- 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

15 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBREM-1026) Add service metadata

by David Lloyd (JIRA)

Add service metadata -------------------- Key: JBREM-1026 URL: https://jira.jboss.org/jira/browse/JBREM-1026 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 api Reporter: David Lloyd Fix For: 3.0.0-M3 A RequestHandlerSource (aka a forwarded service) needs methods to query static metadata, such as: 1) The presence or absence of ordering guarantees across the total path 2) Security information about the total path (encryption strength for example) 3) Path information (like a traceroute, for cost as well as diagnostic information; could include link cost, transport type & version, etc) 4) Possibly authentication information about the total path It should be possible to add new metadata types later on without interfering with backwards compatibility. So lack of a given metadata type must be considered to be possibly indicative of an older version along the path. -- 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

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1589) Add a mechanism to apply runtime Mixin

by Andrew Lee Rubinger (JIRA)

Add a mechanism to apply runtime Mixin -------------------------------------- Key: EJBTHREE-1589 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1589 Project: EJB 3.0 Issue Type: Task Components: common Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 1.0.0-Beta7 We need support to add interfaces and handling to an existing arbitrary service. This will pave the way to tack on additional processing abilities to EJB3 Proxy, like Async. -- 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

15 years, 7 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008