[JBoss JIRA] Created: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[JBoss JIRA] (JBAOP-814) When the...

[JBoss JIRA] (JBAOP-812)...

Flavia Rainone (JIRA)

Tuesday, 15 June 2010 Tue, 15 Jun '10

1:33 p.m.

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://jira.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6 CP01, 2.1.9.GA, 2.2.1.GA Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(). The correct is to create the advisor by calling AspectManager.instance(WovenClass.class).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Flavia Rainone (JIRA)

Tuesday, 15 June Tue, 15 Jun

2:11 p.m.

New subject: [JBoss JIRA] Updated: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://jira.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.sy... ] Flavia Rainone updated JBAOP-796: --------------------------------- Description: Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance. was: Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(). The correct is to create the advisor by calling AspectManager.instance(WovenClass.class).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://jira.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6 CP01, 2.1.9.GA, 2.2.1.GA Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Flavia Rainone (JIRA)

2:16 p.m.

New subject: [JBoss JIRA] Commented: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://jira.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6 CP01, 2.1.9.GA, 2.2.1.GA Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

Flavia Rainone (JIRA)

2:17 p.m.

New subject: [JBoss JIRA] Updated: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://jira.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.sy... ] Flavia Rainone updated JBAOP-796: --------------------------------- Comment: was deleted (was: The same fix needs to be applied to line 419 of GeneratedClassAdvisor, for generated advisor weaving.)

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://jira.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6 CP01, 2.1.9.GA, 2.2.1.GA Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

Flavia Rainone (JIRA)

2:19 p.m.

New subject: [JBoss JIRA] Commented: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://jira.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.sy... ] Flavia Rainone commented on JBAOP-796: -------------------------------------- The same fix needs to be applied to line 419 of GeneratedAdvisorInstrumentor: //This will be called when a class instantiates its advisor CtConstructor ctor = CtNewConstructor.defaultConstructor(genadvisor); ctor.setBody( "{" + " super(\"" + clazz.getName() + "\"); " + " initialise(org.jboss.aop.AspectManager.instance());" + <-- line 419 "}"); genadvisor.addConstructor(ctor);

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://jira.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6 CP01, 2.1.9.GA, 2.2.1.GA Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

Kabir Khan (JIRA)

Thursday, 19 August Thu, 19 Aug

1:01 p.m.

New subject: [JBoss JIRA] Updated: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://jira.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.sy... ] Kabir Khan updated JBAOP-796: ----------------------------- Fix Version/s: 2.1.6.CP02 (was: 2.1.6 CP01)

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://jira.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6.CP02, 2.1.9.GA, 2.2.1.GA Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

Kabir Khan (JIRA)

Friday, 17 December Fri, 17 Dec

8:48 a.m.

New subject: [JBoss JIRA] Updated: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://issues.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.... ] Kabir Khan updated JBAOP-796: ----------------------------- Fix Version/s: Branch_2_2 (was: 2.2.1.GA)

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://issues.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6.CP02, 2.1.9.GA, Branch_2_2 Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

-- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Kabir Khan (JIRA)

Thursday, 11 August Thu, 11 Aug

12:02 p.m.

New subject: [JBoss JIRA] Updated: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://issues.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.... ] Kabir Khan updated JBAOP-796: ----------------------------- Fix Version/s: 2.1.6.CP03 (was: 2.1.6.CP02)

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://issues.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6.CP03, 2.1.9.GA, Branch_2_2 Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Kabir Khan (JIRA)

Friday, 12 August Fri, 12 Aug

9:33 a.m.

New subject: [JBoss JIRA] Updated: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://issues.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.... ] Kabir Khan updated JBAOP-796: ----------------------------- Fix Version/s: 2.1.6.CP04 (was: 2.1.6.CP03)

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://issues.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6.CP04, 2.1.9.GA, Branch_2_2 Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

-- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

Kabir Khan (JIRA)

Friday, 30 November Fri, 30 Nov

11:48 a.m.

New subject: [JBoss JIRA] (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://issues.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.... ] Kabir Khan closed JBAOP-796. ----------------------------

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://issues.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.6.CP03, 2.1.9.GA, Branch_2_2 Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

-- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

Kabir Khan (JIRA)

11:48 a.m.

New subject: [JBoss JIRA] (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader

[ https://issues.jboss.org/browse/JBAOP-796?page=com.atlassian.jira.plugin.... ] Kabir Khan resolved JBAOP-796. ------------------------------ Fix Version/s: 2.1.6.CP03 (was: 2.1.6.CP04) Resolution: Done

...

Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader ------------------------------------------------------------------------------------------------ Key: JBAOP-796 URL: https://issues.jboss.org/browse/JBAOP-796 Project: JBoss AOP Issue Type: Bug Security Level: Public(Everyone can see) Affects Versions: 2.1.9.Alpha1 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 2.1.9.GA, Branch_2_2, 2.1.6.CP03 Currently, an Advisor is created by calling AspectManager.instance().getAdvisor(WovenClass.class). The correct is to create the advisor by calling something equivalent to AspectManager.instance(WovenClass.class.getClassLoader()).getAdvisor(WovenClass.class). Otherwise, the Advisor will be created as part of the AspectManager/Domain corresponding to the current context class loader: public static synchronized AspectManager instance() { return instance(Thread.currentThread().getContextClassLoader()); } In the JBoss AS environment, if the woven class is loaded during an archive deployment, this is equivalent to say that the Advisor will be erroneously created by the domain of the current deployment, instead of being created by the appropriate AspectManager/Domain instance.

4163

days inactive

5062

days old

jboss-jira@lists.jboss.org

Manage subscription

10 comments

2 participants

tags (0)

participants (2)

Flavia Rainone (JIRA)
Kabir Khan (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBoss JIRA] Created: (JBAOP-796) Creation of ClassAdvisor must use the AspectManager equivalent to the advised class' ClassLoader