cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ch ku <gajch...@yahoo.com>
Subject Re: Cocoon - web environment coupling ?
Date Thu, 29 Aug 2002 06:50:22 GMT
Hi Everybody 

I am new to this list. We have been using cocoon for
last 3 months now. Its an excellent application. I am
facing some problems though which I was not able to
understand. 

Our environment is 
apache tomcat cocoon 2.0.1. When I startup apache and
tomcat and try to access some page through cocoon 

e.g /cocoon/email_alert/EmailList, it throws
incremental error. But after refreshing page for 20 to
 30 times I get the webpage back and then all works
fine .

Can anybody help me with this ?

thanks in advance 

chinmay 


















--- Nicola Ken Barozzi <nicolaken@apache.org> wrote:
> 
> Pierre-Alexandre Losson wrote:
> >> But since to set up Cocoon correctly you have to
> perform some steps 
> >> that are not so easy to remember, very recently
> we have been thinking 
> >> of creating a CocoonBean.java that would make the
> embedded usage in 
> >> Cocoon easier.
> >>
> >> Basially what you need is this Bean; you can do
> it quite easily from 
> >> Main.java, and it would be well accepted as a
> contribution to Cocoon 
> >> :-D <hint hint - nudge nudge> ;-)
> > 
> > 
> > I'll gladly investigate and implement this than.
> It'll clearly take me 
> > less time than reimplementing what Cocoon already
> does very well ;)
> 
> Cool! :-D
> 
> >> If you have /any/ question regarding this, feel
> free to ask :-)
> >>
> > 
> > My first question is the following : Cocoon has
> been built with the web 
> > in mind i suppose (historically anyway), an in
> that aspect is built 
> > around a 1 entry ---> 1 output paradigm.
> > 
> > Do you think it would be easy, or stated
> differently, what could be the 
> > problematics of using Cocoon in a  n input ---> n
> output system (xml 
> > pipeline architecture where a pipeline is not a
> 1->1)
> > I suppose one can always transform a n->n
> transformation to multiple 1 
> > to 1 of course but I just wanted to get your
> opinion on this.
> 
> There are no real problems about this, just that it
> hasn't been thought 
> worthwhile IIRC.
> 
> Some committers have been against this (still IIRC),
> because it can 
> possibly create confusion and unmannageability in a
> web publishing and 
> webapp system.
> 
> But when you start using it as an embedded system,
> it becomes quite 
> clear that it needs what XSLT gives, which means
> also n outputs.
> 
> So currently we have transformers that are able to
> write to the 
> filesystem, so that you can have n outputs by
> inserting a Transformer 
> for every n-1 output you need.
> 
> Now, the main point is: what is your use-case?
> To understand the requirements it's always best to
> see real-life
> examples and the exact points where you want the
> "fork" to begin.
> 
> -- 
> Nicola Ken Barozzi                  
> nicolaken@apache.org
>              - verba volant, scripta manent -
>     (discussions get forgotten, just code remains)
>
---------------------------------------------------------------------
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email:
> cocoon-dev-help@xml.apache.org
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message