Re: xsp-actions broke with a NPE (treeprocessor error?)

[Sylvain Wallez]

Antonio Gallardo wrote:

Sylvain Wallez dijo:
 

Antonio Gallardo wrote:

   

Hi:

The lastest changes in treeprocessor broke the xsp-action. The problem is in method setup() in o.a.c.generation.ServerPagesGenerator.java this class needs a SourceResolver.
     

Ooops,sorry! It should be fixed now. Please cross-check!
   

Hi Sylvain:

Thanks for the fix. It works now.
 

BTW, can you explain how you use xsp-action? Do you need xsp taglibs in 
an action or is it just a convenient way to write small custom actions 
without writing a java class?

I'm asking because I several times encountered the need for some very 
small app-specific code to be called as part of a pipeline that 
otherwise don't need all the bells and whistles of a flowscript call, 
and I'm still thinking a flow-action may be a very usefull addition, 
i.e. an action that allows to call a flowscript function (and access the 
global scope) but doesn't require to end with a sendPage or sendPageAndWait.

Sylvain

--
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance  -  http://www.orixo.com