Joerg Heinicke schrieb: > Wondering about your problem I had a look into the code - and the > environment abstraction indeed still exists. I thought it already has > been removed. I send this mail to dev list too, maybe somebody can > comment on this (Daniel, Carsten ?) > Yes, we still use the environment abstraction - mainly for compatibility. We had some discussion in the past to switch to the servlet req/response interfaces etc. While this is the right move, it creates big incompatibilities. So we either have to support two apis in parallel or wait until 3.0.
There are several problems with our abstraction; one of them is that we use our own apis (we can create wrappers for this to directly use the http servlet api) - but the other problem is that we are not using the request attributes to store additional request information. Unfortunately everything is stored in the objectModel map, e.g. the flow context etc. And even more: the request is an object stored in the objectModel. I think we have to change this as well and add all request relevant information as attributes of the request object. This would then allow to easily use other techniques/frameworks - like you could then just forward your request from Cocoon flow to a JSP doing the rendering. But just adding all this stuff to request attributes is not that easy as unfortunately sub request are sharing the attributes with the main request. So whenever you use the cocoon protocol the main request and the sub request use the same set of attributes. I hoped to solve these problems for 2.2 but I never had a good idea - but it's something we should definitly work on for the next releases. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
