[
http://issues.ops4j.org/browse/PAXLOGGING-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13337#action_13337
]
Niclas Hedhman commented on PAXLOGGING-75:
------------------------------------------
Well, there are reasons for this, so a general request like this will go by
without attention. You will need to provide a proper use-case, so we can
discuss if it can be done in an existing manner, should be added or is
undesirable/impossible to provide for.
The Logger class is not designed for inheritence, and I would like to keep it
that way. I assume you are talking of the API side of the story, not the
service, and since the Logger class is 'different' from the original Log4j
class, it is not reasonable to expect that subclasses will work, as the
subclass often knows too much intricate details of its parent class, which in
this case are two different implementations (did I mention I hate
inheritence?)...
Again, show me what you want to do in real terms, not an abstracted
hypothetical case... and we can discuss.
> Constructor of "org.apache.log4j.Logger" is invisible
> -----------------------------------------------------
>
> Key: PAXLOGGING-75
> URL: http://issues.ops4j.org/browse/PAXLOGGING-75
> Project: Pax Logging
> Issue Type: Bug
> Components: API
> Affects Versions: 1.4
> Environment: Apache Felix 2.0, Pax Logging 1.4
> Reporter: Felix Hallmann
> Assignee: Niclas Hedhman
>
> I need a Logger Class extending "org.apache.log4j.Logger".
> I difference to the SLF4J / Log4j Bundles from springsource the Pax Logging
> implementation hides the needed constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
