Organizations sometimes would like to implement naming conventions for components based on the architecture for example. This post shows a simple example advisor that checks for a naming convention.
License
The post contains published code, so our lawyers reminded me to state that the code in this post is derived from examples from Jazz.net as well as the RTC SDK. The usage of code from that example source code is governed by this license. Therefore this code is governed by this license. I found a section relevant to source code at the and of the license. Please also remember, as stated in the disclaimer, that this code comes with the usual lack of promise or guarantee. Enjoy!
Just Starting With Extending RTC?
If you just get started with extending Rational Team Concert, or create API based automation, start with the post Learning To Fly: Getting Started with the RTC Java API’s and follow the linked resources.
You should be able to use the following code in this environment and get your own automation or extension working.
Compatibility
This code has been used with RTC 6.0 and is prepared to be used with RTC 6.0.x with no changes and it is pretty safe to assume, that the code will work with newer versions of RTC. It should run with any version that provides the operation ID.
The code in this post uses common and server libraries/services that are available in the RTC Server SDK.
Download
The code is included in the download in the post DIY stream naming convention advisors.
Solution
In the last few versions of RTC several operations have been made available for operational behavior. At least since RTC 5.0.2 the operation to modify a component is available with the operation ID com.ibm.team.scm.server.component. This allows to create advisors/preconditions as well as participants/follow up actions that operate on such events. An example shipped with the product is implemented in the class com.ibm.team.scm.service.UniqueComponentNameAdvisor.
There are examples shipped with the product in the SDK that you can look at for more sample code. For example: com.ibm.team.scm.service.internal.process.advisors.UniqueComponentNameAdvisor
The code below shows a very basic example how to test the component name for some simple naming schema.
The important information to take away is that the information about the save operation is provided in a special interface IComponentModificationData which allows access to the type of the operation, to old and new properties and to the component directly.
So it is possible to find out what operation is done on the component and based on that look at the properties that the component has.
The code below does exactly that. It checks what operation is going on and then takes the new name of the component and checks it.
/*******************************************************************************
* Licensed Materials - Property of IBM
* (c) Copyright IBM Corporation 2017. All Rights Reserved.
*
* Note to U.S. Government Users Restricted Rights: Use, duplication or
* disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
*******************************************************************************/
package com.ibm.js.scm.naming.advisor.service;
import org.eclipse.core.runtime.IProgressMonitor;
import com.ibm.team.process.common.IProcessConfigurationElement;
import com.ibm.team.process.common.advice.AdvisableOperation;
import com.ibm.team.process.common.advice.IAdvisorInfo;
import com.ibm.team.process.common.advice.IAdvisorInfoCollector;
import com.ibm.team.process.common.advice.runtime.IOperationAdvisor;
import com.ibm.team.repository.common.TeamRepositoryException;
import com.ibm.team.scm.service.internal.AbstractScmService;
import com.ibm.team.scm.service.internal.process.IComponentModificationData;
import com.ibm.team.scm.service.internal.process.IComponentModificationData.OpType;
/**
* An example advisor that checks the name of a component for some naming convention
*
* Also @see com.ibm.team.scm.service.UniqueComponentNameAdvisor for product example code
*/
@SuppressWarnings("restriction")
public class ComponentNamingAdvisor extends AbstractScmService implements
IOperationAdvisor {
public static final String REQUIRED_PREFIX = "TEST_";
public static final String COMPONENT_NAMING_ADVISOR = "com.ibm.js.scm.naming.advisor.service.componentNaming";
@Override
public void run(AdvisableOperation operation,
IProcessConfigurationElement advisorConfiguration,
IAdvisorInfoCollector collector, IProgressMonitor monitor)
throws TeamRepositoryException {
IComponentModificationData data = (IComponentModificationData) operation
.getOperationData();
if (data == null) {
throw new TeamRepositoryException("Missing component data"); //$NON-NLS-1$
}
String compName;
if (data.getOpType() == OpType.CREATE) {
compName = data.getNewName();
} else if (data.getOpType() == OpType.RENAME) {
compName = data.getNewName();
} else {
return;
}
if (validateName(compName)) {
// Nothing to do
return;
}
String description = "The component name violates the naming conventions component name must have prefix '"
+ REQUIRED_PREFIX + "'!";
String summary = description;
IAdvisorInfo info = collector.createProblemInfo(summary, description,
COMPONENT_NAMING_ADVISOR);//$NON-NLS-1$
collector.addInfo(info);
}
/**
* Validate the name against the convention
*
* @param compName
* @return
*/
private boolean validateName(String compName) {
// Implement your own naming convention here
if (compName.startsWith(REQUIRED_PREFIX)) {
return true;
}
return false;
}
}
Summary
This is as usual a very basic example with no or very limited testing and error handling. See the links in the getting started section for more examples. As always I hope this helps someone out there with running RTC.
rsjazz 