You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2011/07/07 18:13:16 UTC
[jira] [Created] (ARIES-706) support dynamic configuration of
classes that will be ignored by proxy/weaving...
support dynamic configuration of classes that will be ignored by proxy/weaving...
---------------------------------------------------------------------------------
Key: ARIES-706
URL: https://issues.apache.org/jira/browse/ARIES-706
Project: Aries
Issue Type: Bug
Components: Proxy
Reporter: Kevan Miller
Currently, the weaving code has a static list of packages that will be ignored. There needs to be some support for a configurable list of packages/classes that will be ignored by Aries.
Including 0.4-SNAPSHOT into Geronimo has identified a number of integration problems with existing open source projects. Arguably, the solution is to update these existing open source projects (to ignore synthetic methods/fields, etc). However, this will not always be practical.
We need a way of dynamically configuring Aries weaving (even to the point of effectively turning weaving off, entirely).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ARIES-706) support dynamic configuration of
classes that will be ignored by proxy/weaving...
Posted by "Richard Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398267#comment-13398267 ]
Richard Ellis commented on ARIES-706:
-------------------------------------
The function from ARIES-786 (for system property configuration) and ARIES-826 (for the ProxyWeavingController service) have provided two ways of controlling weaving. Do we still need this JIRA?
> support dynamic configuration of classes that will be ignored by proxy/weaving...
> ---------------------------------------------------------------------------------
>
> Key: ARIES-706
> URL: https://issues.apache.org/jira/browse/ARIES-706
> Project: Aries
> Issue Type: Bug
> Components: Proxy
> Reporter: Kevan Miller
>
> Currently, the weaving code has a static list of packages that will be ignored. There needs to be some support for a configurable list of packages/classes that will be ignored by Aries.
> Including 0.4-SNAPSHOT into Geronimo has identified a number of integration problems with existing open source projects. Arguably, the solution is to update these existing open source projects (to ignore synthetic methods/fields, etc). However, this will not always be practical.
> We need a way of dynamically configuring Aries weaving (even to the point of effectively turning weaving off, entirely).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (ARIES-706) support dynamic configuration of
classes that will be ignored by proxy/weaving...
Posted by "Emily Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emily Jiang closed ARIES-706.
-----------------------------
Resolution: Fixed
As per Rich's comments, this jira has been fixed under Aries-786 and Aries-826.
> support dynamic configuration of classes that will be ignored by proxy/weaving...
> ---------------------------------------------------------------------------------
>
> Key: ARIES-706
> URL: https://issues.apache.org/jira/browse/ARIES-706
> Project: Aries
> Issue Type: Bug
> Components: Proxy
> Reporter: Kevan Miller
>
> Currently, the weaving code has a static list of packages that will be ignored. There needs to be some support for a configurable list of packages/classes that will be ignored by Aries.
> Including 0.4-SNAPSHOT into Geronimo has identified a number of integration problems with existing open source projects. Arguably, the solution is to update these existing open source projects (to ignore synthetic methods/fields, etc). However, this will not always be practical.
> We need a way of dynamically configuring Aries weaving (even to the point of effectively turning weaving off, entirely).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ARIES-706) support dynamic configuration of
classes that will be ignored by proxy/weaving...
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ARIES-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398328#comment-13398328 ]
Kevan Miller commented on ARIES-706:
------------------------------------
No, I don't think so. You can close it out as fixed.
> support dynamic configuration of classes that will be ignored by proxy/weaving...
> ---------------------------------------------------------------------------------
>
> Key: ARIES-706
> URL: https://issues.apache.org/jira/browse/ARIES-706
> Project: Aries
> Issue Type: Bug
> Components: Proxy
> Reporter: Kevan Miller
>
> Currently, the weaving code has a static list of packages that will be ignored. There needs to be some support for a configurable list of packages/classes that will be ignored by Aries.
> Including 0.4-SNAPSHOT into Geronimo has identified a number of integration problems with existing open source projects. Arguably, the solution is to update these existing open source projects (to ignore synthetic methods/fields, etc). However, this will not always be practical.
> We need a way of dynamically configuring Aries weaving (even to the point of effectively turning weaving off, entirely).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira