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 configuration instance
will create the runtime configuration, which is a processed version of
the packages and their action configs.
The method configuration provider tries to access the runtime
configuration when it is still in the stage of collecting new packages
and actions. Currently, there is no way to inject logic between the
Configuration object being populated with packages and the building of
the runtime configuration. One option could be to create our own
Configuration subclass, which may perform this additional processing
of actionconfigs before the runtime config is built. In fact, I would
think this new process would be part of the runtime config processing.
Perhaps the patch should go in xwork 2's DefaultConfiguration object.>
In summary, what you want can't be done in a configuration provider.
We need to look at the configuration object itself.
Is the Configuration object going to have access to the Struts ObjectFactory?
The processing needs to inspect whatever classes are being used as
Actions, which could include injected classes.
Is the suggestion that there be an "event" or "hook" method between
collection of the configuration elements and finalizing the runtime
configuration that a subclass could override or extend?
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
