March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-334) Add Before/After/Throwing to array interception

by Kabir Khan (JIRA)

Add Before/After/Throwing to array interception ----------------------------------------------- Key: JBAOP-334 URL: http://jira.jboss.com/jira/browse/JBAOP-334 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan -- 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, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-333) Make Array interception aware of scoped classloading

by Kabir Khan (JIRA)

Make Array interception aware of scoped classloading ---------------------------------------------------- Key: JBAOP-333 URL: http://jira.jboss.com/jira/browse/JBAOP-333 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-355) Improve aopc

by Kabir Khan (JIRA)

Improve aopc ------------ Key: JBAOP-355 URL: http://jira.jboss.com/jira/browse/JBAOP-355 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 Hey Kabir, Some hopefully more constructive inputs on aopc: 1) It appears that if any jboss-aop.xml is on the classpath defined by the "classpath" element, it gets applied. In the testsuite, I used a broad classpath, and it picks up a file with the same bindings as the file I name in aoppath. This causes aopc to fail; javaassist complains about seeing the same field twice. The workaround is to not specify anything in aoppath. But that's confusing. Seems to me that if aoppath is used, only bindings specified on the files in that path should be applied. 2) When trying to figure the above out, I look at the Reference Guide and then get really confused. classpath/classpathref -- simple enough. src -- isn't really source (i.e. .java) it's class files. It's basically a subset of classpath, right? This isn't spelled out clearly in the docs and the name of the element is confusing. aopclasspath -- Huh??? 3) Also, having "include" as a nested element within src would be more consistent with normal ant usage. Cheers, Brian Stansberry Lead, AS Clustering JBoss, a division of Red Hat Ph: 510-396-3864 skype: bstansberry -- 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, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAOP-345) Investigate chain overriding for inherited methods

by Kabir Khan (JIRA)

Investigate chain overriding for inherited methods -------------------------------------------------- Key: JBAOP-345 URL: http://jira.jboss.com/jira/browse/JBAOP-345 Project: JBoss AOP Issue Type: Feature Request 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

15 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAOP-335) Configure array interception with annotations

by Kabir Khan (JIRA)

Configure array interception with annotations --------------------------------------------- Key: JBAOP-335 URL: http://jira.jboss.com/jira/browse/JBAOP-335 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0.0.alpha3 equivalents for <arrayreplacement> and <arraybind> -- 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, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-416) Exclude tests testing new functionality from

by Kabir Khan (JIRA)

Exclude tests testing new functionality from --------------------------------------------- Key: JBAOP-416 URL: http://jira.jboss.com/jira/browse/JBAOP-416 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 1.5.6.GA, 2.0.0.alpha6 Once that is done, can you do me a favour? Kabir says: build.sh -f build-test-jdk50.xml clean-tests compile-test-classes precompiled-compatibility-tests Kabir says: It weaves with aop 1.5.5.GA and runs with AOP 2.0 Kabir says: some tests will fail, but most should pass Flávia says: Sure Kabir says: The tests that fail will hopefully be tests where we added some functionality in AOP 2.0 that does not exist in AOP 1.5.5.GA Kabir says: Ideally we need some way to exclude tests that are newer functionality than exists in the old version Kabir says: I'll add a JIRA for that Kabir says: since it would be good to get these automated Kabir says: I only remembered this since I spoke to Jason Green earlier about backward compatibility Flávia says: Yes. After all, we don't have a way of making new functionality work in JBAOP1.5 Kabir says: Thanks -- 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, 10 months

2
19
0 / 0

[JBoss JIRA] Created: (JBAOP-405) IllegalAccessException when accessing a private field through reflection after call to Field.SetAccessable()

by Jason Hill (JIRA)

IllegalAccessException when accessing a private field through reflection after call to Field.SetAccessable() ------------------------------------------------------------------------------------------------------------ Key: JBAOP-405 URL: http://jira.jboss.com/jira/browse/JBAOP-405 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Environment: AOP Standalone Reporter: Jason Hill When a call to java.lang.reflect.Field.set() is intercepted by org.jboss.aop.reflection.ReflectionAspect, it invokes the original interceptor chain for the field instead of allowing the set call to run. Since the Field.set() function is never invoked, any previous calls to Field.setAccessable() have no affect. -- 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, 10 months

3
16
0 / 0

[JBoss JIRA] Created: (JBAOP-446) Get loadtime weaving working with jboss embedded

by Kabir Khan (JIRA)

Get loadtime weaving working with jboss embedded ------------------------------------------------ Key: JBAOP-446 URL: http://jira.jboss.com/jira/browse/JBAOP-446 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0.0.GA -- 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, 10 months

1
9
0 / 0

[JBoss JIRA] Created: (JBAOP-422) Document advice matching involving generics

by Flavia Rainone (JIRA)

Document advice matching involving generics ------------------------------------------- Key: JBAOP-422 URL: http://jira.jboss.com/jira/browse/JBAOP-422 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha5 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.1.0.GA We should add text explainingg in details how advice matching on genadvisor mode when dealing with generics. We have three major scenarios: - there is generics only on the joinpoint being intercepted - there is generics only on the advice/aspect class making the interception - there is generics on both the joinpoint and advice/aspect All three scenarios have to be explained in the documentation. -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAOP-468) Add ManagedOperation metadata to AOP

by Kabir Khan (JIRA)

Add ManagedOperation metadata to AOP ------------------------------------ Key: JBAOP-468 URL: http://jira.jboss.com/jira/browse/JBAOP-468 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.GA Folllowing discussions in Neuchatel, what this will involve from our end is to have the full featureset of -aop.xml doable in a -beans.xml resulting in managed beans implementing everything -- 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, 10 months

1
13
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2009