> >> PERFUME:
> >>>
> >>> 1) The implementation of Perfume
shall result
> >>> in three distinct Cocoon
components:
> >>>
> >>> a) A generator that can
receive a soap
> >>> message and turn it into
an xml sax
> >>> stream.
> >>
> >> Why not use an Action? Then you could set sitemap
variables, call
> >> other
> >> actions, use an existing generator...
> >
> > Please elaborate more here. I've only
written one action component
> > so far, that is used to set a sitemap
> > variable. How would an action component take the
place of a generator
> > component.
>
> My first reason for not using a generator to handle
the SOAP request is
> that it doesn't quite fit into the role of
generators, I think the
> generator should be used to create the response.
A generator would be best suited to part of the task
of creating a "soap service", right? I think we are
on the same page here, just different terminology.
> But the real problem I see here is how to do
something useful with the
> SOAP request. Once you receive the request you've go
to do something
> with it. If all you have is a SOAPGenerator and a
SOAPSerializer, then
> all you can so is put some transformers in between
them to turn the
> request into a response. You wouldn't be able to do
a whole lot unless
> you wrote your own transformer. With the built in
transformers the most
> complex thing I could see doing in using an
XSLTransformer and the an
> SQLTransformer to do a database lookup. If you want
to perform some of
> the functions that are typically done with Actions
or flowscript you'll
> need Actions.
On the contrary, I do not see this as the problem,
but rather the
solution. In My Humble Opinion, the future of
software is in
Cocoon like architectures which are XML centric, and
posses
transformers that modify information from start to
finish.
I call this XML-Directed Software: SQLTransformer,
XSLTransform
LDAPTransformer, are specific instance of this
concept.
> If you had a SOAPAction though, you could take
information about the
> soap request and place it into sitemap parameters,
from there you could
> use those parameters with selectors to choose
appropriate pieces of the
> pipeline.
I'm intrigue by this, but still unable to visualize
it. Can
you provide a example of a sitemap fragment(s) that
demonstrate
what you are articulating?
> >
> > Where can I find out more about flowscript?
>
> Got me. I followed the discussion of the dev list
for a while, but I've
> never played with 2.1 and there's no doc that I've
found yet. I guess
> download 2.1.
Can anyone else point us to an overview of
flowscript?
Steve Punte
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
