Collaboration - Rooms - Extensions points problem

[Former Member]

Hallo,

I'd like to perform my own code when an event of adding meeting appointment in room occur. I found document: Room Extension Developer Guide (https://media.sdn.sap.com/html/submitted_docs/nw_kmc/howto/coll/Room%20Extension%20Developer%20Guide.html). This document describes developing extensions. Extensions is service which is performed when some special event occur. There is 19 possible extensions points describing this events. But there is no suitable for creating meeting appointment for room. Is this possible with extensions mechanism? Or is there another way?

Best regards,

Josef Motl

[detlev_beutner · Accepted solution]

Hi Josef,

this isn't possible by ExtensionPoints directly.

In the end, adding a meeting appointment means creating some resource in some certain collection - so you could create a RepositoryService which reacts on the creation of resources and filters to react further only on created appointments.

Hope it helps

Detlev

[Former Member · Accepted solution]

Hi Detlev,

thanks for your responce, it gives me direction. But, I still don't know how to start. Can you give me some code snippet?

How can I find out which resource is affected by adding meeting appointment?

Best regards,

Josef

[detlev_beutner · Accepted solution]

Hi Josef,

use these as entry points

/thread/49286 [original link is broken]

and/or search on for "Repository Service" on SDN...

Hope it helps

Detlev

[Former Member · Accepted solution]

Hi Detlev,

thank for your responce. And what about my question: "How can I find out which resource is affected by adding meeting appointment?"

Regards,

Josef

[detlev_beutner · Accepted solution]

Hi Josef,

> meeting appointment

Seems that I didn't read exactly... I thought of "Sessions", which are stored internally, but if you think of appointments, you probably think of attaching Exchange or Lotus.

If this is the case, you won't be able to react on such a creation without modifying the implementation...

Sorry for bad news

Detlev