The ContainerConfiguration SPI should include a method that is invoked after all the properties have been set so that component properties can be calculated and perhaps validation can be performed. When you introduce a container-managed component type w/o a post-construct hook, it results in logic being performed in setter methods. We don't want that sort of thing. We want to keep it clean.

public interface ContainerConfiguration
{
ContainerProfile getContainerProfile();
void afterPropertiesSet(); // alternate: void postConstruct();
}

We could also entertain the possibility of honoring the @PostConstruct annotation.

An example use case is to assemble the JSR-88 deployment URI from various facts provided, such as the server host and port (or admin server host and port), if an explicit deployment URI is not provided.