[
https://issues.apache.org/jira/browse/LOG4J2-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713609#comment-13713609
]
Nick Williams commented on LOG4J2-10:
-------------------------------------
Tim,
One change that has been made recently is that classes in o.a.l.l.core.web in
the Core component reference the Servlet API (these classes used to be in their
own component). One of these classes requires Servlet 3.0 and the other classes
require Servlet 2.5. NONE of the classes are referenced by any classes outside
of that package, so I don't THINK it's going to cause an OSGi problem. These
classes are ONLY used through scanning (if you're in a Servlet 3.0 environment
already, so the Servlet classes are already on the classpath) or through the
deployment descriptor (if you're in a Servlet 2.5 environment, ditto).
The purpose of this change was to keep Web application users from having to
include an additional JAR just to get the Core to initialize/deinitialize
correctly in a Web application. What do you think? Is this going to be a
problem OSGi-wise?
Nick
> log4j 2.0 should work well with OSGi and Apache Felix
> -----------------------------------------------------
>
> Key: LOG4J2-10
> URL: https://issues.apache.org/jira/browse/LOG4J2-10
> Project: Log4j 2
> Issue Type: Wish
> Reporter: Curt Arnold
> Attachments: reduced-dependency-bundles-2.patch,
> reduced-dependency-bundles.patch
>
>
> OSGi and specifically the Apache Felix implementation should be considered
> for framework services such as internal logging and configuration.
> log4j 2.0 should be able to be a provider of OSGi logging services.
> OSGi package visibility declarations should be used to distinguish between
> exported and explicitly supported APIs and implementation specific details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
