Ted Husted wrote:
On 12/19/06, Don Brown <[EMAIL PROTECTED]> wrote:
Ok, the problem here is a misunderstanding how the configuration
providers work. A configuration provider creates packageconfigs
populated with the appropriate information. Once all configuration
providers have provided their
On 12/19/06, Don Brown <[EMAIL PROTECTED]> wrote:
Ok, the problem here is a misunderstanding how the configuration
providers work. A configuration provider creates packageconfigs
populated with the appropriate information. Once all configuration
providers have provided their packages, the confi
Ok, the problem here is a misunderstanding how the configuration
providers work. A configuration provider creates packageconfigs
populated with the appropriate information. Once all configuration
providers have provided their packages, the configuration instance
will create the runtime configura
The exception is thrown because, for some reason, the bean selector
configuration provider isn't providing a factory for the default mapping
of ActionMapper. Is your new configuration provider preempting it somehow?
Don
Ted Husted wrote:
On the ticket for generating ActionConfigs for all pot
