Stefano Mazzocchi wrote:
Maybe I'm the only one, but I'm not scared of the core. For me it is simply that the highest priority items are all in the portal block. I do have items in core on my list. Namely,No, and I don't care.
This is *NOT* what I'm trying to solve. I don't care if users user java or not, what I care is that cocoon committers are not afraid of the core or that they are not adding java components to the system because writing them in javascript is faster and easier (been there, done that).
I want to make it easier to go back into hacking cocoon itself, because innovation is happen on the outside and I think this is dangerous in the long run to the solidity of the internals.
1. HandleErrors doesn't work properly on internal pipelines.
2. I really want thread-safe generators and transformers.
I've glanced at the sitemap code to see what it would take to do item 2 and it didn't seem to me that the code was pretty understandable.
But I can only get to those on my own time as my task list for my employer isn't even leaving me time to work on the portal stuff. <sigh>
Ralph
