-Original Message-
From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]]
Reinhard Poetz wrote:
There remains one open question for me: How to I get 'feedback'
whether the called pipeline did its job well or not? And if
not, how
to I get information about what happend
Reinhard Poetz wrote:
Stefano Mazzocchi wrote:
snip
Let me add:
- make a new method that allows the flow to call a pipeline and pass a
different output stream. This will allow to use pipelines as tools to
serialize things, say, to disk or to other means.
What do you think?
/snip
I think
Sylvain Wallez wrote:
Sorry to jump in lately, but the vote made me consider that thread as
important and I finally looked at it. So here we go...
Which was the reason to call for a vote even if the discussion is not
yet finalized :-)
I do know how lazy you people are :-) (oh, just because
Thank you very much! I thought that it would work the other way!
Regards,
Reinhard
-Original Message-
From: Christopher Oliver [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 7:18 AM
To: [EMAIL PROTECTED]
Subject: Re: [vote] finilizing the pending votes on flow [was Re
-Original Message-
From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 17, 2003 1:27 PM
To: [EMAIL PROTECTED]
Subject: Re: [vote] finilizing the pending votes on flow [was Re: [RT]
Flow/SitemapIntegration]
Reinhard Poetz wrote:
Stefano Mazzocchi wrote
Reinhard Poetz wrote:
Therefore I'll come up with a solution of using the flow as controller for
XMLForms - a 'pre-alpha' version is already running at my laptop. I know
that my solution is far from being perfect (continuations can be very tricky
...) but I want to learn and the feedback will
[I'm resending this, since the first time I managed to inadvertently cut
the last part of the message.]
Reinhard Poetz wrote:
Therefore I'll come up with a solution of using the flow as
controller for
XMLForms - a 'pre-alpha' version is already running at my laptop. I know
that my solution
For my flows I use a self-defined function which makes this for me:
function callPipeline(src) {
xc = cocoon.componentManager.lookup( myXMLConsumer.ROLE );
resolver =
cocoon.environment.getObjectModel().get(source-resolver);
srce = resolver.resolveURI(src);
Ugo Cei wrote:
Reinhard Poetz wrote:
Therefore I'll come up with a solution of using the flow as
controller for
XMLForms - a 'pre-alpha' version is already running at my laptop. I know
that my solution is far from being perfect (continuations can
be very tricky
...) but I want to
Stefano Mazzocchi wrote:
Sylvain Wallez wrote:
Sorry to jump in lately, but the vote made me consider that thread
as important and I finally looked at it. So here we go...
Which was the reason to call for a vote even if the discussion is not
yet finalized :-)
I do know how lazy you people
Michael Melhem wrote:
On Fri, Jan 17, 2003 at 04:20:17PM +0100, Sylvain Wallez wrote:
snip/
OK. So we have some strong and justified -1's against map:flowmap...
Yes your argument is convincing, so perhaps we should put
the flowmap issue on the back-burner .. ;)
One small point
Reinhard Poetz wrote:
There remains one open question for me: How to I get 'feedback' whether the
called pipeline did its job well or not? And if not, how to I get
information about what happend (error message/status information)?
What do you think?
I think you are getting right to the bone
Sorry to jump in lately, but the vote made me consider that thread as
important and I finally looked at it. So here we go...
Semantic confusion induced by map:pipeline
First of all, I wonder if all this started because the sitemap top-level
Stefano Mazzocchi wrote:
snip
Let me add:
- make a new method that allows the flow to call a pipeline and pass a
different output stream. This will allow to use pipelines as tools to
serialize things, say, to disk or to other means.
What do you think?
/snip
I think you mean a function
Hi Reinhard,
Just a warning, you should always use the var keyword with local
variables in JavaScript. Your function should probably read:
function callPipeline(src) {
var xc = cocoon.componentManager.lookup( myXMLConsumer.ROLE );
var resolver =
15 matches
Mail list logo
