October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAOP-193) Wrong casting of run-as identity

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-193?page=all ] Kabir Khan updated JBAOP-193: ----------------------------- Fix Version/s: 2.0.0.alpha3 (was: 2.0.0.alpha2) > Wrong casting of run-as identity > -------------------------------- > > Key: JBAOP-193 > URL: http://jira.jboss.com/jira/browse/JBAOP-193 > Project: JBoss AOP > Issue Type: Bug > Affects Versions: 1.3.4 > Reporter: Kabir Khan > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha3 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-6) Compile time reweaving

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-6?page=all ] Kabir Khan updated JBAOP-6: --------------------------- Fix Version/s: 2.0.0.alpha3 (was: 2.0.0.alpha2) > Compile time reweaving > ---------------------- > > Key: JBAOP-6 > URL: http://jira.jboss.com/jira/browse/JBAOP-6 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: 2.0.0.alpha3 > > > Support for compile time reweaving. Currently AOPC ignores a class that implements Advised -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-226) Memory leaks (advanced)

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-226?page=all ] Kabir Khan updated JBAOP-226: ----------------------------- Fix Version/s: 2.0.0.alpha3 (was: 2.0.0.alpha2) > Memory leaks (advanced) > ----------------------- > > Key: JBAOP-226 > URL: http://jira.jboss.com/jira/browse/JBAOP-226 > Project: JBoss AOP > Issue Type: Task > Affects Versions: 1.3.6 > Reporter: Kabir Khan > Fix For: 2.0.0.alpha3 > > > Need to resolve memory leaks for > * AOP with generated weaving (domain per class) > * AOP in scoped deployments (domain per scoped classloader) > * standalone jboss-aop.xml files deployed in jboss (we will probably need to make the advisor clear itself from the woven class if "empty" following a rebind, and have something in the woven code to repopulate the classadvisor when executing the joinpoints) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-195) Error running ArgsTestCase in Eclipse

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-195?page=all ] Kabir Khan updated JBAOP-195: ----------------------------- Fix Version/s: 2.0.0.alpha3 (was: 2.0.0.alpha2) > Error running ArgsTestCase in Eclipse > ------------------------------------- > > Key: JBAOP-195 > URL: http://jira.jboss.com/jira/browse/JBAOP-195 > Project: JBoss AOP > Issue Type: Task > Reporter: Kabir Khan > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha3 > > > This is when running with generated advisors. It works fine when running from command-line on Windows, but causes an error when running/debugging in Eclipse. All other tests work fine in both places. My main concern is that this error in Eclipse might show up on other platforms > java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.aop.JoinPoint in org/jboss/aop/joinpoint.java > at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:174) > at org.jboss.test.aop.args.POJO$POJOAdvisor.bunchArgs_N_5735936556171587907(POJO$POJOAdvisor.java) > at org.jboss.test.aop.args.POJO.bunchArgs(POJO.java) > at org.jboss.test.aop.args.ArgsTestCase.testBench(ArgsTestCase.java:62) > 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 junit.framework.TestCase.runTest(TestCase.java:154) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Caused by: java.lang.RuntimeException: org.jboss.aop.JoinPoint in org/jboss/aop/joinpoint.java > at javassist.CtClassType.getClassFile2(CtClassType.java:194) > at javassist.CtClassType.prune(CtClassType.java:1046) > at org.jboss.aop.AOPClassPool.cacheCtClass(AOPClassPool.java:138) > at javassist.ClassPool.get0(ClassPool.java:405) > at javassist.ClassPool.get(ClassPool.java:371) > at javassist.compiler.MemberResolver.lookupClass0(MemberResolver.java:408) > at javassist.compiler.MemberResolver.lookupClass(MemberResolver.java:372) > at javassist.compiler.MemberResolver.lookupFieldByJvmName2(MemberResolver.java:258) > at javassist.compiler.TypeChecker.fieldAccess(TypeChecker.java:791) > at javassist.compiler.TypeChecker.atFieldRead(TypeChecker.java:719) > at javassist.compiler.TypeChecker.atExpr(TypeChecker.java:521) > at javassist.compiler.ast.Expr.accept(Expr.java:67) > at javassist.compiler.TypeChecker.atCallExpr(TypeChecker.java:603) > at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:156) > at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45) > at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:235) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:323) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:344) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.MemberCodeGen.atTryStmnt(MemberCodeGen.java:140) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:360) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:344) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.CodeGen.atSwitchStmnt(CodeGen.java:533) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:362) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:344) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.MemberCodeGen.atTryStmnt(MemberCodeGen.java:140) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:360) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.CodeGen.atStmnt(CodeGen.java:344) > at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49) > at javassist.compiler.CodeGen.atMethodBody(CodeGen.java:285) > at javassist.compiler.Javac.compileBody(Javac.java:212) > at javassist.CtBehavior.setBody(CtBehavior.java:221) > at javassist.CtBehavior.setBody(CtBehavior.java:196) > at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:654) > at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:234) > at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:164) > ... 20 more -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-246) Optimize advisor.resolveAnnotation(field, org.jboss.cache.aop.annotation.Serializable.class)

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-246?page=all ] Kabir Khan updated JBAOP-246: ----------------------------- Fix Version/s: 2.0.0.alpha3 (was: 2.0.0.alpha2) > Optimize advisor.resolveAnnotation(field, org.jboss.cache.aop.annotation.Serializable.class) > --------------------------------------------------------------------------------------------- > > Key: JBAOP-246 > URL: http://jira.jboss.com/jira/browse/JBAOP-246 > Project: JBoss AOP > Issue Type: Task > Reporter: Ben Wang > Fix For: 2.0.0.alpha3 > > > I am running PojoCache benchmark and I have noticed this statement is expensive: > Object obj = advisor.resolveAnnotation(field, org.jboss.cache.aop.annotation.Serializable.class); > of which I think it should not. > I am runnign JDK5.0 but with 1.4 lib. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-48) serialization and Aspect scoping

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-48?page=all ] Kabir Khan updated JBAOP-48: ---------------------------- Fix Version/s: 2.0.0.alpha3 (was: 2.0.0.alpha2) > serialization and Aspect scoping > -------------------------------- > > Key: JBAOP-48 > URL: http://jira.jboss.com/jira/browse/JBAOP-48 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Assigned To: Bill Burke > Fix For: 2.0.0.alpha3 > > > Resolve rules when aspects are serialized that are attached on a per-instance basis. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-87) Add @Depends to annotations that define dependencies

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-87?page=all ] Kabir Khan updated JBAOP-87: ---------------------------- Fix Version/s: 2.0.0.alpha2 > Add @Depends to annotations that define dependencies > ---------------------------------------------------- > > Key: JBAOP-87 > URL: http://jira.jboss.com/jira/browse/JBAOP-87 > Project: JBoss AOP > Issue Type: Task > Components: Aspect Library > Reporter: Adrian Brock > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha2 > > > Need to create an "@Depends" annotation that defines which annotations > introduce dependenecies. > Need to annotate other annotations with the @Depends annotation where relevent. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-233) Fix the serialization test for aop proxies

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-233?page=all ] Kabir Khan updated JBAOP-233: ----------------------------- Fix Version/s: 2.0.0.alpha2 Assignee: Kabir Khan > Fix the serialization test for aop proxies > ------------------------------------------ > > Key: JBAOP-233 > URL: http://jira.jboss.com/jira/browse/JBAOP-233 > Project: JBoss AOP > Issue Type: Sub-task > Reporter: Adrian Brock > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha2 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-240) Test AOP/MC integration with security manager

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-240?page=all ] Kabir Khan updated JBAOP-240: ----------------------------- Fix Version/s: 2.0.0.alpha2 Assignee: Kabir Khan > Test AOP/MC integration with security manager > --------------------------------------------- > > Key: JBAOP-240 > URL: http://jira.jboss.com/jira/browse/JBAOP-240 > Project: JBoss AOP > Issue Type: Sub-task > Reporter: Adrian Brock > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha2 > > > The AOP/MC integration needs to have the tests working with the > java SecurityManager enabled. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-227) Test the proxy/advisor decision tree in the AOPJoinpointFactory

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-227?page=all ] Kabir Khan updated JBAOP-227: ----------------------------- Fix Version/s: 2.0.0.alpha2 Assignee: Kabir Khan > Test the proxy/advisor decision tree in the AOPJoinpointFactory > --------------------------------------------------------------- > > Key: JBAOP-227 > URL: http://jira.jboss.com/jira/browse/JBAOP-227 > Project: JBoss AOP > Issue Type: Sub-task > Reporter: Adrian Brock > Assigned To: Kabir Khan > Fix For: 2.0.0.alpha2 > > > The decision tree described on the attached forums thread needs fully testing. > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=81869 > There are already some basic tests in aop-mc-int > see org.jboss.test.microcontainer.advisor.test.* -- 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, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006