You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Omar Adobati <om...@gmail.com> on 2006/08/01 14:12:38 UTC
Action Vs Logicsheet
Good Morning,
How I could choose if I need an action or a logicsheet? Or, better
said, when I should use Action instead logicsheet or vice versa?
Sorry the dummy question,
Omar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Action Vs Logicsheet
Posted by Toby <to...@linux.it>.
ian.d.stewart@jpmchase.com wrote:
> you can only have one flow active at a time per user
I have found CInclude to be a decent practical solution to this problem.
I generate the container page (think of a portal page, with sub-modules
and forms) using SQL Transformer and a few steps of JX and XSLT,
generating CInclude tags where I need to call functions or continuations,
which will then produce the requested modules. This lets me include
more than one flowscript (or CForm) in the same page.
Of course there can only be one "active" flow (meaning a continuation
call) at every given point; the others are just function calls: new
forms displayed somewhere else in the page, which the user might choose
to pursue, disregarding his current one.
This solution is far from perfect: it creates a new cocoon Request for
each included module, complicating things like HTTP POST processing, but
it's the best I could find.
(I will admit, I have yet to look at BricksCMS.)
Toby
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Action Vs Logicsheet
Posted by Omar Adobati <om...@gmail.com>.
It seems as there are a lot of different ideas about what to use and I
think to be more confused then I was sending the first e-mail...
So, I suppose also that there's no a definitive answer to my question...
Action and Transformer are the old-school way to do the job, flow is
the new... noone is the wrong... I'll try to experiment those three
ways and then I'll try to write someting about them.
good night,
Omar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Re: Re: Flow concurrency (was Re: Action Vs Logicsheet)
Posted by Torsten Curdt <tc...@apache.org>.
> Hi Torsten,
>
> I admit that it's been awhile since I've looked into JavaFlow, but I was
> under the impression that it suffered from the same concurrency issues.
>
> Are you say that that's not the case?
I am pretty sure it should be ok as external state is only held inside
a context object. There is no synchronization required and the state
of the internal resume/record status is (of course) held in a
non-static way.
The only issue I am aware of are sub-request though the cocoon
protocol as they use the same thread. Basically if you call a pipeline
and then inside the flow again call out to anther pipeline that also
uses flow ...which would be a bit awkward anyway ;-)
...but it could well be this has changed during development in jakarta
commons. We still have 2-3 things to fix - but that javaflow version
is already *much* better than the one in 2.1
HTH
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Re: Flow concurrency (was Re: Action Vs Logicsheet)
Posted by ia...@jpmchase.com.
Hi Torsten,
I admit that it's been awhile since I've looked into JavaFlow, but I was
under the impression that it suffered from the same concurrency issues.
Are you say that that's not the case?
Thanks,
Ian
It's better to be hated for who you are
than loved for who you are not
Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078
"Torsten Curdt"
<tcurdt@apache.or
g> To
Sent by: users@cocoon.apache.org,
tcurdt@gmail.com rgoers@apache.org
cc
08/02/2006 04:47 Subject
AM Re: Re: Flow concurrency (was Re:
Action Vs Logicsheet)
Please respond to
users@cocoon.apac
he.org
> > Not sure if that's really such a big thing (how many concurrent
> > requests to the flow engine do you expect a user to make. Quick
> > fingers! ;-)
> Think "Cocoon Portal".
Still! ...except for the first load and all portlets creating the
first continuation (if they do) the user still has use the portlets
concurrently. If the flow is nothing enormously long running it should
be alright. If not - well then there might be an issue. But it's not
as if hundreds of users are getting blocked. Do you experienced any
problems with it like that?
...but why am I going into details here - use javaflow ;-)
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Re: Flow concurrency (was Re: Action Vs Logicsheet)
Posted by Torsten Curdt <tc...@apache.org>.
> > Not sure if that's really such a big thing (how many concurrent
> > requests to the flow engine do you expect a user to make. Quick
> > fingers! ;-)
> Think "Cocoon Portal".
Still! ...except for the first load and all portlets creating the
first continuation (if they do) the user still has use the portlets
concurrently. If the flow is nothing enormously long running it should
be alright. If not - well then there might be an issue. But it's not
as if hundreds of users are getting blocked. Do you experienced any
problems with it like that?
...but why am I going into details here - use javaflow ;-)
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Flow concurrency (was Re: Action Vs Logicsheet)
Posted by Ralph Goers <Ra...@dslextreme.com>.
Torsten Curdt wrote:
>> >> You're saying that flow calls in concurrently received requests
>> within
>> >> a session are processed serially, not in parallel threads? Is that
>> >> right?
>> >
>> > That's pretty much it in a nutshell, yes.
>>
>> wow...
>
> Not sure if that's really such a big thing (how many concurrent
> requests to the flow engine do you expect a user to make. Quick
> fingers! ;-)
Think "Cocoon Portal".
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Flow concurrency (was Re: Action Vs Logicsheet)
Posted by Torsten Curdt <tc...@apache.org>.
> >> You're saying that flow calls in concurrently received requests within
> >> a session are processed serially, not in parallel threads? Is that
> >> right?
> >
> > That's pretty much it in a nutshell, yes.
>
> wow...
Not sure if that's really such a big thing (how many concurrent
requests to the flow engine do you expect a user to make. Quick
fingers! ;-)
> Is there a developer around who can confirm/refute the above?
For javaflow this should not be true.
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Flow concurrency (was Re: Action Vs Logicsheet)
Posted by Mark Lundquist <ml...@wrinkledog.com>.
On Aug 1, 2006, at 1:46 PM, ian.d.stewart@jpmchase.com wrote:
>> You're saying that flow calls in concurrently received requests within
>> a session are processed serially, not in parallel threads? Is that
>> right?
>
> That's pretty much it in a nutshell, yes.
wow...
Is there a developer around who can confirm/refute the above?
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Action Vs Logicsheet
Posted by ia...@jpmchase.com.
You're saying that flow calls in concurrently received requests within
a session are processed serially, not in parallel threads? Is that
right?
That's pretty much it in a nutshell, yes.
Ian
It's better to be hated for who you are
than loved for who you are not
Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078
Mark Lundquist
<ml@wrinkledog.co
m> To
users@cocoon.apache.org
08/01/2006 04:31 cc
PM
Subject
Re: Action Vs Logicsheet
Please respond to
users@cocoon.apac
he.org
Hi Ian,
On Aug 1, 2006, at 12:59 PM, ian.d.stewart@jpmchase.com wrote:
> Having personally experienced it, I can answer pretty confidently that
> it
> is indeed true, at least in the configuration I was using (sidebar and
> main
> content each within its own frame).
You're saying that flow calls in concurrently received requests within
a session are processed serially, not in parallel threads? Is that
right?
>
> As far as the why's, I had the need for both the sidebar and the main
> page
> to be generated dynamically, and at the time CForms + FlowScript was
> promoted as the One True Way(TM) to generate content dynamically within
> Cocoon..
Well certainly, XSLT has always been used to generate dynamic content...
best regards,
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
Re: Action Vs Logicsheet
Posted by Mark Lundquist <ml...@wrinkledog.com>.
Hi Ian,
On Aug 1, 2006, at 12:59 PM, ian.d.stewart@jpmchase.com wrote:
> Having personally experienced it, I can answer pretty confidently that
> it
> is indeed true, at least in the configuration I was using (sidebar and
> main
> content each within its own frame).
You're saying that flow calls in concurrently received requests within
a session are processed serially, not in parallel threads? Is that
right?
>
> As far as the why's, I had the need for both the sidebar and the main
> page
> to be generated dynamically, and at the time CForms + FlowScript was
> promoted as the One True Way(TM) to generate content dynamically within
> Cocoon..
Well certainly, XSLT has always been used to generate dynamic content...
best regards,
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Action Vs Logicsheet
Posted by ia...@jpmchase.com.
Having personally experienced it, I can answer pretty confidently that it
is indeed true, at least in the configuration I was using (sidebar and main
content each within its own frame).
As far as the why's, I had the need for both the sidebar and the main page
to be generated dynamically, and at the time CForms + FlowScript was
promoted as the One True Way(TM) to generate content dynamically within
Cocoon..
It's better to be hated for who you are
than loved for who you are not
Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078
Mark Lundquist
<ml@wrinkledog.co
m> To
users@cocoon.apache.org
08/01/2006 03:01 cc
PM
Subject
Re: Action Vs Logicsheet
Please respond to
users@cocoon.apac
he.org
On Aug 1, 2006, at 10:21 AM, ian.d.stewart@jpmchase.com wrote:
> Ok, let's assume a typical layout (header, footer, sidebar, main
> content).
ah, OK, that kind of component... :-)
> Under normal circumstances (i.e., no control flow), each of these
> components would start loading at more or less the same time and at any
> given time all of the components would be at least partially loaded
> (and
> thereby usable).
With you so far...
> If we instead use control flow to load these components,
> the header would load first. Once the header is completely loaded,
> then
> the sidebar would start loading. Then the main page, and finally the
> footer.
Huh? No way, I don't think that is true!!
cheers,
—ml—
P.S. Also, I'm having trouble envisioning a design where these layout
elements (header, sideabar, etc.) map to discrete requests... unless
you were using frames/iframes? And even if it were so, why would there
be a need to involve some flow/action/XSP business in the handling of
each one of these?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
Re: Action Vs Logicsheet
Posted by Mark Lundquist <ml...@wrinkledog.com>.
On Aug 1, 2006, at 10:21 AM, ian.d.stewart@jpmchase.com wrote:
> Ok, let's assume a typical layout (header, footer, sidebar, main
> content).
ah, OK, that kind of component... :-)
> Under normal circumstances (i.e., no control flow), each of these
> components would start loading at more or less the same time and at any
> given time all of the components would be at least partially loaded
> (and
> thereby usable).
With you so far...
> If we instead use control flow to load these components,
> the header would load first. Once the header is completely loaded,
> then
> the sidebar would start loading. Then the main page, and finally the
> footer.
Huh? No way, I don't think that is true!!
cheers,
—ml—
P.S. Also, I'm having trouble envisioning a design where these layout
elements (header, sideabar, etc.) map to discrete requests... unless
you were using frames/iframes? And even if it were so, why would there
be a need to involve some flow/action/XSP business in the handling of
each one of these?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Action Vs Logicsheet
Posted by ia...@jpmchase.com.
Ok, let's assume a typical layout (header, footer, sidebar, main content).
Under normal circumstances (i.e., no control flow), each of these
components would start loading at more or less the same time and at any
given time all of the components would be at least partially loaded (and
thereby usable). If we instead use control flow to load these components,
the header would load first. Once the header is completely loaded, then
the sidebar would start loading. Then the main page, and finally the
footer. The larger the content of the particular component, the more
pronounced the effect.
It's better to be hated for who you are
than loved for who you are not
Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078
Mark Lundquist
<ml@wrinkledog.co
m> To
users@cocoon.apache.org
08/01/2006 12:00 cc
PM
Subject
Re: Action Vs Logicsheet
Please respond to
users@cocoon.apac
he.org
On Aug 1, 2006, at 8:54 AM, ian.d.stewart@jpmchase.com wrote:
> Keep in mind that control flow is synchronized to the user's session.
> This
> means that you can only have one flow active at a time per user (this
> is
> true whether you are using FlowScript or JavaFlow). For most simple
> applications this is not an issue, but if you have a page with multiple
> components, and each component is generated using control flow, then
> subsequent components won't start loading until previous components
> have
> finished loading.
Interesting... but I'm not sure I understand, can you give an example?
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
Re: Action Vs Logicsheet
Posted by Mark Lundquist <ml...@wrinkledog.com>.
On Aug 1, 2006, at 8:54 AM, ian.d.stewart@jpmchase.com wrote:
> Keep in mind that control flow is synchronized to the user's session.
> This
> means that you can only have one flow active at a time per user (this
> is
> true whether you are using FlowScript or JavaFlow). For most simple
> applications this is not an issue, but if you have a page with multiple
> components, and each component is generated using control flow, then
> subsequent components won't start loading until previous components
> have
> finished loading.
Interesting... but I'm not sure I understand, can you give an example?
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Action Vs Logicsheet
Posted by ia...@jpmchase.com.
Keep in mind that control flow is synchronized to the user's session. This
means that you can only have one flow active at a time per user (this is
true whether you are using FlowScript or JavaFlow). For most simple
applications this is not an issue, but if you have a page with multiple
components, and each component is generated using control flow, then
subsequent components won't start loading until previous components have
finished loading.
For this reason, I use JXTemplate in combination with custom actions when
loading components, and it seems to work pretty well.
It's better to be hated for who you are
than loved for who you are not
Ian D. Stewart
Appl Dev Analyst-Advisory, DCS Automation
JPMorganChase Global Technology Infrastructure
Phone: (614) 244-2564
Pager: (888) 260-0078
Mark Lundquist
<ml@wrinkledog.co
m> To
users@cocoon.apache.org
08/01/2006 11:24 cc
AM
Subject
Re: Action Vs Logicsheet
Please respond to
users@cocoon.apac
he.org
On Aug 1, 2006, at 5:12 AM, Omar Adobati wrote:
> How I could choose if I need an action or a logicsheet? Or, better
> said, when I should use Action instead logicsheet or vice versa?
Neither! Avoid both and use flow. Some people like Javaflow, I like
Flowscript... but XSP and custom actions are old-skool obsolete :-)
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
-----------------------------------------
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and
any attachments are believed to be free of any virus or other
defect that might affect any computer system into which it is
received and opened, it is the responsibility of the recipient to
ensure that it is virus free and no responsibility is accepted by
JPMorgan Chase & Co., its subsidiaries and affiliates, as
applicable, for any loss or damage arising in any way from its use.
If you received this transmission in error, please immediately
contact the sender and destroy the material in its entirety,
whether in electronic or hard copy format. Thank you.
Re: Action Vs Logicsheet
Posted by Mark Lundquist <ml...@wrinkledog.com>.
On Aug 1, 2006, at 5:12 AM, Omar Adobati wrote:
> How I could choose if I need an action or a logicsheet? Or, better
> said, when I should use Action instead logicsheet or vice versa?
Neither! Avoid both and use flow. Some people like Javaflow, I like
Flowscript... but XSP and custom actions are old-skool obsolete :-)
—ml—
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org