On Mon, 21 Jan 2002, Oleg V Alexeev wrote:
> Date: Mon, 21 Jan 2002 16:06:24 +0300
> From: Oleg V Alexeev <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>,
> Oleg V Alexeev <[EMAIL PROTECTED]>
> To: Struts Developers List <[EMAIL PROTECTED]>
> Subject: Re: Validator integration in Struts
>
> Hello David,
>
> Can you help me with services? A time ago I start services subproject
> in commons-sandbox - it will be core lib to build service-oriented
> struts architecture. Now we start new project and I have not time
> enough to prepare it to the work with struts.
> Is it interesting for you?
>
It (integrating services) is finally getting to the top of my TODO list.
I presume we should really be doing this based on the version in
commons-sandbox, right? One thing I can't seem to find is the old mail
threads describing the roles of the various components -- Oleg, could you
please refresh my memory with a short description of the roles of all the
core components (Event, Module, Queue, Service, ServiceManager, and so
on)? (This stuff should really be added into the Javadoc comments also.)
I note that Oleg proposes that a Service have an initDigester() method so
that it can add custom processing rules to the Digester that will be used
to process the struts-config.xml file. One implication of taking
advantage of this facility is that you won't be able to use a validating
XML parse of this file, because the custom elements for each service won't
be defined in the DTD.
As an alternative, how about the idea that each Service implementation
class must be configured based on JavaBeans properties, so that we can use
nested <set-property> elements like we do with data sources to configure
each service?
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
