com.ibm.team.repository.common.TeamRepositoryException
Hello,
I'm trying to integrate rtc client api in a was web application.
I'm using was 7 and rtc api 3.0.
this is my code
When I call t.registerLoginHandler() I receive the follow error:
Caused by: com.ibm.team.repository.common.TeamRepositoryException: Badly configured client. Missing a foundation component tag.
at com.ibm.team.repository.client.internal.TeamRepository.checkServerVersionMatches(TeamRepository.java:1582)
at com.ibm.team.repository.client.internal.TeamRepository.internalLogin(TeamRepository.java:1444)
at com.ibm.team.repository.client.internal.TeamRepository.login(TeamRepository.java:617)
Can someone help me?
Thanks in advance!
I'm trying to integrate rtc client api in a was web application.
I'm using was 7 and rtc api 3.0.
this is my code
TeamPlatform.startup();
ITeamRepositoryService teamRepositoryService = TeamPlatform.getTeamRepositoryService();
t = teamRepositoryService.getTeamRepository("https://172.24.xxx.xx:9443/ccm/");
t.registerLoginHandler(new ITeamRepository.ILoginHandler() {
public ILoginInfo challenge(ITeamRepository repository) {
return new ILoginInfo() {
public String getUserId() {
return "user";
}
public String getPassword() {
return "password";
}
};
}
});
t.login(null);
When I call t.registerLoginHandler() I receive the follow error:
Caused by: com.ibm.team.repository.common.TeamRepositoryException: Badly configured client. Missing a foundation component tag.
at com.ibm.team.repository.client.internal.TeamRepository.checkServerVersionMatches(TeamRepository.java:1582)
at com.ibm.team.repository.client.internal.TeamRepository.internalLogin(TeamRepository.java:1444)
at com.ibm.team.repository.client.internal.TeamRepository.login(TeamRepository.java:617)
Can someone help me?
Thanks in advance!
2 answers
The issue is because of missing plugin configurations in eclipse classes, caused by classloading issues.
WebSphere 7 is implemented using OSGI technology like eclipse, so the eclipse platform classes by default are loaded from WebSphere, and the ones not by RTC client libraries included in the web application.
A possible solution is to include the lib classes into the webapp and reverse the class loading policy. Be careful to remove javax.servlet jar (included into RTC clint libraries), in order to be able to use the websphere classes for this specific library.
There are at least 2 way to reverse classloading policies:
* From WebSphere administration console. This is ok when deploying throught the console, but it will not work inside RAD WebSphere test environment, since the checkboxes will be disabled
* By creating deployment.xml file, usin RAD java right click menu on EAR file ( JavaEE --> Open WebSphere Application Server Deployment )
Best Regards
WebSphere 7 is implemented using OSGI technology like eclipse, so the eclipse platform classes by default are loaded from WebSphere, and the ones not by RTC client libraries included in the web application.
A possible solution is to include the lib classes into the webapp and reverse the class loading policy. Be careful to remove javax.servlet jar (included into RTC clint libraries), in order to be able to use the websphere classes for this specific library.
There are at least 2 way to reverse classloading policies:
* From WebSphere administration console. This is ok when deploying throught the console, but it will not work inside RAD WebSphere test environment, since the checkboxes will be disabled
* By creating deployment.xml file, usin RAD java right click menu on EAR file (
Best Regards