You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Chris Custine (JIRA)" <ji...@apache.org> on 2009/03/19 05:53:50 UTC

[jira] Created: (DIRSERVER-1332) Create apacheds-all OSGi bundle

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


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.


[jira] Commented: (DIRSERVER-1332) Create apacheds-all OSGi bundle

Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRSERVER-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683354#action_12683354 ] 

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

Hi Chris,

It's very nice to see OSGI support for Apache DS. I'd love to see that running in an OSGI container.

However, I'm a little concerned about the modifications on the apacheds-all project.

Is it still possible to use the apacheds-all jar file (bundle jar I should say now) as a "simple" jar library (like before) or does the changes in the resources and/or the way the jar is built in the pom.xml file forbids us to do so ?

This is just to make sure that we stay compatible with our previous usage of the project. ;)

> 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.


[jira] Commented: (DIRSERVER-1332) Create apacheds-all OSGi bundle

Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRSERVER-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683357#action_12683357 ] 

Chris Custine 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 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.

> 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.


[jira] Resolved: (DIRSERVER-1332) Create apacheds-all OSGi bundle

Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Custine resolved DIRSERVER-1332.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.5

> 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.


[jira] Commented: (DIRSERVER-1332) Create apacheds-all OSGi bundle

Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (DIRSERVER-1332) Create apacheds-all OSGi bundle

Posted by "Chris Custine (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRSERVER-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683324#action_12683324 ] 

Chris Custine commented on DIRSERVER-1332:
------------------------------------------

Initial support for embedded OSGi bundle.  This will not work by itself and requires some form of bootstrapping code to push the configuration and create the server.  I will be adding some sandbox code in the next few days to show examples of how this can be achieved in various ways.

> 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.


[jira] Closed: (DIRSERVER-1332) Create apacheds-all OSGi bundle

Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRSERVER-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRSERVER-1332.
----------------------------------------


> 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.