From my point of view, bundles that are generic from any specific
technology are good candidates for a Felix subproject or provide some
functionality that is clearly outside of any other existing project. As
an example, you can imagine some form of a remoting service that can
make OSGi service remotely available using different remoting
technologies that can be plugged in. On the other, if a bundle is tied
to a specific technology, e.g., James, then perhaps it is better suited
to be hosted at that community.
Of course, if the community in question isn't interested and there is
sufficient interests in the Felix community, then it is still a possible
subproject for Felix, but I think the ultimate goal would be to get the
original community to eventually take it over.
So, in short, it depends. :-)
-> richard
Pedro Pedruzzi wrote:
Hi all.
I am looking for OSGi bundles implementing services such as DNS, HTTP,
NTP, SMTP and SNMP servers.
I found some projects working on implementations of these servers in
Java. But it seems that they usually don't provide a release of the
service component as an OSGi bundle (publishing services and possibly
using ConfigAdmin).
Of course these components wrapped to accomplish this, just the way
you did with Jetty to implement HTTP Service (except that it will not
implement a API from the specs like HTTP Service).
Where should such an OSGi wrapper project resides? Do we expect the
component maintainers to write and host it? Or do we write ourselves
and host it as a separate project, or possibly host it along with
Felix?
For example, I noticed that James Server (ASF mail server) guys were
thinking about implementing James as a set of OSGi bundles [1]. There
is also a sandbox implementation of a configuration file loader for
ConfigAdmin [2]. And I want to run James server, like it is today (not
OSGi), inside Felix.
I'd appreciate any comments on this. And also on where I can found
bundles for the services I mentioned.
Regards,
