February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAOP-255) Instanceof expressions and methods overriding with a different return type

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-255?page=all ] Kabir Khan updated JBAOP-255: ----------------------------- Fix Version/s: 2.0.0.alpha4 (was: 2.0.0.alpha3) > Instanceof expressions and methods overriding with a different return type > -------------------------------------------------------------------------- > > Key: JBAOP-255 > URL: http://jira.jboss.com/jira/browse/JBAOP-255 > Project: JBoss AOP > Issue Type: Bug > Affects Versions: 1.5.0.GA > Reporter: Kabir Khan > Fix For: 2.0.0.alpha4 > > -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-261) Benchmark and optimize resolveAnnotation call in both JDK1.4 and 1.5

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-261?page=all ] Kabir Khan updated JBAOP-261: ----------------------------- Fix Version/s: 2.0.0.alpha4 (was: 2.0.0.alpha3) > Benchmark and optimize resolveAnnotation call in both JDK1.4 and 1.5 > -------------------------------------------------------------------- > > Key: JBAOP-261 > URL: http://jira.jboss.com/jira/browse/JBAOP-261 > Project: JBoss AOP > Issue Type: Task > Reporter: Ben Wang > Fix For: 2.0.0.alpha4 > > > In the PojoCache benchmark, I have found that resolveAnnotation for field can be quite expensive (at least for JDK1.4). It will be nice if we can benchmark it and then even optimize it. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-268) Get jdk15.dynamic tests working with generated advisors

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-268?page=all ] Kabir Khan updated JBAOP-268: ----------------------------- Fix Version/s: 2.0.0.alpha4 (was: 2.0.0.alpha3) > Get jdk15.dynamic tests working with generated advisors > ------------------------------------------------------- > > Key: JBAOP-268 > URL: http://jira.jboss.com/jira/browse/JBAOP-268 > Project: JBoss AOP > Issue Type: Sub-task > Reporter: Kabir Khan > Assigned To: Flavia Rainone > Fix For: 2.0.0.alpha4 > > > Some classloader stuff is going on with these tests causing them not to work with generated advisors - they are currently set up to use ClassicInstrumentor -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-320) Arg annotation with number specifying the adice argument number

by Flavia Rainone (JIRA)

Arg annotation with number specifying the adice argument number --------------------------------------------------------------- Key: JBAOP-320 URL: http://jira.jboss.com/jira/browse/JBAOP-320 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone Assigned To: Flavia Rainone Priority: Minor Add a parameter to the annotation @Arg So that it receives the advice method argument number. This is for use in cases like: public void interceptedMethod(String original, String copy) { } And you want to receive the value of copy, not of original, on your advice: public void myAdvice(@Arg String copy) { } -- 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

19 years, 2 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAOP-344) Add JBoss EULA to aop 2.0

by Kabir Khan (JIRA)

Add JBoss EULA to aop 2.0 ------------------------- Key: JBAOP-344 URL: http://jira.jboss.com/jira/browse/JBAOP-344 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAOP-37) Before, After, After Throwing support

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-37?page=all ] Kabir Khan updated JBAOP-37: ---------------------------- Fix Version/s: 2.0.0.alpha4 (was: 2.0.0.alpha3) Assignee: (was: Flavia Rainone) > Before, After, After Throwing support > ------------------------------------- > > Key: JBAOP-37 > URL: http://jira.jboss.com/jira/browse/JBAOP-37 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 2.0.0.alpha1 > Reporter: Bill Burke > Fix For: 2.0.0.alpha4 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > This should be optimized as well. I've done a non-CVS-checked-in prototype of this. > Feature Details: > To use this feature, one should use the xml tags 'before', 'after' and 'throwing'. > The signature of these advices should take any annotated arguments (annotation rules follow) and 'after' can return a value in order to overwrite/replace the intercepted join point returned value. > Besides, to continue using the advice around, the user should just continue using the 'advice' xml tag. > Around advices should either stick to the signature > Object [advice_name](Invocation invocation) > Or they can now use annotated parameters, as in 'before', 'after' and 'throwing' > The parameters can be annotated with JoinPoint, Invocation, Return, Throwable, Arg, Args, Callee, Caller and Target. > Parameter Annotation Rules: > Except for around default signature, all parameters must be annotated with one of the annotations defined in package org.jboss.aop.advice. We have annotations that are allowed only for specific types of join points, and we have annotations that are allowed only for specific types of advices. > These annotations are allowed depending on the advice type: > - JoinPoint: Before, After, Throwing > - Invocation: Around > - Return: Around, After > - Throwable: Throwing > These annotations are allowed depending on the join point type: > - Callee: call join points > - Caller: call join points > - Target: every non-static join point that is not a call > Finally, we have the mutually exclusive annotations Arg and Args. Both can always be used (but not on the same advice method). The first one must annotate every advice parameter whose value is the value of a join point argument. The second one annotates parameters of type Object[] that must receive all join point arguments values. > Advice Matching Rules > Every Arg parameter is bound to a join point argument of the same type. If there is more than one join point argument with the requested type, then the Arg parameter will be bound to the first join point argument that has not been bound yet. > When there are overloaded advice methods, JBoss AOP will use a priority order to pick the best match. The advice method with the most suitable type of the highest priority annotated parameter type is chosen. > The increasing priority order of arguments is: Arg/Args, Return/Throwable, Target/Callee/Caller , JoinPoint/Invocation. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-354) PerVMAdvice depends on optimized classes

by Flavia Rainone * (JIRA)

PerVMAdvice depends on optimized classes ---------------------------------------- Key: JBAOP-354 URL: http://jira.jboss.com/jira/browse/JBAOP-354 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Flavia Rainone * Assigned To: Flavia Rainone * Fix For: 2.1.0.GA, 1.5.4.GA, 2.0.0.alpha3 On unoptimized instrumentation, PerVMAdvice throws a CannotCompileException, because it refers to an optimized invocation (this class is generated only on optimized instrumentation). To reproduce this bug, run args tests on unoptimized instrumentation. -- 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

19 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAOP-352) Integrate Args with Arg

by Flavia Rainone * (JIRA)

Integrate Args with Arg ----------------------- Key: JBAOP-352 URL: http://jira.jboss.com/jira/browse/JBAOP-352 Project: JBoss AOP Issue Type: Sub-task Affects Versions: 2.1.0.GA, 2.0.0.alpha3 Reporter: Flavia Rainone * Changes in the arguments array need to be reflected on both the Arg parameter annotated values, and the dispatch method. -- 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

19 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4138) Update jfreechart to 0.9.21

by Fernando Nasser (JIRA)

Update jfreechart to 0.9.21 --------------------------- Key: JBAS-4138 URL: http://jira.jboss.com/jira/browse/JBAS-4138 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Fernando Nasser Fix For: JBossAS-4.2.0.CR1 minor upgrade from 0.9.20, but the included jcommon goes from 0.6.4 to 0.9.7 -- 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAOP-353) NPE on _getInstanceAdvisor (inside constructor joinpoints)

by Flavia Rainone * (JIRA)

NPE on _getInstanceAdvisor (inside constructor joinpoints) ---------------------------------------------------------- Key: JBAOP-353 URL: http://jira.jboss.com/jira/browse/JBAOP-353 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Flavia Rainone * Assigned To: Flavia Rainone * Fix For: 2.1.0.GA, 1.5.4.GA, 2.0.0.alpha3 The problem happens when the constructor sets a field and JBoss AOP intercepts that field write joinpoint. Once this happens, the field write wrapper is called. Inside the warpper, the getInstanceAdvisor method is executed and throws NullPointerException. -- 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

19 years, 2 months

3
4
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 February 2007