thanks Gokturk for the details, have another q. what will happen if I try to run the server in another OSGi runtime? will the server still start its own OSGi runtime?
On Mon, Oct 17, 2011 at 11:42 AM, Göktürk Gezer <[email protected]> wrote: > Hi Kiran, Pierre > Answer depends on which level we'll use OSGI. If we'll only support OSGI, > the answer is yes. If we'll use OSGI as our fuel to make ApacheDS > extendable, the answer is no. > But only supporting is not a good decision for ApacheDS. As OSGI support, we > can only separate 3.th party dependencies for now and make ApacheDS > megabundle, so that users can install ApacheDS on their OSGI frameworks > without causing library dependency problems. This can already be implemented > in no time. > However as we use OSGI to actually make ApacheDS extendable , we have to use > other features of OSGI other than modularity. And that makes us dependent on > OSGI Framework. Any other solution for extendability other than OSGI will > also broke your current way of running ApacheDS. > So, OSGI support is something meaningful for libraries only. For an > application like ApacheDS, we must sit on top of OSGI. That will change our > way of deploying, installing and running ApacheDS. > > Regards, > Gokturk > > On Mon, Oct 17, 2011 at 5:16 PM, Pierre-Arnaud Marcelot <[email protected]> > wrote: >> >> Hi Kiran, >> >> That's a very good and important question. >> >> It would be cool if we could do the same thing we did with the API >> (Shared) which is OSGI-ready but also works perfectly as a set of simple >> (good old) jar files. >> >> Regards, >> Pierre-Arnaud >> >> On 17 oct. 2011, at 16:10, Kiran Ayyagari wrote: >> >> > Is it possible to start the server without using karaf at all after >> > complete OSGification of the server? >> > put it in another way, would it be possible to start the server using >> > the existing apacheds.sh script, without loading karaf? >> > >> > >> > On Mon, Oct 17, 2011 at 1:04 AM, Göktürk Gezer <[email protected]> >> > wrote: >> >> Hi Emmanuel, >> >> I attached "custom felix framework distribution" patch at >> >> #DIRSERVER-1669 . >> >> This custom framework will let us run and debug our OSGI based codes >> >> inside >> >> Eclipse. To use it properly, there are two additional steps: >> >> ...after mvn install, mvn eclipse:eclipse and importing projects into >> >> Eclipse >> >> 1-) Add apache-felix/bin/felix.jar to project's Build Path ( to use >> >> ApacheDS-OSGI.launcher ) >> >> 2-) In apache-felix project's Build Path, add all projects in >> >> workspace as >> >> project dependencies. ( to enable source viewing while debugging >> >> (requires >> >> Eclipse restart) ) >> >> With this in our hands, we can work on OSGI faster than ever. >> >> >> >> Regards, >> >> Göktürk >> > >> > >> > >> > -- >> > Kiran Ayyagari >> > > -- Kiran Ayyagari
