[ http://jira.jboss.com/jira/browse/JBAOP-226?page=all ]
Kabir Khan updated JBAOP-226:
-----------------------------
Fix Version/s: 2.0.0.alpha2
(was: 2.0.0.alpha1)
> 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.alpha2
>
>
> 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
[ http://jira.jboss.com/jira/browse/JBAOP-246?page=all ]
Kabir Khan updated JBAOP-246:
-----------------------------
Fix Version/s: 2.0.0.alpha2
(was: 2.0.0.alpha1)
> 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.alpha2
>
>
> 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
[ http://jira.jboss.com/jira/browse/JBAOP-44?page=all ]
Kabir Khan updated JBAOP-44:
----------------------------
Fix Version/s: 2.0.0.alpha2
(was: 2.0.0.alpha1)
> document new ARGS features
> --------------------------
>
> Key: JBAOP-44
> URL: http://jira.jboss.com/jira/browse/JBAOP-44
> Project: JBoss AOP
> Issue Type: Task
> Affects Versions: 2.0.0.alpha1
> Reporter: Bill Burke
> Assigned To: Bill Burke
> Fix For: 2.0.0.alpha2
>
>
> Document typed argument access within aspects as well as the CurrentInvocation class.
--
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
[ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ]
Kabir Khan updated JBAOP-253:
-----------------------------
Fix Version/s: 2.0.0.alpha2
(was: 2.0.0.alpha1)
> Before release, submit the jar to the Messaging team for testing
> ----------------------------------------------------------------
>
> Key: JBAOP-253
> URL: http://jira.jboss.com/jira/browse/JBAOP-253
> Project: JBoss AOP
> Issue Type: Task
> Reporter: Ovidiu Feodorov
> 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
[ http://jira.jboss.com/jira/browse/JBAOP-43?page=all ]
Kabir Khan updated JBAOP-43:
----------------------------
Fix Version/s: 2.0.0.alpha2
(was: 2.0.0.alpha1)
> ThreadMetadata serialization
> ----------------------------
>
> Key: JBAOP-43
> URL: http://jira.jboss.com/jira/browse/JBAOP-43
> 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.alpha2
>
>
> ThreadMetadata should be serialized separately and merged with remote ThreadMetaData.
--
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
[ http://jira.jboss.com/jira/browse/JBAOP-48?page=all ]
Kabir Khan updated JBAOP-48:
----------------------------
Fix Version/s: 2.0.0.alpha2
(was: 2.0.0.alpha1)
> 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.alpha2
>
>
> 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
[ http://jira.jboss.com/jira/browse/JBAOP-69?page=all ]
Kabir Khan updated JBAOP-69:
----------------------------
Fix Version/s: 2.0.0.alpha2
(was: 2.0.0.alpha1)
> InvocationResponse should catch/wrap exceptions
> -----------------------------------------------
>
> Key: JBAOP-69
> URL: http://jira.jboss.com/jira/browse/JBAOP-69
> 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.alpha2
>
>
> InvocationResponse in dynamicInvoke should catch all thrown exceptions and stuff them into InvocationResponse.
> The "client" of dynamicInvoke should look in IR to see if an exception is in there and rethrow it. It should also set the response attachments of the invocation as well.
--
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
[ http://jira.jboss.com/jira/browse/JBAOP-268?page=all ]
Kabir Khan updated JBAOP-268:
-----------------------------
Fix Version/s: 2.0.0.alpha2
(was: 2.0.0.alpha1)
> 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
> Fix For: 2.0.0.alpha2
>
>
> 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