It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,878
×10,913

question asked: Mar 10 '11, 1:01 p.m.
question was seen: 5,488 times
last updated: Mar 10 '11, 1:01 p.m.

Related questions

CRJAZ1115I with *.common.transport.ITeamServiceContext

0
Eduardo Bello (440●19●22) | asked Mar 10 '11, 1:01 p.m.
I'm trying to use a code like this to get session id: 


ITeamServiceContext context = getService(ITeamServiceContext.class);

String sessionId = context.getHttpServletRequest().getSession().getId();


I added the following interfaces to my plugin xml extension->operationAdvisor->extensionService->prerequisites: 


requiredService interface="com.ibm.team.repository.common.transport.ITeamServiceContext



requiredService interface="com.ibm.team.workitem.service.IWorkItemServer"



requiredService interface="com.ibm.team.build.internal.common.ITeamBuildService"





requiredService interface="com.ibm.team.links.common.service.ILinkService"



requiredService interface="com.ibm.team.repository.service.IRepositoryItemService"

						

requiredService interface="com.ibm.team.workitem.common.IWorkItemCommon"



<requiredService interface="com.ibm.team.links.common.service.ILinkService"



My manifest.mf 


Manifest-Version: 1.0

Bundle-ManifestVersion: 2

Bundle-Name: Rtc_check_links_fields_advisor Plug-in

Bundle-SymbolicName: rtc_check_links_fields_advisor;singleton:=true

Bundle-Version: 1.0.0.qualifier

Bundle-RequiredExecutionEnvironment: J2SE-1.5

Require-Bundle: com.ibm.team.repository.common.transport,

 com.ibm.team.process.service,

 com.ibm.team.workitem.common,

 com.ibm.team.workitem.service,

 com.ibm.team.process.common,

 com.ibm.team.repository.common,

 com.ibm.team.repository.service,

 rtc_util

Import-Package: javax.servlet.http,

 org.eclipse.core.runtime


But I can't get it to work... 


com.ibm.team.repository.common.transport.TeamServiceRegistryException: CRJAZ1115I The service "com.ibm.team.repository.common.transport.ITeamServiceContext" was not registered.

	at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getClassForInterface(OsgiServicesManager.java:195)

	at com.ibm.team.repository.common.transport.internal.registry.OsgiServicesManager.getService(OsgiServicesManager.java:256)

	at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.buildServicesMap(AbstractActivationManagerOwner.java:310)

	at com.ibm.team.repository.common.transport.internal.registry.AbstractActivationManagerOwner.doActivate(AbstractActivationManagerOwner.java:568)

	at com.ibm.team.repository.common.transport.internal.registry.ExtensionServiceActivationManagerOwner.doActivate(ExtensionServiceActivationManagerOwner.java:69)

	at com.ibm.team.repository.common.transport.internal.registry.ExtensionServiceActivationManagerOwner.forceActivate(ExtensionServiceActivationManagerOwner.java:91)

	at com.ibm.team.repository.common.transport.registry.ExtensionServiceElementDescriptor.getImplementation(ExtensionServiceElementDescriptor.java:345)

	at com.ibm.team.process.internal.service.OperationAdvisorServerRegistry.createAdvisor(OperationAdvisorServerRegistry.java:115)

	at com.ibm.team.process.internal.common.advice.runtime.OperationAdviceManager.runAdvisors(OperationAdviceManager.java:811)

	at com.ibm.team.process.internal.common.advice.runtime.OperationAdviceManager.advise(OperationAdviceManager.java:273)

	at com.ibm.team.process.internal.common.util.AbstractProcess.doAdvise(AbstractProcess.java:177)

	at com.ibm.team.process.internal.service.ServerProcess.access$1(ServerProcess.java:1)

....

....

....

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Eduardo Bello (440●19●22) | answered Mar 10 '11, 4:34 p.m.
Although I don't understand why this error occurs, I choose another approach by getting the context using 


TeamServiceContext context = TeamServiceContext.getCurrent();


And that worked well.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.