April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1265) Remove the test-configs/ejb-jacc/deploy/jbossweb-tomcat6.sar

by Anil Saldhana (JIRA)

Remove the test-configs/ejb-jacc/deploy/jbossweb-tomcat6.sar ------------------------------------------------------------ Key: EJBTHREE-1265 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1265 Project: EJB 3.0 Issue Type: Sub-task Components: core, Security Affects Versions: AS 5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: AS 5.0.0.CR1 Jacc is just a JaccAuthorizationModule in the security domain. No special container configuration needed. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1264) Remove the test-configs/ejb-jacc/deploy/ejb3-interceptors-aop.xml

by Anil Saldhana (JIRA)

Remove the test-configs/ejb-jacc/deploy/ejb3-interceptors-aop.xml ----------------------------------------------------------------- Key: EJBTHREE-1264 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1264 Project: EJB 3.0 Issue Type: Sub-task Components: Security Affects Versions: AS 5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: AS 5.0.0.CR1 We have to remove the ejb3-interceptors-aop.xml in the jacc test config. The reason is that Jacc is just an authorization module in the security domain. There is no special configuration needed. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-453) Reproduce app server thirdparty directory using maven repository

by Paul Gier (JIRA)

Reproduce app server thirdparty directory using maven repository ---------------------------------------------------------------- Key: JBBUILD-453 URL: http://jira.jboss.com/jira/browse/JBBUILD-453 Project: JBoss Build System Issue Type: Feature Request Components: JBossBuild, Maven Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - App Server As a step towards app server mavenization, we need to be able to reproduce the thirdparty directory including the libraries.ent file. This could be done using an assembly, or using a new maven plugin. -- 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

18 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1557) DynamicRulesTest.testDynamicFunction Fails under JDK 1.6

by Ming Jin (JIRA)

DynamicRulesTest.testDynamicFunction Fails under JDK 1.6 -------------------------------------------------------- Key: JBRULES-1557 URL: http://jira.jboss.com/jira/browse/JBRULES-1557 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 5.0.0-M1 Environment: JDK 1.6 Reporter: Ming Jin Assigned To: Ming Jin Priority: Minor Fix For: 5.0.0-M1 NoClassDefFoundError was thrown as the following: java.lang.NoClassDefFoundError: org/drools/test/AddFive It happened in testDynamicFunction, in a call of fireAllRules after the function has been removed, and then added again. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5357) AOP Inconsistences with JBossMessaging

by Clebert Suconic (JIRA)

AOP Inconsistences with JBossMessaging -------------------------------------- Key: JBAS-5357 URL: http://jira.jboss.com/jira/browse/JBAS-5357 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Clebert Suconic Priority: Blocker Fix For: JBossAS-5.0.0.CR1 AOP is not working with JBossMessaging. Any client class used on Server side (classes where we use aopc) will cause exceptions like this: SERVER 1 STDOUT: Caused by: java.lang.ClassNotFoundException: org.jboss.jms.client.delegate.JoinPoint_start_N_8025343665958530775_4$aop SERVER 1 STDOUT: at java.net.URLClassLoader$1.run(URLClassLoader.java:200) SERVER 1 STDOUT: at java.security.AccessController.doPrivileged(Native Method) SERVER 1 STDOUT: at java.net.URLClassLoader.findClass(URLClassLoader.java:188) SERVER 1 STDOUT: at java.lang.ClassLoader.loadClass(ClassLoader.java:306) SERVER 1 STDOUT: at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268) SERVER 1 STDOUT: at java.lang.ClassLoader.loadClass(ClassLoader.java:251) SERVER 1 STDOUT: at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:279) This specific message was introduced by JBAOP-500 (according to Flavia), so I've tried to use AOP CR1 and CR2 but I got all sort of different exceptions (on classNotFoundException). -- 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

18 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5403) Remove tx and txlock aspects from trunk/aspects once jboss-aspects is released

by Adrian Brock (JIRA)

Remove tx and txlock aspects from trunk/aspects once jboss-aspects is released ------------------------------------------------------------------------------ Key: JBAS-5403 URL: http://jira.jboss.com/jira/browse/JBAS-5403 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: AOP Reporter: Adrian Brock Assigned To: Andrew Lee Rubinger Fix For: JBossAS-5.0.0.CR1 -- 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

18 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-5201) EJB2 Entity with cache invalidation fails to deploy with NPE

by Brian Stansberry (JIRA)

EJB2 Entity with cache invalidation fails to deploy with NPE ------------------------------------------------------------ Key: JBAS-5201 URL: http://jira.jboss.com/jira/browse/JBAS-5201 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 An entity with cache invalidation configured will fail to deploy. This is the cause of the failing o.j.t.cluster.multicfg.ejb2.test.CacheInvalidationUnitTestCase. Example bean config: <entity> <ejb-name>cif_CachedEntityPK</ejb-name> <configuration-name>Standard CMP 2.x EntityBean with cache invalidation</configuration-name> <cache-invalidation>true</cache-invalidation> </entity> Failure: 2008-02-01 23:32:04,875 DEBUG [org.jboss.ejb.plugins.AbstractInstanceCache] Starting InvalidableEntityInstanceCache... 2008-02-01 23:32:04,878 DEBUG [org.jboss.ejb.EntityContainer] Starting failed jboss.j2ee:jndiName=local/cif_CachedEntityPK@8115601,service=EJB java.lang.NullPointerException at org.jboss.ejb.plugins.InvalidableEntityInstanceCache.start(InvalidableEntityInstanceCache.java:123) at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:352) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:167) at $Proxy5.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:255) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) at org.jboss.system.ServiceController.doChange(ServiceController.java:659) at org.jboss.system.ServiceController.start(ServiceController.java:431) ..... Problem is JBossEntityMetaData.getCacheInvalidationConfig() can return null if jobss.xml doesn't include a cache-invalidation-config element; in 4.x it wouldn't because a default value would be set. Likely solution is either 1) to add a JBossEntityMetaData.determineCacheInvalidationConfig() method or 2) just lazy create a default config in JBossEntityMetaData.getCacheInvalidationConfig(). The latter is a simpler solution; the former is used elsewhere when there is a need to merge metadata from a <container-configuration/>, but there is no cache invalidation configuration in <container-configuration/>. Either way, this will require a new jboss-metadata release. -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-16) Handle getHomeJndiName check in JBossSessionBeanMetaData.determineJndiName

by Scott M Stark (JIRA)

Handle getHomeJndiName check in JBossSessionBeanMetaData.determineJndiName -------------------------------------------------------------------------- Key: JBMETA-16 URL: http://jira.jboss.com/jira/browse/JBMETA-16 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta7 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: 1.0.0.Beta8 To avoid code like this below, we need to handle the handle the check for getHomeJndiName in determineJndiName else if( beanMD.isSession()) { JBossSessionBeanMetaData md = (JBossSessionBeanMetaData) beanMD; jndiName = md.getHomeJndiName(); if(jndiName == null) jndiName = md.determineJndiName(); } -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1229) @Resource(type=UserTransaction.class) on class level does not work

by Carlo de Wolf (JIRA)

@Resource(type=UserTransaction.class) on class level does not work ------------------------------------------------------------------ Key: EJBTHREE-1229 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1229 Project: EJB 3.0 Issue Type: Bug Components: core Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.CR1 -- 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

18 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1231) Only call bean.afterBegin if the tx.registerSynchronization succeeds

by Carlo de Wolf (JIRA)

Only call bean.afterBegin if the tx.registerSynchronization succeeds --------------------------------------------------------------------- Key: EJBTHREE-1231 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1231 Project: EJB 3.0 Issue Type: Bug Components: core Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.CR1 -- 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

18 years, 1 month

1
2
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 April 2008