cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reinhard Poetz" <>
Subject RE: Flow and actions correct way?
Date Fri, 13 Feb 2004 12:31:34 GMT

From: Upayavira [] 

> Antonio Gallardo wrote:
> >Joose Vettenranta dijo:
> >  
> >
> >>When creating java-class that can be called from inside 
> flow, does it 
> >>have to be compiled against some cocoon class, or can be 
> separed? How 
> >>can I get information from request, or does that have to 
> been wrapped 
> >>through flow? What I like to do, is to make an action like class, 
> >>which would take input as parameters and take input from request. 
> >>Although, flow has cocoon.get.request() stuff, so that 
> could be used 
> >>as a wrapper.
> >>    
> >>
> You should probably use the the cocoon.createObject() method, 
> which will 
> treat your object as if it were an Avalon component. Then, if your 
> object implements certain interfaces (e.g. SitemapModelComponent?) it 
> will have certain methods called to pass it stuff, such as the 
> ObjectModel, which will enable it to get at the Java Request 
> object. I 
> would caution against using the cocoon object within Java, it just 
> doens't make sense.
> HTH.

IIUC only Avalon interfaces are supported by cocoon.createObject(), 
not Cocoon internal interfaces like SitemapModelComponent.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message