[
https://issues.apache.org/jira/browse/PROXY-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576743#action_12576743
]
Torsten Curdt commented on PROXY-11:
------------------------------------
While I agree it would be nice to use that method of picking the
implementation. Why don't you just create a wrapper that checks the existence
of different classes and we include that into the next release of proxy. That
should be pretty straight forward. I fear changing the build of proxy is a
slightly bigger task.
BTW: about commons logging - I guess that's no longer more than FUD ...or do
you still have problems?
> slf4j-like discovery of the Proxy implementation to use
> -------------------------------------------------------
>
> Key: PROXY-11
> URL: https://issues.apache.org/jira/browse/PROXY-11
> Project: Commons Proxy
> Issue Type: Improvement
> Affects Versions: 1.0
> Environment: wicket
> Reporter: Johan Compagner
>
> I set this prio to major but for wicket it is really a blocker. In the
> current state i just cant use commons proxy
> I dont want in a general framework to make a decission which implementation
> that i should use
> Something like this should be done outside the code or at least outside my
> code (that slf4j or commons logging also do)
> Look at how slf4j does it because the commons logging way is a bit flawed
> (classloading problems)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
