November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-380) MC chooses the wrong constructor to build a bean from metadata

by Carlo de Wolf (JIRA)

MC chooses the wrong constructor to build a bean from metadata -------------------------------------------------------------- Key: JBMICROCONT-380 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-380 Project: JBoss Microcontainer Issue Type: Bug Affects Versions: JBossMC.2.0.0.CR5 Reporter: Carlo de Wolf Priority: Critical Given the following piece of xml, MC can pick the wrong constructor to instantiate BeanMetaDataDeployer: <bean name="BeanMetaDataDeployer" class="org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer"> <constructor><parameter><inject bean="jboss.kernel:service=Kernel"/></parameter></constructor> </bean> java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[org.jboss.dependency.spi.Controller] actual=[org.jboss.kernel.Kernel] at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395) at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:153) at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:106) at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:80) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.createTarget(AOPConstructorJoinpoint.java:276) at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:97) at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241) ... -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1122) *MessageCountersAsHTML LastAdd uses wrong value

by Aslak (JIRA)

*MessageCountersAsHTML LastAdd uses wrong value ----------------------------------------------- Key: JBMESSAGING-1122 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1122 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Reporter: Aslak Assigned To: Tim Fox ServerPeer.listMessageCountersAsHTML() and QueueService.listMessageCounterAsHTML() displays the column "Las Add", but uses the message counters last update value. -- 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

15 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-6145) Upgrade to JSF 1.2_10

by Stan Silvert (JIRA)

Upgrade to JSF 1.2_10 --------------------- Key: JBAS-6145 URL: https://jira.jboss.org/jira/browse/JBAS-6145 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JSF Affects Versions: JBossAS-5.0.0.CR2 Reporter: Stan Silvert Assignee: Stan Silvert JSF 1.2_10 has some performance enhancements and also fixes JBSEAM-3363/JBIDE-2190. There are workarounds for the issues above, but it is VERY desirable to have JSF 1.2_10 in GA if JSF 1.2_10 is released in time. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBNAME-21) Add ability to inject the naming SecurityManager

by Scott M Stark (JIRA)

Add ability to inject the naming SecurityManager ------------------------------------------------ Key: JBNAME-21 URL: https://jira.jboss.org/jira/browse/JBNAME-21 Project: JBoss Naming Issue Type: Feature Request Components: jnpserver Affects Versions: 5.0.0.CR3 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: 5.0.0.GA It would be nice to be able to inject a SecurityManager instance rather than having to rely on the jvm System.getSecurityManager() value. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6025) Upgrade to jnp-client/server 5.0.0.GA

by Dimitris Andreadis (JIRA)

Upgrade to jnp-client/server 5.0.0.GA ------------------------------------- Key: JBAS-6025 URL: https://jira.jboss.org/jira/browse/JBAS-6025 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Naming Reporter: Dimitris Andreadis Assignee: Scott M Stark Priority: Critical Fix For: JBossAS-5.0.0.GA Upgrade to a final version for AS5. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1571) Timer fails to access a protected EJB first time...

by Mohammad Kargar (JIRA)

Timer fails to access a protected EJB first time... --------------------------------------------------- Key: EJBTHREE-1571 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1571 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Environment: OS: Test on Windows XP and Linux Reporter: Mohammad Kargar I have two ejb modules (say module-a and module-b). All ejbs in module-a are protected and unauthenticatedIdentity of the related application-policy has been set to a valid user. EJBs under module-b are not protected and there is a timer ejb in this module that invokes another ejb from module-a. The strange thing is that the Timeout method fails to access the protected ejb always for the first attempt due to an authentication failure, but the second attempt (timer service waits for few milliseconds and tries again) works fine! -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBNAME-19) Allow the Naming instance to be injected into the LocalOnlyContextFactory

by Scott M Stark (JIRA)

Allow the Naming instance to be injected into the LocalOnlyContextFactory ------------------------------------------------------------------------- Key: JBNAME-19 URL: https://jira.jboss.org/jira/browse/JBNAME-19 Project: JBoss Naming Issue Type: Feature Request Components: jnp-client Affects Versions: 5.0.0.CR3 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: 5.0.0.GA We should allow the Naming instance to be injected into the LocalOnlyContextFactory so that it can operate with a Naming instance other than the JVM global instance set on the NamingContext. -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBNAME-20) Split out ObjectFactory implementation from LocalOnlyContextFactory

by Scott M Stark (JIRA)

Split out ObjectFactory implementation from LocalOnlyContextFactory ------------------------------------------------------------------- Key: JBNAME-20 URL: https://jira.jboss.org/jira/browse/JBNAME-20 Project: JBoss Naming Issue Type: Task Components: jnp-client Affects Versions: 5.0.0.CR3 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: 5.0.0.GA The LocalOnlyContextFactory currently implements a URL content ObjectFactory for some reason: // ObjectFactory implementation ---------------------------------- public Object getObjectInstance(Object obj, Name name, Context nameCtx, Hashtable environment) throws Exception { Context ctx = getInitialContext(environment); Reference ref = (Reference)obj; return ctx.lookup((String)ref.get("URL").getContent()); } This should be in a separate URLContentObjectFactory bean -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6163) JACC: Look at the cmp2-audit.jar for security domain

by Anil Saldhana (JIRA)

JACC: Look at the cmp2-audit.jar for security domain ---------------------------------------------------- Key: JBAS-6163 URL: https://jira.jboss.org/jira/browse/JBAS-6163 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.CR2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: JBossAS-5.0.1.CR1 The trace log for jacc tests involving the CMP2 audit jar are showing trace as follows: ============= 2008-11-05 10:50:57,320 TRACE [org.jboss.security.plugins.identitytrust.JBossIdentityTrustManager] (WorkerThread#0[127.0.0.1:41997]) Trust Exception: org.jboss.security.identitytrust.IdentityTrustException: java.lang.IllegalStateException: ApplicationPolicy not found for CLIENT_LOGIN_MODULE at org.jboss.security.identitytrust.JBossIdentityTrustContext.isTrusted(JBossIdentityTrustContext.java:65) at org.jboss.security.plugins.identitytrust.JBossIdentityTrustManager.isTrusted(JBossIdentityTrustManager.java:72) at org.jboss.security.javaee.EJBAuthenticationHelper.isTrusted(EJBAuthenticationHelper.jav ============ The IdentityTrust feature should be disabled and the correct security domain should have been taken. -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-439) Abiltity to change priority of messages in a queue/durable sub

by Tim Fox (JIRA)

Abiltity to change priority of messages in a queue/durable sub -------------------------------------------------------------- Key: JBMESSAGING-439 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-439 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: 1.0.2 A "nice to have" would be to allow the priority of messages in a destination to be changed by an administrator - this should be available via the normal management interfaces. -- 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

15 years, 6 months

5
5
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