Is a Portal service guaranteed to be a singleton?

[Former Member]

Hi,

Does anyone know if a portal service is guaranteed to be a singleton (i.e. there will only be one instance of it) ?

From my tests, this appears to be true, but are there situations where it is not?

Cheers

Dagfinn

[detlev_beutner · Accepted solution]

Hi Dagfinn,

I have your question and the answer to this open since this morning, but didn't send it for not having answered the second question about whether all services are loaded by the same classloader (I'm quite sure answer is also yes, but to be <i>really sure</i>, one should have a look into the sources; no time at the moment).

Anyhow, pfffft, dust, go away, here comes the answer from this morning:

Yes, see the statement of the leader of the leaders, the poster of the posters, the king of the kings, the famous ... taramtamtam ... Detlev

Or simply trust SAP: "Since an extension is a service, there is only one instance in the portal. It is a singleton." To be read in https://media.sdn.sap.com/html/submitted_docs/nw_kmc/howto/coll/Room%20Extension%20Developer%20Guide...

You can also check the sitaution: Services are centralized "stopped" and/or "started" / "restarted" from System Administration ... (the path you will find by yourself or already know).

Hope it helps

Detlev

[Former Member · Accepted solution]

Hi,

Thanks for confirming this, O' Great One

I am also planning to look into the source regarding the classloader of the service. My question in the other thread was more of a rethorical question