On 12.10.2005 13:52, Daniel Fagerstrom wrote:
But even then you realize that accessing the natural functionality
(and power)
of Cocoon is often very difficult, because there is no obvious API
and no
function library to access the core functionality.
BTW, this is the most negative issue with Cocoon at least one person
has (I
don't mean myself and I don't want to speak in his name, so leave him
anonymous): Cocoon does not really provide an API you can program to.
Take even
such a simple task as accessing session/request/etc.
Agree about the lack of well defined API. Both in the sense that we
don't mark what is supposed to externally reusable and reasonable stable
interfaces. And in the sense that we have had feature creep in our core
interfaces as Berin showed for Processor.
+1
For session, request etc I think we should migrate to the servlet apis
as I wrote in an other message. Having own interfaces in this area
doesn't make that much sense anymore.
I can't follow your reasoning. We have an abstraction of the
environment. Why do you want to give it up?
Jörg
