For an itest to validation messages, i was trying to recreate the exception
messages from implementation.spring module reported by
SpringImplementationProcessor.java code. Here is the piece of code from the
resolve method.
/* Load the Spring component type by reading the Spring application context
*/
SpringXMLComponentTypeLoader springLoader = new
SpringXMLComponentTypeLoader(assemblyFactory, javaFactory, policyFactory);
try {
// Load the Spring Implementation information from its application
context file...
springLoader.load(springImplementation);
} catch (ContributionReadException e) {
throw new ContributionResolveException(e);
}
ComponentType ct = springImplementation.getComponentType();
if (ct.isUnresolved()) {
// If the introspection fails to resolve, try to find a side file...
ComponentType componentType = resolver.resolveModel(ComponentType.class,
ct);
if (componentType.isUnresolved()) {
throw new ContributionResolveException("SpringArtifactProcessor:
unable to resolve componentType for Spring component");
}
springImplementation.setComponentType(componentType);
springImplementation.setUnresolved(false);
} // end if
I find the later part of the code trying to throw
ContributionResolveException in its resolve method saying that
"SpringArtifactProcessor: unable to resolve componentType for Spring
component", is unreachable, because all the exceptions araising due to a
introspection failure to resolve the component type are caught from the
first ContributionResolveException and thrown.
Can someone help in identifying a scenario to reproduce this second
ContributionResolveException in this code?
--
Thanks & Regards,
Ramkumar Ramalingam
