At 12:21 PM +0200 11/7/01, Ulrich Mayring wrote:
Doing a 'grep -r sendRedirect * | wc -l' on the above app I get 104.
Does this mean I have to write 104 actions? Or is it possible to write a
generic redirect action
If they are all totally different sendRedirect tests, used only
On Sun, 15 Jul 2001, Jeremy Quinn wrote:
Being able to make Actions using XSP TagLibs allows existing XSP languages
a route into the 'ideal' way of working with Cocoon 2, where they have
developed out of the usage patterns in Cocoon 1.
Why not drop Actions altogether and instead put XSP
On Sun, 15 Jul 2001, giacomo wrote:
On Sun, 15 Jul 2001, Uli Mayring wrote:
Why not drop Actions altogether and instead put XSP taglibs in that place?
It's all just Java, so why should we have two places to do our custom
logic? From what I hear Actions allow more than XSP (redirects
Uli,
have you thought about redesigning the SOAP taglib
(logicsheet?) so that it is portable to C2?
I would need to have it running fairly soon and am
ready to put in some eforts :-)
With regards to the auth taglib, I would still suggest
that you look into the RequestIntercepter
implementation
Drasko Kokic wrote:
Uli,
have you thought about redesigning the SOAP taglib
(logicsheet?) so that it is portable to C2?
I would need to have it running fairly soon and am
ready to put in some eforts :-)
With regards to the auth taglib, I would still suggest
that you look into the
Drasko Kokic wrote:
Uli,
have you thought about redesigning the SOAP taglib
(logicsheet?) so that it is portable to C2?
I would need to have it running fairly soon and am
ready to put in some eforts :-)
With regards to the auth taglib, I would still suggest
that you look into the
Hi,
we had several month ago a lengthy discussion about this redirection
thing.
These are the two major reasons for removing the redirect from the xsp:
1. Working in a servlet environment and doing redirects is not that easy.
If you do a redirect when something is written already to the
Anders Lindh wrote:
Migrating from C1 becomes so much more complicated
when XSP redirects are not available...
I agree. There's no way I can port my old Cocoon1 apps
without redirects
being available conditionally (i.e. depending on user
input). Perhaps
this is possible
On 11.Jul.2001 -- 10:08 AM, Ulrich Mayring wrote:
Carsten Ziegeler wrote:
The right place for application flow and redirects is the sitemap in
c2. So you can make redirects in the sitemap using the map:redirect-to
element or you can write your custom action which can do a
Hi Ulrich,
I've found that over time, my sitemap testing has moved from focusing
on technical nitty gritty to focusing on concepts. Its a subtle
difference, but it makes conditional checking for your examples below
a little easier.
On Wed, 11 Jul 2001, Ulrich
Marcus Crafter wrote:
[...]
Ok, thanks a lot for your info. I now understand it is possible, but
extremely complicated and verbose to do redirects in Cocoon2 :-)
I've found that over time, my sitemap testing has moved from focusing
on technical nitty gritty to focusing on
Doing a 'grep -r sendRedirect * | wc -l' on the above app I get 104.
Does this mean I have to write 104 actions? Or is it possible to write a
generic redirect action
If they are all totally different sendRedirect tests, used only once
in individual xsp pages, you may need to
Anders Lindh wrote:
Doing a 'grep -r sendRedirect * | wc -l' on the above app I get 104.
Does this mean I have to write 104 actions? Or is it possible to write a
generic redirect action
If they are all totally different sendRedirect tests, used only once
in individual xsp
Berin Loritsch wrote:
If you think of ways to minimize redirects, then you can minimize the number
of Actions you have to write.
Heh, this reminds me of the discussion a few days ago, where I was
criticized for saying: Don't use Internet Explorer and you won't incur
the IE/Cocoon/PDF
Ok, thanks a lot for your info. I now understand it is possible, but
extremely complicated and verbose to do redirects in Cocoon2 :-)
Oh, you aren't being fair. Just because it is too easy to do in
scripting frameworks, doesn't mean we should allow the same abuse
of redirects in Cocoon. You
Anders Lindh wrote:
Ok, thanks a lot for your info. I now understand it is possible, but
extremely complicated and verbose to do redirects in Cocoon2 :-)
Oh, you aren't being fair. Just because it is too easy to do in
scripting frameworks, doesn't mean we should allow the same abuse
of
it. So please, give us redirects even if you tell us not to use it.
-Christopher
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: RE: AW: [C2] Redirects
Ok, thanks a lot for your info. I now understand it is possible, but
extremely complicated and verbose to do
Ulrich Mayring wrote:
It's not up to me what framework our business partners use. But I have
to able to communicate with them - the Sitemap is an inappropriate
format for this communication. It's too low-level, we need to think in
concepts :-)
I agree. I don't think the Sitemap is the
On 11.Jul.2001 -- 05:06 PM, Anders Lindh wrote:
One of the issues is technical in nature. Because of the SAX stream
approach
that Cocoon 2 uses, the XSP page is being serialized AS it is being parsed.
What is happening is that each SAX event (startDocument, startElement,
etc),
is being
Berin Loritsch wrote:
No, I'm saying, don't use redirects when another tool will work better.
I'm challenging the concept that you _have_ to use redirects to control
program flow.
Ok, you're saying I should select my logic from inside Beans. I don't
use Beans for various reasons and think I
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 11, 2001 3:37 PM
Subject: Re: AW: [C2] Redirects
Berin Loritsch wrote:
Oh, you aren't being fair. Just because it is too easy to do in
scripting frameworks, doesn't mean we should allow the same abuse
of redirects in Cocoon. You just
Ulrich Mayring wrote:
Christopher Painter-Wakefield wrote:
I think the point is also well taken that, hey, redirects
are a part of the current state of the art
in web programming.
Not only that, redirects are part of the HTTP standard. So they should
be the first thing that is
Ulrich Mayring wrote:
Berin Loritsch wrote:
That is a problem inherent in JSP, ASP, and ColdFusion. Each has their own
proprietary
way of handling logic. XSP is the first scripting language that allows you to
use logicsheets defined in other languages--but any time you use the
On Wed, 11 Jul 2001, Berin Loritsch wrote:
I think you may already be used to not
getting the output stream in Cocoon 1.
In Cocoon1 it is actually possible to get the OutputStream, I'm using that
in my soap taglib. My auth taglib makes heavy use of redirects (such as
redirecting you to the
On Wed, 11 Jul 2001, Berin Loritsch wrote:
If I understand this correctly, the Avalon Configuration object is kind
of a simplified XML structure without deeper nesting, right?
It can fully represent an XML structure, but it ignores namespaces and you
cannot traverse UP the
25 matches
Mail list logo
