[
https://issues.apache.org/jira/browse/HTTPCLIENT-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roland Weber closed HTTPCLIENT-160.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 4.0 Alpha 1)
There will be no tracing in HttpCore, and only selected tracing in other
components.
As far as I can tell, AOP is only able to handle entry/exit tracing, which is
usually
generating more noise than anybody would like. At the same time, it would
complicate
the build environment and require us to learn a new programming paradigm. I'm
not
at all against learning, but HttpComponents are supposed to reach production
quality.
They are the wrong testbed for experimenting with new paradigms.
I'm closing this issue for now. If anyone knows of a place in HttpComponents
where
AOP might add significant value, please re-open.
cheers,
Roland
> Introduce Aspect oriented programming
> -------------------------------------
>
> Key: HTTPCLIENT-160
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-160
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Affects Versions: 2.0 Alpha 2
> Environment: Operating System: All
> Platform: All
> Reporter: Jeff Dever
> Priority: Minor
>
> HttpClient uses logging extensively to provide exeuction trace. Each method
> has
> (or is supposed to have) an log at its entry point. This is a classic "cross
> cutting concern" that is well solved by aspect oriented programming tecniques.
> AspectJ is well supporte in Maven and is used in a number of other Jakarta
> projects, notably Cactus.
> Consider introducing aspects to HttpClient.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
