directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DIRSERVER-1332) Create apacheds-all OSGi bundle
Date Thu, 19 Mar 2009 08:45:50 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683367#action_12683367
] 

Pierre-Arnaud Marcelot commented on DIRSERVER-1332:
---------------------------------------------------

# The only thing that I have done that may cause problems is that i have generated a modified
schema for validating the server.xml file as opposed to the xbean generation during the build.
I did this to get around some issues I was having but I think I can make it work better with
a few more hours of work. As far as the packaging (bundle vs jar), a bundle is just a jar
with extra manifest info so everything will continue to work the same if you are just using
it as a jar. I will work more on the schema tomorrow because I am sure that will not work
with existing server.xml files. 

I don't think the files under src/main/resources will bother us when using the jar as a simple
library.

BTW, I don't see any BundleActivator class. Which class is responsible of the life cycle of
the bundle?


# I checked back in December about current usage of apacheds-all and I didn't recall any official
uses so I thought we established that it was OK to work on it here in trunk. If this is going
to cause some worries I am happy to move it to sandbox if necessary.

Yeah, we don't make use of this jar inside the project. It is more directed to our users who
want a single library containing all the dependencies.
Here's initial JIRA about the apacheds-all project: https://issues.apache.org/jira/browse/DIRSERVER-900
The apacheds-all project is also used in the documentation at http://cwiki.apache.org/confluence/display/DIRxSRVx11/4.2.+Using+ApacheDS+for+unit+tests

I don't think working in a sandbox is required, but if the modifications to make the jar become
an OSGI bundle forbids us to use the jar in its initial purpose, I think a new specific apacheds-osgi
project in trunk would make more sense.

My 2 cents.

> Create apacheds-all OSGi bundle
> -------------------------------
>
>                 Key: DIRSERVER-1332
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1332
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>    Affects Versions: 1.5.5
>            Reporter: Chris Custine
>            Assignee: Chris Custine
>             Fix For: 1.5.5
>
>
> The apacheds-all project could very easily be converted to an OSGi bundle for deployment
in an OSGi container.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message