You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Tim Moloney (JIRA)" <ji...@apache.org> on 2007/02/11 05:38:05 UTC
[jira] Updated: (FELIX-204) commons-logging wrapping
[ https://issues.apache.org/jira/browse/FELIX-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Moloney updated FELIX-204:
------------------------------
Attachment: ApacheFelixCommons.tgz
I attached a tar file containing the following:
ApacheFelixCommons
|-- README
|-- activation-osgi
| `-- pom.xml
|-- avalon-framework-osgi
| `-- pom.xml
|-- commons-logging-osgi
| `-- pom.xml
|-- dependencies
|-- jms-osgi
| `-- pom.xml
|-- jmxtools-osgi
| `-- pom.xml
|-- jta-osgi
| `-- pom.xml
|-- log4j-osgi
| `-- pom.xml
|-- logkit-osgi
| `-- pom.xml
|-- mail-osgi
| `-- pom.xml
|-- pom.xml
|-- servlet-api-osgi
| `-- pom.xml
|-- template-pom.xml
`-- xerces-osgi
`-- pom.xml
> commons-logging wrapping
> ------------------------
>
> Key: FELIX-204
> URL: https://issues.apache.org/jira/browse/FELIX-204
> Project: Felix
> Issue Type: New Feature
> Components: Felix Commons
> Reporter: Tim Moloney
> Priority: Minor
> Attachments: ApacheFelixCommons.tgz
>
>
> Create the bundle(s) necessary to use commons-logging with Felix.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (FELIX-204) commons-logging wrapping
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Sunday 11 February 2007 12:45, Tim Moloney wrote:
> Hopefully, these bundles are useful enough for others to start using
> them. If they need refinement, perhaps others smarter than me on the
> above topics can improve them as needed.
The improvement already exist;
http://wiki.ops4j.org/confluence/display/ops4j/Pax+Logging
;o)
api : The internal api used for inter-bundle communication, as well
as some common APIs such as JDK util Logging and KFLog.
log4j : Log4J API
avalon : Avalon API
slf4j : SLF4J API
jcl : Commons-Logging API.
service : The current service implementation uses Log4J and allows you
to supply the log configuration via OSGi's Configuration Admin
Service.
To use; Load the legacy APIs that are needed, and use each APIs factory
method as usual.
The service can be reloaded with stopping the clients, to allow
for feature enhancements.
I am also contemplating to make Log4J backend itself more modular, so that
Appenders, Filters and Formatters can be loaded separately if needed. But
that work has not gotten far yet. Likewise, although it implements the OSGi
Log Service API, it is not fully compliant yet in respect to LogEvents and
LogReaders, but that is the target before a 1.0 release.
Cheers
Niclas
Re: [jira] Updated: (FELIX-204) commons-logging wrapping
Posted by Tim Moloney <t....@verizon.net>.
For your convenience, here's the README from the attachment.
===== begin README =====
This is my first attempt at creating a bundle for commons-logging (and
all the jars on which it depends).
While I could have simply created a single large bundle for
commons-logging that inlined all of its dependency jars, many of its
dependencies are useful library jars in their own right. So, to be as
modular as possible, I created a bundle for each of the dependency
jars.
While my cursory testing shows that these bundles work in Felix, there
are still a couple of issues left to work out.
- Copying the library jar to project directory so <Include-Resource>
can access it.
Currently this is a manual process that, if possible, needs to be
automated in maven. A better solution would be for the
maven-bundle-plugin to find and use the library jar file in the
maven repository.
- Maven dependencies vs OSGi bundle dependencies.
I don't fully understand maven dependency handling, OSGi dependency
handling, nor how they compare. Only the library jar file needs to
be listed in the <dependencies> section in the pom.xml file. This
relieves us from worrying about dependencies when creating the
bundle. However, all dependency bundles must be loaded in Felix
before commons-logging-osgi can be started, whether the dependency
jar is used by the commons-loggin configuration or not. For
example, if commons-logging is not configured to use avalon, the
avalon-framework-osgi bundle (and all of its dependencies) are
required to be loaded and started before commons-logging-osgi will
start. Perhaps this is a limitation on how commons-logging was
built. Perhaps I misunderstand how commongs-logging is supposed to
work. Perhaps I misunderstand how OSGi dependency management works.
Hopefully, these bundles are useful enough for others to start using
them. If they need refinement, perhaps others smarter than me on the
above topics can improve them as needed.
Tim Moloney
t.moloney@verizon.net
===== end README =====
Tim Moloney (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/FELIX-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Tim Moloney updated FELIX-204:
> ------------------------------
>
> Attachment: ApacheFelixCommons.tgz
>
> I attached a tar file containing the following:
>
> ApacheFelixCommons
> |-- README
> |-- activation-osgi
> | `-- pom.xml
> |-- avalon-framework-osgi
> | `-- pom.xml
> |-- commons-logging-osgi
> | `-- pom.xml
> |-- dependencies
> |-- jms-osgi
> | `-- pom.xml
> |-- jmxtools-osgi
> | `-- pom.xml
> |-- jta-osgi
> | `-- pom.xml
> |-- log4j-osgi
> | `-- pom.xml
> |-- logkit-osgi
> | `-- pom.xml
> |-- mail-osgi
> | `-- pom.xml
> |-- pom.xml
> |-- servlet-api-osgi
> | `-- pom.xml
> |-- template-pom.xml
> `-- xerces-osgi
> `-- pom.xml
>
>
>
>> commons-logging wrapping
>> ------------------------
>>
>> Key: FELIX-204
>> URL: https://issues.apache.org/jira/browse/FELIX-204
>> Project: Felix
>> Issue Type: New Feature
>> Components: Felix Commons
>> Reporter: Tim Moloney
>> Priority: Minor
>> Attachments: ApacheFelixCommons.tgz
>>
>>
>> Create the bundle(s) necessary to use commons-logging with Felix.
>>
>
>