osgi-branch ( status update )

[Göktürk Gezer <go...@apache.org>]

Hi Everyone,

I finally completed component-hub. It's core functionality is implemented
with the latest commits.

Now it can be used to :
* listen for annotated component's of any
type,(Interceptors,Partitions,DirectoryBackedServers for now...)
* create, cache and reconfigure instances of installed components
* Register HubListener to be notified of certain component type's
components as ADSComponent.
(you can look into previous mails with Pierre on 'OSGI status' for detailed
explanation of these systems.)

It's only lacking HouseKeeping process for now, has all the facilities to
implement it though. All we have to do is chose a good housekeeping schema:

I was thinking a schema that component-hub may delete all the entries in
config and schema partitions belonging to a component who is never been
online for 3 ApacheDS session. So if some test component is installed into
ApacheDS and then deleted. ApacheDS will keep its schema and config entries
for 3 server session, and then delete it. I'd like to hear more from you on
that...

So as i wrote in my first mails when i started component-hub, it would be
more and more easy now to make any part of ApacheDS extensible.

After finishing my reviews on component-hub I will go on by writing
HubClients for three main extension points:  Interceptors, Partitions and
DirectoryBackedServers. And then making them work together in the server
startup by using OSGI events.

More to come...


Regards,
Göktürk

Re: osgi-branch ( status update )

[Göktürk Gezer <go...@apache.org>]

Hi,

On Mon, Jan 9, 2012 at 11:25 AM, Alex Karasulu <ak...@apache.org> wrote:

>
> On Mon, Jan 9, 2012 at 4:55 AM, Göktürk Gezer <go...@apache.org> wrote:
>
>> Hi Everyone,
>>
>> I finally completed component-hub. It's core functionality is implemented
>> with the latest commits.
>>
>>
> Superb!
>
> SNIP ...
>
>
>> It's only lacking HouseKeeping process for now, has all the facilities to
>> implement it though. All we have to do is chose a good housekeeping schema:
>>
>> I was thinking a schema that component-hub may delete all the entries in
>> config and schema partitions belonging to a component who is never been
>> online for 3 ApacheDS session. So if some test component is installed into
>> ApacheDS and then deleted. ApacheDS will keep its schema and config entries
>> for 3 server session, and then delete it. I'd like to hear more from you on
>> that...
>>
>>
> Hmmm not understanding what it is you clearly need. Can you in a separate
> thread specify the problem, goal and why we're doing this. I think it has
> to do with record or schema retention for new components right?
>

Of course, i will open a separate thread for this and all the HubListeners.
HouseKeeping is what you think it is. But it's not primary objective right
now. We'll bring the server online in OSGI as a first step and then it can
be discussed along with bunch of similar topics those are about performance
and DIT structure.


>
>> So as i wrote in my first mails when i started component-hub, it would be
>> more and more easy now to make any part of ApacheDS extensible.
>>
>> After finishing my reviews on component-hub I will go on by writing
>> HubClients for three main extension points:  Interceptors, Partitions and
>> DirectoryBackedServers. And then making them work together in the server
>> startup by using OSGI events.
>>
>>
> Great thanks for the updated status.
>
> --
> Best Regards,
> -- Alex
>

Re: osgi-branch ( status update )

[Alex Karasulu <ak...@apache.org>]

On Mon, Jan 9, 2012 at 4:55 AM, Göktürk Gezer <go...@apache.org> wrote:

> Hi Everyone,
>
> I finally completed component-hub. It's core functionality is implemented
> with the latest commits.
>
>
Superb!

SNIP ...


> It's only lacking HouseKeeping process for now, has all the facilities to
> implement it though. All we have to do is chose a good housekeeping schema:
>
> I was thinking a schema that component-hub may delete all the entries in
> config and schema partitions belonging to a component who is never been
> online for 3 ApacheDS session. So if some test component is installed into
> ApacheDS and then deleted. ApacheDS will keep its schema and config entries
> for 3 server session, and then delete it. I'd like to hear more from you on
> that...
>
>
Hmmm not understanding what it is you clearly need. Can you in a separate
thread specify the problem, goal and why we're doing this. I think it has
to do with record or schema retention for new components right?


> So as i wrote in my first mails when i started component-hub, it would be
> more and more easy now to make any part of ApacheDS extensible.
>
> After finishing my reviews on component-hub I will go on by writing
> HubClients for three main extension points:  Interceptors, Partitions and
> DirectoryBackedServers. And then making them work together in the server
> startup by using OSGI events.
>
>
Great thanks for the updated status.

-- 
Best Regards,
-- Alex

Re: osgi-branch ( status update )

[Göktürk Gezer <go...@apache.org>]

On Mon, Jan 9, 2012 at 3:21 PM, Pierre-Arnaud Marcelot <pa...@marcelot.net>wrote:

> On 9 janv. 2012, at 03:55, Göktürk Gezer wrote:
>
> > Hi Everyone,
> >
> > I finally completed component-hub. It's core functionality is
> implemented with the latest commits.
> >
> > Now it can be used to :
> > * listen for annotated component's of any
> type,(Interceptors,Partitions,DirectoryBackedServers for now...)
> > * create, cache and reconfigure instances of installed components
> > * Register HubListener to be notified of certain component type's
> components as ADSComponent.
> > (you can look into previous mails with Pierre on 'OSGI status' for
> detailed explanation of these systems.)
>
> That's great Göktürk!
>
> I'm currently busy with the release of the first milestone for Studio 2.0,
> but as soon as I'm done with this I will definitely have a look at the OSGI
> branch and your latest commits.
>

I'm waiting for Studio too :)
Then yes, we should have a look at the code together. I need somebody to
review it.

>
> > It's only lacking HouseKeeping process for now, has all the facilities
> to implement it though. All we have to do is chose a good housekeeping
> schema:
> >
> > I was thinking a schema that component-hub may delete all the entries in
> config and schema partitions belonging to a component who is never been
> online for 3 ApacheDS session. So if some test component is installed into
> ApacheDS and then deleted. ApacheDS will keep its schema and config entries
> for 3 server session, and then delete it. I'd like to hear more from you on
> that…
>
> Like Alex, I'm having trouble following you here.
>
> What's an ApacheDS session exactly? Where does it happen? How long does a
> session last?
>

Yeah, i guess i am obscure on that, messed up with the terminology :) I was
trying to say:

Every individual component type will have its own automatically generated
schema elements and entries on ApacheDS. HouseKeeping will make sure we
keep ApacheDS clean of those schema elements and entries of component's
which is not been seen for a while. While saying session, i was referring
server start-stop cycles. So what is my mind is, when server is started and
stopped 3 times wihout having some component's bundle in its Felix folder,
then all previous schema elements and entries belonging to it will be
removed. But we can discuss it later as i said...


>
> Regards,
> Pierre-Arnaud
>
> > So as i wrote in my first mails when i started component-hub, it would
> be more and more easy now to make any part of ApacheDS extensible.
> >
> > After finishing my reviews on component-hub I will go on by writing
> HubClients for three main extension points:  Interceptors, Partitions and
> DirectoryBackedServers. And then making them work together in the server
> startup by using OSGI events.
> >
> > More to come...
> >
> >
> > Regards,
> > Göktürk
>
>

Re: osgi-branch ( status update )

[Pierre-Arnaud Marcelot <pa...@marcelot.net>]

On 9 janv. 2012, at 03:55, Göktürk Gezer wrote:

> Hi Everyone,
> 
> I finally completed component-hub. It's core functionality is implemented with the latest commits.
> 
> Now it can be used to :
> * listen for annotated component's of any type,(Interceptors,Partitions,DirectoryBackedServers for now...)
> * create, cache and reconfigure instances of installed components
> * Register HubListener to be notified of certain component type's components as ADSComponent.
> (you can look into previous mails with Pierre on 'OSGI status' for detailed explanation of these systems.)

That's great Göktürk!

I'm currently busy with the release of the first milestone for Studio 2.0, but as soon as I'm done with this I will definitely have a look at the OSGI branch and your latest commits.

> It's only lacking HouseKeeping process for now, has all the facilities to implement it though. All we have to do is chose a good housekeeping schema:
> 
> I was thinking a schema that component-hub may delete all the entries in config and schema partitions belonging to a component who is never been online for 3 ApacheDS session. So if some test component is installed into ApacheDS and then deleted. ApacheDS will keep its schema and config entries for 3 server session, and then delete it. I'd like to hear more from you on that…

Like Alex, I'm having trouble following you here.

What's an ApacheDS session exactly? Where does it happen? How long does a session last?

Regards,
Pierre-Arnaud 

> So as i wrote in my first mails when i started component-hub, it would be more and more easy now to make any part of ApacheDS extensible.
> 
> After finishing my reviews on component-hub I will go on by writing HubClients for three main extension points:  Interceptors, Partitions and DirectoryBackedServers. And then making them work together in the server startup by using OSGI events.
> 
> More to come...
> 
> 
> Regards,
> Göktürk