Hello Ted,
Sunday, June 10, 2001, 1:39:17 PM, you wrote:
TH> [ This suggestion based on a conversation with Roland Huss ]
TH> "Craig R. McClanahan" wrote:
>> In future versions of Struts we will be integrating the ability to create
>> client side validations.
TH> As we start work on the 1.1 task list, I would like to suggest that we
TH> start thinking in terms of a core Struts framework that can be
TH> supplemented by any number of extensions. (As Roland Huss put it,
TH> something like Java and Javax.)
It sounds very good, but there are some troubles with such kind of
extensions.
I am trying to make my extension more pluggable, but it is needed to
perform some operations (Digester catch to perform configuration scan,
request processing catch, etc.) at ActionServlet level and so my
extension - BeanFactoryServlet extends ActionServlet to perform such
operations. Therefore imagine such situtaion as - developer needs to
perform validations, bean-factory support or other services. If all of
such extensions will be formed as extended from ActionServlet classes
then developer needs to perform some hack and integrate all this
packages to one servlet. i think it can be not so far simple way.
To support flexible extensions mechanism for struts there are can be
made some additions to the core structure of the framework -
1. Add ability to register components or external servlets (at
application level) via struts-config file.
2. Give such external components or servlets ability to use action
mappings database from ActionServlet.
3. Extend core API of struts to support pluggable extensions - for
example use event model or direct calls via registrations in action
mappiongs database.
The best way for my mind is to write external servlets, register it in
struts ActionServlet and use it as external services. This approach
can be useful in case of mutliple ActionServlet instances in one
application - every ActionServlet subscribe to use and uses some
amount of external services.
--
Best regards,
Oleg mailto:[EMAIL PROTECTED]
