You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by bu...@apache.org on 2003/11/04 15:31:40 UTC

DO NOT REPLY [Bug 24389] New: - New ResourceLoadAction

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24389>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24389

New ResourceLoadAction

           Summary: New ResourceLoadAction
           Product: Cocoon 2
           Version: 2.1.2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: general components
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: andrzej@chaeron.com


I've created a new ResourceLoadAction (based on the ResourceExistsAction).

This action is very useful if you want to load a pipeline, so that it can set up 
some things used in your calling pipeline.  

For example, you may need to access DOM information stored in your 
session/request object, so might need to call a pipeline ahead of time to read 
the data from a database and then use WriteDomTransformer to put the data where 
your main pipeline can get at it.

I ran into a situation where I wanted to use a Selector coupled with the 
JXPathMetaModule (to read the selector value from a DOM document in the session)
, but needed to do ensure that the data was first loaded into the session.  
ResourceLoadAction solved this need.

Basically, it's very much like a <map:call> but with the serialized output being 
thrown away, so it can be used to call any arbitrary pipeline anywhere you can 
put an action.

Source attached.

....Andrzej